PrizmDoc® Viewer v13.28 Release - Updated
PrizmDoc Viewer / Troubleshooting / Document Viewing Issues
In This Topic
    Document Viewing Issues
    In This Topic

    Introduction

    This section outlines possible reasons why some documents may render differently than expected:

    Note for all Formats

    Viewing pages in documents which have more than 10,000 pages

    PrizmDoc Viewer currently does not support viewing pages past the 10,000th page.

    As a possible workaround, consider splitting the original document into a number of smaller PDF files. For example, use 1,000 pages per document for viewing. You can use the PrizmDoc Content Conversion Service API for splitting an original document into smaller files. Specify a PDF as the output format and specify the desired page range for each resulting PDF.

    Document fidelity differences when transitioning from traditional Linux platforms to the PrizmDoc Docker image or updating an existing PrizmDoc Docker image to the latest version

    The PrizmDoc Docker image uses the latest Ubuntu version. This may cause some fidelity differences when converting certain source files to PDF. Also, if you transitioned from a traditional Linux install to the PrizmDoc Docker image, and added custom fonts such as Asian fonts, you will need to add those fonts to the PrizmDoc Docker image. For instructions, see the "Adding fonts and packages to the container" section in Using Docker.

    Text initially shows unexpected symbols when loading

    Browsers initially render with the use of a system font as opposed to the use of the associated embedded web font. Different browsers may use slightly different strategies in displaying text while web fonts are loading. During the time when browsers transition from system fonts to embedded fonts the text may appear illegible with unrecognizable characters. Each browser may handle this situation differently and certain documents with high numbers of SVG elements clustered in a region of the document can increase the loading time of a web font and are more likely to produce this effect.

    Related FAQs