Skip to content

16.2.2

📅 2024-07-31

Starting with this release, you can download the OCR SDK from the IRIS download center as NuGet packages. These packages are in addition to the platform-specific packages. You can download them and then reference the NuGet packages directly in your projects.

NuGet packages are organized as follows:

Five NuGet packages allow you to import all elements for a platform by using a single dependency.

  • iDRS.macOS includes all .NET components, native runtimes, and assets that you need to build an application for macOS.
  • iDRS.Linux-x64 includes all .NET components, native runtimes, and assets that you need to build an application for Linux and run it on x64 hardware.
  • iDRS.Windows-x64 includes all .NET components, .NET Framework, native runtimes, and assets that you need to build an application for Windows and run it on x64 hardware.
  • iDRS.Windows-x86 includes all .NET components, .NET Framework, native runtimes, and assets that you need to build an application for Windows and run it on x86 hardware.
  • iDRS.Windows includes all .NET components, .NET Framework, native runtimes, and assets that you need to build an application for Windows and run it on x86 or x64 hardware.

These NuGet packages contain only dependencies. They are provided for convenience to simplify integration.

Six other NuGet packages include the elements required by the convenience NuGet packages:

  • iDRS.NET contains iDRS .NET and .NET Framework runtimes and product documentation.
  • iDRS.runtime.<Platform-Arch> contains the native runtimes for the specific platform or platform-architecture.
  • iDRS.assets contains iDRS resources files.

If you import one or more convenience NuGet packages, you do not need to import content NuGet packages.

The last NuGet package includes the source code for the sample iDRS applications (CsReader, CsBarcode, and CsImage2Html). This NuGet contains only the sample source code and does not depend on iDRS. A Readme file in the NuGet gives instructions to use the sample code.

With this new version, our high-quality OCR engine (HQOCR) now supports Japanese. This HQOCR engine completely replaces the previous engine for processing documents in this language.

This switch to our cutting-edge engine will bring significant improvements in performance and accuracy for challenging documents such as low-resolution images, magazines, or newspapers, as well as a slight improvement in accuracy for good- quality scans.

As a result of the replacement of the Japanese OCR engine, the following resource files have been added or removed:

Resource fileStatus
japanese_rnn_engine.binNew/added
net_japanese_rnn_hori.binNew/added
net_japanese_rnn_vert.binNew/added
japanese.binRemoved
japanese_bigrams.binRemoved
japanese_duo.binRemoved
japanese_features.binRemoved
japanese_features_fast.binRemoved
japanese_features_one_candidate.binRemoved
japanese_font_features.binRemoved
japanese_rosetta_same_proba.binRemoved
japanese_same_proba.binRemoved
japanese_similar_characters_differentiation.binRemoved

The extended font set is the default in this release. It replaces the historical set of three standard Latin fonts. The following resource is removed:

Resource fileStatus
fontmetrics_ec.binRemoved
Internal IDDescriptionService desk IDs
IDRSRD-6391iDRS .NET leaks memory when parsing object arrays
IDRSRD-6473The iDRS SDK does not output the same number of zones during zonal if no font information is requested
IDRSRD-6509iDRS exceptions source should not contain an absolute path
IDRSRD-6858The iDRS can print message on console during OCR, when missing resource file
IDRSRD-7491Cell’s text alignment is not properly set in iDRS XLSX output for some specific images
IDRSRD-7560The iDRS should propose iterators in its Array class
IDRSRD-8293The iDRS does not detect the correct orientation for a specific image
IDRSRD-8294TheiDRS sometimes recognizes letter ‘O’ instead of Zero next to currency (dollar) signISD-33781
IDRSRD-9163The iDRS does not output correct paragraph position on a specific image
IDRSRD-9192The iDRS does not use the correct font metrics file for default settings
IDRSRD-9206The iDRS crashes while deskewing a very small image
IDRSRD-9233The iDRS can keep a lot of memory allocated when processing multiple images with the same CTextRecognition object
IDRSRD-9240Language detection ‘allowed’ list should support regional variants
IDRSRD-9243iDRS memory increases when setting SetMemoryThreshold in CPageCollectionStorageOptions
IDRSRD-9250The iDRS crashes when exporting to Docx with FontInfoComputation set to None
IDRSRD-9267The iDRS throws an exception when recognizing a specific image with new page segmentationISD-34288
IDRSRD-9271OCR alternatives are not provided when new page segmentation is activated
IDRSRD-9275The iDRS triggers an exception while processing XLSX output on a specific image
IDRSRD-9281The iDRS creates Editable docx with incorrect text direction on a Trad. Chinese image, when using new segmentation
IDRSRD-9295iOS SmartCapture sample App does not position properly vertical text on the OCR review screen
IDRSRD-9314The iDRS developer guide should include some tips explaining how to output best quality XLSX documents
IDRSRD-9318Conversion to Excel single table of a specific file could be improved
IDRSRD-9347OCR accuracy is degraded on high resolution (>300 dpi) documents
IDRSRD-9379Documentation for SetEmptyFormsDetections needs to be updatedISD-34648
IDRSRD-9396The iDRS leaks small chunks of memory when accessing page sections using .NET APIISD-34638
IDRSRD-9403The iDRS should group text in fewer textboxes when converting documents to docx Editable layout
IDRSRD-9426The iDRS crashes when processing the attached PDF with new page segmentation activatedISD-34948
IDRSRD-9435The iDRS crashes when processing a specific image with new page segmentation activatedISD-34967