DC 6.0 Formats - Limitations

The transcode system has some known limitations:

• Fonts: LibreOffice is used to convert Office documents (Word, Excel, PowerPoint), LibreOffice documents, and Visio documents to PDFs. Renditions of image formats, such as the thumbnail format, are then generated from this PDF. However, only a limited set of fonts is available, meaning that the fonts in these generated PDFs and images might differ from the fonts of the input files.

  • The standard fonts included with LibreOffice in Linux distributions are available. A list of these fonts can be found here: https://wiki.documentfoundation.org/Fonts. Note that the fonts 'OpenSymbol' and ‘Source Sans Pro’ are currently not available with the LibreOffice Linux distribution used in the transcode system.

  • Microsoft TrueType core fonts, available from https://packages.debian.org/sid/ttf-mscorefonts-installer, are also available.

• txt to image transcoding: ImageMagick is used to convert txt files to images. If an image format is defined without a custom conversion command, the transcode system can create renditions of txt files in this image format. However, if an image format is defined with a custom conversion command, it is most likely not possible to get renditions of txt files in this image format.

  • This is the case since most custom conversion commands have the form [%infile%] <parameters> [%outfile%], but to create image renditions of txt files, the following command format must be used: TEXT:[%infile%] <parameters> [%outfile%]. This, however, will not work for anything else than txt files.

  • If a custom conversion command is used, and the txt to image transcoding fails, the logs will contain the following error: System.Exception: Failed to transcode with custom ImageMagick command\nData: {\"exitCode\":1,\"stdErrorContent\":\"magick: improper image header ....

  • To support image renditions of txt files, please configure your image formats without using the custom conversion command parameter. This is recommended in general.

• ifc: Aspose.CAD is used to convert ifc files to images and PDFs. Multiple versions of the ifc file format exist. Currently, only versions 2.3 and 4.0 are supported.

• indd to pdf transcoding: We support extracting the page images that are stored as metadata in the InDesign file by Adobe InDesign. Note that only two images are saved by default by Adobe InDesign, but the file settings withing InDesign can be modified to save images of all pages.