PrizmDoc® v14.1 Release - Updated
PrizmDoc / Support & Troubleshooting / Document Viewing Issues / PDF Files
In This Topic
    PDF Files
    In This Topic


    This section outlines possible reasons why some PDF documents rendered differently than expected.

    Fonts are pixelated

    Some PDF files contain "Type 3" fonts with glyphs (defined by PDF graphics operators) that compose squares rather than arcs. There is a limitation in PrizmDoc's PDF rendering engine where it uses large squares when converting such fonts to SVG format, which results in pixelated display.

    If viewing documents that contain Type 3 fonts is important, we recommend you consider using one of the following approaches:

    Dynamic XFA PDF forms document content is not rendered

    PrizmDoc does not support rendering Dynamic XFA (XML Forms Architecture) PDF forms. Messages such as "Please wait... If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document." or "To view the full contents of this document, you need a later version of the PDF viewer." will be displayed instead of actual form content.

    The document displays extra space or extra content at the edges

    In PDF documents, the MediaBox property (defines the dimensions of the media, such as paper for printing the document) is usually equal to the CropBox property (defines the area that should be visible to the user). However, in some PDFs, especially those which were created by pre-print applications, the area specified by the CropBox is smaller than that of MediaBox.

    By default, PrizmDoc renders PDF documents according to the MediaBox, to avoid hiding contents that fall outside of the CropBox. As a result, you might see extra space or extra contents at the edges of the page, compared to other PDF viewers. If you prefer PrizmDoc to render contents according to the CropBox, please set the fileTypes.pdf.pageBoundaries central configuration property to cropBox.

    After changing the fileTypes.pdf.pageBoundaries setting, you must clear your cache in order for the new settings to take effect on files previously converted with the old mode.