Skip to content

16.2.6+82

📅 2025-04-18

Support for PDF/UA accessibility compliance

Section titled “Support for PDF/UA accessibility compliance”

A new property has been added to CPdfOutputParams: CPdfOutputParams.AccessibilityConformance.

When this property is set, the generated PDF will conform to the PDF/UA standard, ensuring enhanced accessibility for assistive technologies.

Following the recent updates to the DOCX Exact and Editable layouts, the Flowing layout has now received significant enhancements.

All improvements made to the Editable layout since version 16.0 have also been incorporated into the Flowing layout, substantially increasing the quality of the generated DOCX outputs.

To facilitate the matching between input and output zones during zonal OCR, an Identifier has been introduced to the following classes:

  • COcrZoneDescription: upon creation, each instance is assigned a unique identifier. This identifier can be modified to provide a more meaningful name.

  • CPageZone: when zonal OCR is performed, the identifier from each COcrZoneDescription is propagated to the corresponding CPageZone instance generated.

    • For full page OCR, the CPageZone.Identifier will remain empty.

Example of usage:

// Define a zone where we expect an IBAN value
COcrZoneDescription objZoneDescription1 = COcrZoneDescription::Create(ZoneType::Text, rc1);
objZoneDescription1.SetIdentifier("IBAN");
....
// Do zonal ocr recognition
....
// Retrieve IBAN result
CPageZoneArray::iterator itIban = std::find_if(xZones.begin(), xZones.end(), [](const CPageZone& obj) { return obj.GetZoneType() == ZoneType::Text && obj.GetIdentifier() == "IBAN"; });

N/A

Internal IDDescriptionService desk IDs
IDRSRD-9880The iDRS throws an exception when converting a specific document to DOCX
IDRSRD-9870The iDRS throws an exception when creating a DOCX document from a specific Hebrew image
IDRSRD-9835The iDRS creates an invalid DOCX output from a specific Arabic document
IDRSRD-9831The iDRS generates characters with incorrect stretch factors when processing documents with English and Korean languages
IDRSRD-9825The iDRS seems to be hanging indefinitely when recognizing specific imagesISD-36630
IDRSRD-9822The iDRS crashes in CTextRecognition.RecognizeText on a specific image
IDRSRD-9820The iDRS throws an exception when creating a flowing DOCX in specific case
IDRSRD-9813The iDRS can randomly crash when setting multiple thread for in-page processing
IDRSRD-9800iDRS 16.2.5+119 consumes an unexpected amount of memory when running OCRISD-36544
IDRSRD-9791Accuracy on Zonal OCR for Korean language drops by 7% on customer benchmark
IDRSRD-9718The iDRS merges 2 clearly separate tables on a given document
IDRSRD-9672Email and web links are not clickable in XLSX documents generated by iDRS
IDRSRD-9628Language detection feature requires really unexpected resources
IDRSRD-9588The supported character set of Japanese HQOCR lacks some expected characters
IDRSRD-9479The iDRS generated DOCX documents with incorrect paragraph tabulations
IDRSRD-9359The iDRS logic for selection of Word paper size should be improved
IDRSRD-9277The iDRS inserts two spaces between words when exporting Arabic documents to docx with flowing mode
IDRSRD-6469skew detection failure on grayscale image
IDRSRD-7671Table elements not properly positionned in docx output
IDRSRD-5873Layout of iDRS docx output with flowing text should be improvedISD-17602, ISD-33550
IDRSRD-5545The iDRS mis-recognizes some text in a specific japanese document
IDRSRD-6962The iDRS should support PDF/UA standardISD-35915, ISD-34203, ISD-13201, ISD-21814
IDRSRD-4742Numeric characters mismatched for Japanese OCR in some specific images