Version 26.5 Release Notes - SelectPdf Library for .NET | |
Tagged (PDF/UA-1) and PDF/A-3a conversions of real web pages now conform, text search works in every script, and the Chromium engine converts pages that navigate while they are printed.
Accessible PDF from real web pages - tagged (Tagged = true, PDF/UA-1) and PDF/A-3a conversions of real-world pages now pass validation: the page's decorative paint (backgrounds, borders, separators) is marked as an artifact, content the engine left outside the structure is attached to the element it belongs to, a picture drawn twice is described once, and grouping elements hold their content the way the standard requires. Checked with veraPDF on GitHub, the W3C home page and Wikipedia in English, Chinese, Arabic, Hebrew and Japanese, with the Chromium and Blink engines. See Accessible PDF and PDF/A.
Figures - an HTML <figure> around one picture is tagged as that picture, with the picture's alternate text and the caption inside it; a figure around no picture or several is tagged as a group with its caption as a paragraph. Earlier versions gave the figure the placeholder description "Image".
Text search in every script - PdfToText.Search finds text in non-Latin scripts (Cyrillic, Chinese, Japanese, Korean, Hindi, Thai, Arabic, Hebrew), and right-to-left terms typed in reading order. Earlier versions found only text in the Windows code page.
Arabic text extraction - letters the Chromium engine draws as shaped glyphs are extracted inside their words, so far fewer words come out split.
Extracted text no longer contains the invisible bidi embedding characters (U+202A - U+202C) around right-to-left text.
With the Chromium and Blink engines, an internal-link destination whose name is longer than 127 bytes (an anchor in a Japanese heading, for example) is renamed spdfdest1, spdfdest2... and the links to it are updated: PDF/A does not allow longer names.
A link to a destination the page does not define (a "skip to content" link with an empty target, or an anchor that is not on the page) keeps its area but no longer points anywhere.
A tagged or PDF/A-3a conversion of a page with alternate text outside Latin-1 (Arabic, Chinese, Hebrew or Japanese pages, for example) no longer fails to save with "The method parameter cannot be null".
PDF/A conversions of pages with long anchor names no longer fail PDF/A validation.
With the Chromium engine, a page that navigates to another address while it is being printed no longer fails with "PrintToPDF failed".