#### A.1.5 Check your version of DITA2Go

If you are using DITA2Go, do the following:

1. In a text editor, open an output file (.htm or .rtf or .dita or .ent) that you created with DITA2Go, and find a line near the top of the file that shows the DITA2Go version and build numbers. The line you want looks like this:

   HTML/XML: |
       <!-- generated by DCL filter dwhtm, Ver 4.0 x002 h289 -->
   RTF: |
       {\info {\doccomm DCL filter dwrtf, Ver 4.0 x002 r297}}

   Table A-1 lists the build numbers underlined in these examples.

2. Go to the DITA2Go Web site:

   http://www.dita2go.com/

   Navigate to Downloads > Basic Software > Components, and check the build numbers on the archived DLL files. For example:

   File | Size | Description | Last updated
       drxml002.zip
   | 215k | DITA input module | 01-Jun-2010
       dwrtf295.zip
   | 251k | RTF output module | 01-Jun-2010
       dwhtm289.zip
   | 421k | HTML/XML output module | 01-Jun-2010

3. Compare the number on each DLL archive file with the build numbers you found in your output, as shown in Table A-1.

   Table A-1 Examples of build numbers for DITA2Go DLL files

   Output type | DLL file | Build number: | Current?
   Latest | Used
   All |
       drxml.dll
       002
       x002
   | Yes
   HTML |
       dwhtm.dll
       289
       h284
   | No
   RTF |
       dwrtf.dll
       295
       r295
   | Yes

4. If the build number on a DLL archive is higher than the corresponding build number in your output file, obtain and install the current update; see §1.4 How to update DITA2Go. Then try the conversion again.
5. If you think you have all the latest DLLs, but a build number in the output file does not agree, there might be an old copy somewhere on your system, typically in \windows\system or \windows\system32. Find and delete the old copy, then download an updated copy and unzip it in %OMSYSHOME%\common\bin.
6. If you still encounter the problem, check whether later beta versions of any DLLs are available on the DITA2Go Web site:

   http://www.dita2go.com/

   Navigate to Downloads > Basic Software > Beta Components, and check the four-part numbers in the descriptions of the DLL files. The first two parts are the product version, third part the build number, and fourth is the beta version, zero for the released DLL, incremented for each beta build. For example:

   File | Size | Description | Last updated
       drxml.dll
   | 580k | DITA input module, 4.0.3.42 | 04-Jun-2012
       dwrtf.dll
   | 588k | RTF output module, 4.0.297.2 | 02-Jun-2012
       dwhtm.dll
   | 1052k | HTML/XML output module, 4.0.291.4 | 04-Jun-2012

7. Compare the third part of the number in each description with the build numbers you found in your output, as shown in Table A-1. If the fourth part is greater than zero, and the problem is due to a defect in DITA2Go, the defect might have been corrected. See §1.4.2 Try out DITA2Go beta executables.

Still no luck? See §A.2 How to request help.

Previous Topic: A.1.4 Check path names, file names, and drive location

Next Topic: A.2 How to request help

Parent Topic: A.1 Things to check first

Sibling Topics:

A.1.1 Examine your conversion log file

A.1.2 Check your DITA2Go installation

A.1.3 Check the DITA2Go User’s Guide

A.1.4 Check path names, file names, and drive location

Table of Contents • Index