A.2.4 Package the problem

If you have placed settings in a file in %OMSYSHOME%\d2g\local\config\*, copy those settings to your project configuration file before you do the following.

Create a .zip file smaller than 1 MB that contains the following files:

DITA file(s)

The smallest fragments that yield the problem. No unzipped files.

Output file(s)

Whatever output (if any) shows the undesired result.

Log file

Located by default in your project directory; see §4.2 Logging conversion events.

Configuration file(s)

Your project configuration file, plus any chapter-specific configuration file used by the problem DITA file.

Configuration templates

Include all configuration files and templates in every chain that might affect the result, except the distribution templates. However, if you have placed settings in a file in %OMSYSHOME%\d2g\local\config\*, copy those settings to your project configuration file before you create the package.

Macro libraries

If the problem file uses DITA2Go macros located in library files.

CSS file(s)

If your project uses CSS (HTML output only), and the problem is a display problem.

Help project file

If the problem occurs when you generate one of the following:

  • WinHelp: MyDoc.hpj.
  • HTML Help: MyDoc.hhp.
  • JavaHelp or Oracle Help for Java: MyDoc.hs.

Graphics files

Any external graphics referenced by the problem-file fragment.

Zip your files!

Do not send unzipped files.

Finally: Send the package to Omni Systems.

Previous Topic:  A.2.3 Document the problem

Next Topic:  A.2.5 Send the package to Omni Systems

Parent Topic:  A.2 How to request help

Sibling Topics:

A.2.1 If the problem involves a crash

A.2.2 Scope the problem

A.2.3 Document the problem

A.2.5 Send the package to Omni Systems

Table of ContentsIndex