Limitations

edit

Creating documents

  • The content builder breaks the lines of a text box and of the cells of a table with the Unicode line breaking algorithm, without a dictionary: the languages written without spaces between their words (Thai, Lao, Khmer, Burmese) are broken between their characters only when a word does not fit. It does not apply the bidirectional algorithm to the lines.
  • The cells of a table of the content builder (PdfTable) hold text: no image, nested table or cell that spans several rows; the tables of a flow document have them. The justified lines stretch the spaces only.
  • A flow document (PdfFlowDocument) does not hyphenate, nor break with a dictionary. It reorders the runs of a right-to-left paragraph, not the characters of different directions inside a run of a standard font. A table row taller than a page goes beyond the bottom margin. It has no form fields.
  • The standard 14 fonts show the characters of WinAnsiEncoding (Symbol and ZapfDingbats their own); other characters need an embedded font.
  • The fonts with CFF2 outlines, the bitmap fonts and the instances of variable fonts are not embedded.
  • The appearances the API writes for the values of form fields use the font of their default appearance when the form knows it, otherwise the standard 14 fonts: the fields of a saved document that use an embedded font need the font again to be filled (Use an embedded font).
  • A page copied from another document is not tagged: the structure tree belongs to the document of the page.

Reading and extracting

  • The documents encrypted for certificates (the public-key security handler) need RSA certificates: the elliptic-curve recipients (key agreement) are not supported. Their crypt filters share one key: when the recipients are in several crypt filters, those of the streams are used.
  • The text extraction does not recognize the text of scanned pages. Its reading order of the layout (Read the columns in order) finds the columns from the blank spaces of the page: it reads them from left to right, and keeps the order of the content for the text written vertically.
  • The library reports the permissions of an encrypted document, but does not enforce them.
  • The folders of a portfolio are read, not created, and the files are not associated with their folder. The actions without a class of their own (threads, sounds, movies, renditions, transitions, 3D views, rich media) are read as dictionaries. The library does not run the actions, except the scripts of the form fields (Form scripts).
  • A document opened over HTTP reads its whole page tree, so the dictionaries of all its pages are downloaded when the pages are first used; the hint tables of a linearized file are not read.
  • A file larger than 2 GB is read with OpenSeekable: Open(path), Open(stream) and OpenAsync read the file into one array, which cannot be larger than 2 GB. One stream cannot be larger than 2 GB.
  • A file larger than 2 GB is written by Save, SaveAsync, SaveIncremental and SaveIncrementalAsync. ToByteArray, a linearized file and the signatures are built in one array, so they are limited to 2 GB. The offsets of a cross-reference table have 10 digits: a file whose objects are after 9,999,999,999 bytes needs a cross-reference stream (UseObjectStreams), and cannot be updated incrementally if it has a table.

Conformance and signatures

  • The save checks what the conformance levels require of the document as a whole. The content (the order of the structure, the alternate descriptions, the colors of the annotations of PDF/A-1, the values of the numbers) must follow the other rules of the level: validate the documents with veraPDF.
  • A visible signature is a new signature field: an existing signature field that is not signed yet keeps its widget, and the library does not draw an appearance for it.
  • The verification of a signature does not decide whether the signer is trusted: the application builds the certificate chain.
  • The writer encrypts the embedded files with the method of the other streams.
  • A linearized file cannot be encrypted, has no object streams, and is built in memory before it is written. It has no thumbnail hint table: the thumbnails of the pages, if any, are counted with the objects of their pages.

Converting to PDF/A

  • ConvertToPdfA converts to PDF/A-2 and PDF/A-3, levels b and u, and level a for a document that is tagged (AutoTag tags one, from a guess of its layout). It does not convert to PDF/A-1, which has no transparency, or to PDF/A-4.
  • AutoTag puts a text operator in one element, does not reorder the content, and finds the tables from their rules only: see Tagging existing documents.
  • It embeds substitutes for the Latin standard fonts only, and has no CMYK profile: see What it cannot fix.

Redaction

  • Redact does not change the content of the tiling patterns, the soft masks, the glyphs of Type 3 fonts and the appearances of the annotations it keeps, nor the text outside the pages (metadata, bookmarks, the alternate descriptions of the structure elements): see Redaction.
  • A path that crosses an area is clipped, not cut: its coordinates stay in the file. A redacted image is stored again in sRGB.

Rendering

  • The renderer composites the page in sRGB, for a screen; overprinting is simulated when the options ask for it (Print production), with a simple model of the inks, and the colors of images and shadings are separated from their RGB colors. The other parameters of the output device (black generation, undercolor removal) are ignored.
  • The halftones are ignored unless the options ask for them. They are then applied to the red, green and blue components of the image, to fully opaque objects only; the screens of the other colorants, AccurateScreens and the named device halftones are not used (see Halftones).
  • FlattenAnnotations draws the appearances in the rectangles of the annotations: the NoZoom and NoRotate flags are not applied. The appearances UpdateAppearance draws for the free texts use the standard 14 fonts, and draw the borders of the shapes without their cloudy effect.
  • The appearances generated for the annotations that have none are simple: their text is not wrapped, a rich text value is drawn with the standard 14 fonts, and the alignment of a text is estimated without the metrics of its font (see Layers and annotations).