pdfToolbox and pdfaPilot offer the possibility to convert several file formats to PDF. In order to receive the best results, the applications in which the files have been created are used for this conversion.

In case any errors occur during processing, please consult the following notes.

• All applications should be installed with the default options, in order to guarantee that all needed components are available.
• Install all the latest updates.
• Start the application at least once and make sure that the setup wizards have been executed successfully.
• pdfToolbox or pdfaPilot need to be activated. This means, a valid activation request must have been sent and the software must have been activated with the activation file received afterwards.
• The activation needs to be performed for the user who wants to execute the file conversion.
• On Windows systems, install the Microsoft .NET Framework Version 3.5 or newer - this is not automatically installed with the regular Windows Update but belongs to the optional updates.
• While conversions to PDF are performed, no other users on this machine should use the applications needed for this process.
• In particular the file to be processed should not be opened in the respective application.
• Only one instance of the application that creates PDF must be used at the same time. Therefore in pdfToolbox Server, pdfaPilot Server or in Enfocus Switch the number of instances needs to be set to 1.
• Although some file types can be processed with several applications it is recommended to process documents with the application where they were created with.

• Please make sure that Microsoft Office is activated. In case Microsoft Office runs as an evaluation version, a warning dialog might pop up during conversion.
• If there is no “PDF or XPS” entry in the “Save as” menu, install the missing Add-in. You can download it on the Microsoft website.
• Install the latest service pack for Microsoft Office.

• Word documents may contain annotations from the function “Track changes”. They are output into the PDF with the setting “Screen”. When outputting with setting “Print” they are not output. In the Desktop version of pdfToolbox the setting “Print” is default so that annotations are not output. Whereas in pdfaPilot Desktop the setting “Screen” is default so that annotations are output. On the Mac the output of annotations can only be omitted when running the english language version of Word. Moreover “Enable access for assistive devices” need to be enabled in “Universal Access” of the “System preferences”.

• If the contents exceed the “print area”, only the parts covered by this “print area” will be output whilst the other parts will not be output.
• The page format of the output PDF is optimized in order to fit as much content as possible in a well readable way onto a page. For large sheets the content may be spread over several PDF pages.

• A page range can not be specified, the parameter Page range (pagerange) does not have an influence.
• Images are exported with a resolution of 72 ppi, the parameter Print (topdf_print) does not have an influence.
• If Microsoft Office 2008 and Microsoft Office 2011 are installed the Office application that is set as default for opening Office documents in the system or the Office application that is already open is used to process Office documents.

• Under Windows dialogs appearing in the Office application during processing can be handled.
• Therefore an empty file named MTPGuiActions.log has to be placed in the user folder here: <user>\AppData\Roaming\axaio software\MS Office 12\MadeToPrint\Logfiles\
• If the Office document that opens a dialog is processed now an ID of the dialog is logged in MTPGuiActions.log
• This ID needs to be entered in MTPGuiActions.cfg which can be found in the etc/PDFOfficeTool folder next to the executable of pdfToolbox or pdfaPilot Desktop or Server
• Within MTPGuiActions.cfg the options of the dialog handling is described

• For trouble shooting PDF documents can be converted directly to PDF. Thus more detailed error messages are displayed.
• The command line application that performs the conversion can be found in the etc/PDFOfficeTool folder next to the executable of pdfToolbox or pdfaPilot Desktop or Server
• Therefore the following call has to be executed on the command line:
  • ../MTPOffice <path to the office document> -1 <path to the user folder>
  • Example: C:\Program files\callas pdfToolbox Server 5\cli\etc\PDFOfficeTool\MTPOffice.exe C:\test.doc -1 C:\Documents and Settings\testuser\AppData\Roaming\callas software\callas pdfToolbox CLI 5

• Close all open OpenOffice instances before processing with pdfToolbox 4 or pdfaPilot 2.
• Please keep in mind the known restrictions of OpenOffice.org regarding cases where umlauts from Type1 and OpenType fonts might not be output correctly. You will find more information on the current state of this issue on OpenOffice.org.

• Please verify that OpenOffice is installed inside the default installation path (e.g. ”/Applications/OpenOffice.org” on Mac OS X systems) - if it is not, please re-install it to this location.

• A recommended environment, where OpenOffice support has been tested thoroughly, is Ubuntu 10.04 LTS (also known as “Ubuntu Lucid Lynx”).
• Additionally to OpenOffice.org 3, the following packages need to be installed as described below:
  • sudo aptitude install openoffice.org-java
  • sudo aptitude install ure
  • sudo aptitude install openoffice.org-headless
• Processing of OpenOffice documents requires at least JRE 1.5 (Java Runtime Environment).
• In case of a manual OpenOffice.org installation the $PATH environment variable has to be extended by the directory which contains the OpenOffice.org executable (soffice).
• Example (assuming that OpenOffice.org has been manually installed below the /opt directory):
  • find /opt -name soffice
• The find command responds with something like:
  • /opt/openoffice.org3/program/soffice
• Now the $PATH environment variable has to be extended as shown below:
  • PATH=/opt/openoffice.org3/program:$PATH
• Afterwards it should be verified that the soffice executable is found in the expected place. The command:
  • which soffice
• should now respond with the path located by the find command above:
  • /opt/openoffice.org3/program/soffice

• A page range can not be specified as it is also via manual PDF export, the parameter Page range (pagerange) does not have an influence.
• Images are exported with a resolution of 72 ppi as it is also via manual PDF export, the parameter Print (topdf_print) does not have an influence.
• Documents of iWork '08 Pages can not be processed with pdfToolbox Server application or pdfaPilot Server application because of a changed file format (file packages of Pages version 3 and earlier).

• If a PostScript or EPS file can not be converted to PDF a log file named mtpps.log is placed in the user folder. It contains information about the conversion problem.
• ICC profiles referenced in a PDF settings file need to be copied into the operating system folder for ICC profiles, e.g.:
  • Windows: C:\Windows\system32\spool\drivers\color
  • Mac OS X: /Macintosh HD/Library/ColorSync/Profiles
• A Color settings file (.csf) that is referenced in the PDF settings file is not necessary for the processing.

In case your problems cannot be solved with these instructions, please send an email with the file to be converted and detailed information on your system environment to support@callassoftware.com.