Requirements for conversions to PDF

pdfaPilot offers 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.

Supported applications and files

Application Operating system As of pdfaPilot version
  • Microsoft Word 2007
  • Microsoft Word 2010 (32bit and 64bit)
  • Microsoft Excel 2007
  • Microsoft Excel 2010 (32bit and 64bit)
  • Microsoft PowerPoint 2007
Windows 2.1
  • Microsoft PowerPoint 2010 (32bit and 64bit)
  • Microsoft Publisher 2007
  • Microsoft Publisher 2010 (32bit and 64bit)
  • Microsoft Visio 2007
  • Microsoft Visio 2010 (32bit and 64bit)
  • Microsoft Project 2010 (32bit and 64bit)
Windows 2.3
  • Microsoft Word 2013 (32bit and 64bit)
  • Microsoft Excel 2013 (32bit and 64bit)
  • Microsoft PowerPoint 2013 (32bit and 64bit)
  • Microsoft Visio 2013 (32bit and 64bit)
  • Microsoft Publisher 2013 (32bit and 64bit)
  • Microsoft Project 2013 (32bit and 64bit)
Windows 5.0
  • Microsoft Word 2011
  • Microsoft Excel 2011
  • Microsoft PowerPoint 2011
  • iWork '09 Pages
Mac 2.4
  • Microsoft Word 2016/365
  • Microsoft Excel 2016/365
  • Microsoft PowerPoint 2016/365
  • Microsoft Visio 2016/365
  • Microsoft Publisher 2016/365
  • Microsoft Project 2016/365
Windows
[MS Office on Mac until version 9.1.326]
7.0
  • Microsoft Word 2019
  • Microsoft Excel 2019
  • Microsoft PowerPoint 2019
  • Microsoft Visio 2019
  • Microsoft Publisher 2019
  • Microsoft Project 2019
Windows
[MS Office on Mac until version 9.1.326]
8.0
  • Microsoft Word 2021
  • Microsoft Excel 2021
  • Microsoft PowerPoint 2021
  • Microsoft Visio 2021
  • Microsoft Publisher 2021
  • Microsoft Project 2021
Windows 11.0
  • OpenOffice.org 3.2
Windows, Mac and Linux 2.2
  • OpenOffice.org 3.3
Windows, Mac and Linux 2.3
  • OpenOffice.org 4.x
Windows, Mac and Linux 5.0
  • LibreOffice 4.x
Windows, Mac and Linux 5.0
  • LibreOffice 5.x
Windows, Mac and Linux 6.2
  • LibreOffice 6.x
Windows, Mac and Linux 8.0
  • LibreOffice 7.x
Windows, Mac and Linux 9.0
  • PostScript and EPS files
All Platforms 2.4
  • Image files
All Platforms 2.4
  • XPS files
Windows 6.0

Supported file types

Application
File type

Windows Mac Linux
Microsoft Word
.doc .docx .dot .dotx .dotm .rtf .txt .xml .vcf .ics .wpd
.doc .docx .txt

Microsoft Excel
.xls .xlsx .xlsm .xlt .xltx .xltm
.xls .xlsx

Microsoft PowerPoint
.ppt .pptx .pps .ppsx .pot .potx .potm .ppa .ppam
.ppt .pptx

Microsoft Visio
.vsd .vdx .vdw .vss .vsx .vtx (v.11) .vsdx (v.11)


Microsoft Project
.mpp .mpt .mpd .mpw .mpx


Microsoft Publisher
.pub


OpenOffice/LibreOffice Writer
.odt .ott .sxw .stw .doc .rtf .sdw .vor .txt .pdb .xml .psw .docx .docm .dotx .dotm .602 .wpd .hwp
OpenOffice/LibreOffice Calc
.ods .ots .sxc .stc .dif .dbf .xls .xlt .sdc .vor .slk .csv .pxl .uos .xlc .xlm .xlw .sdc .xlsb .xlsm .xlsx .xltm .xltx .wb2
OpenOffice/LibreOffice Impress
.odp .otp .sxi .sti .ppt .pot .sxd .sda .sdd .vor .uop .odg .cgm .pptm .pptx .potm .potx
OpenOffice/LibreOffice Draw
.bmp .emf .pcx .pgm .wmf (from version 8.2)
iWork '09 Pages

.pages

PostScript and EPS files
.ps .eps .prn
Image files
.tiff .tif .jpeg .jpg .png
.gif .psd (from version 10.1) .psb (from version 11)
HTML
.html .htm .svg

File types that require additional parameters:

Application File type

Windows Mac Linux
Email
.msg .eml .emlx
When emails are converted also any attachments are converted, compressed archives (.zip, .gz, .7z, .rar) are uncompressed.

Further information on the settings for email conversion here.

General

  • All Office-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.
  • 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 4 or newer - this is not automatically installed with the regular Windows Update but belongs to the optional updates.
  • Please ensure, that the Microsoft Visual C++ Redistributable Packages for Visual Studio (2013, 2017, 2019) were properly installed by the callas installation package. Only the 32bit versions of the runtime libraries are needed because the internal conversion tool is a 32bit application.
  • 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 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.
  • Microsoft Office files are not processed via OpenOffice/LibreOffice by default under Windows and MacOS if no Microsoft Office is installed on the system. For Server/CLI, processing of such MS Office files by OpenOffice/LibreOffice can be forced using the --topdf_forceopenoffice parameter.
  • Since in Microsoft Word, autocorrection is activated by default, we recommend to deactivate spellchecking, grammar checking and hyphenation via the Word options to speed up the Office conversion.

Microsoft applications

  • 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.
  • Install the latest service pack for Microsoft Office.
  • When updating the Microsoft Office Suite it is recommended to deinstall previously installed version before to ensure all registry entries are removed and properly set when the new installation of Office takes place. Especially when installing Microsoft Office 2010 on a system with an existing Microsoft Office 2007 such registry entries seems to remain. See Microsoft knowledge base for details how to uninstall.

Word

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”.

Excel

  • 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.
  • To ensure conversion, the print spooler has to be active. This is the case when the Excel preview shows the content. Otherwise the spooler has to be started in the “Services” configuration of the system settings. After doing this, the “Microsoft XPS Document Writer” shows up in the print dialog of Excel.

Powerpoint

It is not recommended to use parallel conversion of PowerPoint files with MS Office, as this can sometimes lead to problems, instead sequential processing works stable.

Mac

  • 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.

Dialog handling

  • 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 pdfaPilot Desktop or Server
  • Within MTPGuiActions.cfg the options of the dialog handling is described

Usage when running as a service

Sometimes problems may occure when running pdfaPilot as a service with Microsoft Office. Automation is not supported by Microsoft officially, but the following workaround was successful in most cases:

  • Create the following folders (with appropriate permissions) on your system:
    • Windows Server 2012 + later:
      • C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache
    • Especially when running Office 32Bit on x64 systems, the following folders are required as well:
      • Windows x64: C:\Windows\SysWOW64\config\systemprofile\Desktop
      • Windows x86: C:\Windows\System32\config\systemprofile\Desktop
      • Please NOTE:
        For smooth operation, the folders named above need to be restored after a Windows Update.
  • For the Office/Excel conversion in a service setting, it is necessary to set up a default printer, especially when working with the "System" account.
  • For Microsoft Excel, Microsoft Word and Microsoft PowerPoint the DCOM Identity "The launching user" must be selected. For Microsoft Visio the DCOM Identity "The interactive user" needs to be selected.

OpenOffice and LibreOffice

  • Close all open OpenOffice and LibreOffice instances before processing with pdfaPilot.
  • 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.
  • Only LibreOffice or OpenOffice may be installed.
  • For Windows only the 32-bit versions of LibreOffice and OpenOffice are supported (before pdfaPilot 9/pdfEngine 11).
  • From pdfaPilot 9/pdfEngine 11 onwards with the 64bit variant on Windows, the Libre/OpenOffice has to be 64bit as well (and 32bit when the 32bit variant of pdfaPilot/pdfEngine is installed).
  • For Non-Windows systems (Mac, Linux..) the JDK needs to be installed: https://www.oracle.com/java/technologies/javase-jdk14-downloads.html

Mac

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.

On Mac the following default installation/location are supported (in this order - first wins):

  • /Applications/LibreOffice.app
  • /Applications/OpenOffice.app
  • /Applications/OpenOffice.org.app

Linux

  • Support for Office Conversion has been tested thoroughly on Ubuntu 14.04 LTS (Server) with the default installation of LibreOffice and also with an OpenOffice installation.
  • On Debian based Linux distributions (like Ubuntu or Mint), the required LibreOffice packages are installed via the package manager or via the command line as shown below:
    • sudo aptitude install libreoffice
    • (please substitute 'libreoffice' by 'openoffice' if you prefer OpenOffice)
  • On other linux distributions or with other OS versions it might be required to search for packages with different names. E.g install everything found with the following search terms:
    • libreoffice (or openoffice)
    • uno
    • ure
    • headless
  • Some distributions, like e.g. Debian 10 ("Buster") may require to install the additional "libreoffice-java-common"package:
    • sudo apt install libreoffice-java-common

iWork '09 Pages

  • 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 pdfaPilot Server application because of a changed file format (file packages of Pages version 3 and earlier).

PostScript and EPS files

  • ICC profiles referenced in a PDF settings file (.joboptions) need to be copied into the operating system folder for ICC profiles, e.g.:
    • Windows:
      C:\Windows\system32\spool\drivers\color
    • MacOS:
      /MacOS HD/Library/ColorSync/Profiles
  • The application will also look into the following folders for ICC profiles: 
    • /Library/Application Support/Adobe/Color/Profiles/Recommended
    • /Library/Application Support/Adobe/Color/Profiles
    • /System/Library/ColorSync/Profiles
  • Alternatively, you can put ICC-files for PostScript to PDF in the subfolder of the application:
              .../etc/PDFPSTool/ICCProfiles
  • A Color settings file (.csf) that is referenced in the PDF settings file is not necessary for the processing.

Additional settings with limited user rights

In general it is recommended to grant the respective service user administrator privileges. If this level of rights can not set due to internal regulations, some additional settings within the operating system are recommended.

The following folders should allow the user the respective access right:

For 64-bit machines
C:\Windows\Temp
Modify
C:\Windows\syswow64\config
Read
C:\Windows\syswow64\config\systemprofile
Read
C:\Windows\syswow64\config\systemprofile\
AppData
Modify
C:\Windows\syswow64\config\systemprofile\
Desktop
Modify (Create it, if it does not exist)
C:\Windows\syswow64\config\systemprofile\
AppData\Local\Microsoft\Windows\
INetCache
Modify (Create it, if it does not exist)
For 32-bit machines
C:\Windows\Temp
Modify
C:\Windows\system32\config
Read
C:\Windows\system32\config\systemprofile
Read
C:\Windows\system32\config\systemprofile\AppData
Modify
C:\Windows\system32\config\systemprofile\Desktop
Modify (Create it, if it does not exist)
C:\Windows\system32\config\systemprofile\
AppData\Local\Microsoft\Windows\
INetCache
Modify (Create it, if it does not exist)

Office conversion

Additional settings

  • Set the 32-bit folder preferences (detailed above) in addition to the 64-bit preferences on 64-bit systems running 64-bit versions of Microsoft Office
  • Set the default printer to XPS Document Writer

DCOM settings

  • Launch DCOMCNFG by using:C:\WINDOWS\SysWOW64> mmc comexp.msc /32
  • Go to Computers > MyComputer > DCOM Config.
  • Right-click the application that you want to automate.The application names are listed in the table below:
Application
DCOM Name
Microsoft Access 2007/2010/2013/2016
Microsoft Access Application
Microsoft Excel 2007/2010/2013/2016
Microsoft Excel Application
Microsoft Office Word 2007
Microsoft Office Word 97 -
2003 Document
Microsoft Word 2010/2013/2016
Microsoft Word 97 - 2003
Document
  • On some systems Microsoft Word is not displayed and you will have to use {00020906-0000-0000-C000-000000000046} instead.
  • Click Properties to open the property dialog box for this application.
  • Verify Identity and Security tabs

Note

For Microsoft Excel, Microsoft Word and Microsoft PowerPoint the DCOM Identity "The launching user" must be selected.

For Microsoft Visio the DCOM Identity "The interactive user" needs to be selected.

Slow conversion on systems without Internet connection

Some customers experienced long processing times on maschines without an Internet connection, especially when using MS Office 365 or MS Office 2016/2019.
The following registry key did the trick for them:
[HKEY_CURRENT_USER\Software\Microsoft\Office\Common\ClientTelemetry] "DisableTelemetry"=dword:00000001
This might be related to:
https://docs.microsoft.com/en-US/DeployOffice/compat/manage-the-privacy-of-data-monitored-by-telemetry-in-office
We haven't found if there are official settings available - therefore we recommend an intensive testing on such systems before this key is used in a production environment as we can not estimate if there are any side effects.

Still problems when converting?

In case you are having trouble with 'Convert to PDF', please contact our support team and simply fill out this form.