IDOL and KeyView OEM 25.3.0
25.3 OEM Release Notes

# Export SDK

## 25.3.0

### New in this Release

- Format detection has been extended, with support for 28 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the Export SDK Programming Guides.

- Format detection has been improved for the following formats:

  - Microsoft Excel Workbooks (versions 4 and 5) (effectively .xlw files) were previously detected as `Excel_Fmt`, but are now detected as the more precise `Excel_Workbook_Fmt`. Microsoft Excel Spreadsheets (up to version 5) (effectively .xls files) are still detected as `Excel_Fmt`.

  - JPEG-LS files were previously detected as `JPEG_File_Interchange_Fmt`, but are now detected as a separate format.

- File Content Extraction now supports CSV files that use semi-colons as the delimiting character.

- Improved performance of character set detection, resulting in faster processing for some formats such as UTF-8 and ASCII encoded plain-text files.
- Significantly improved performance when extracting content from file formats that compress data using the DEFLATE algorithm. File Content Extraction now uses a faster implementation of this algorithm. DEFLATE is used in many common file formats including zip files and Microsoft Office formats (`.docx`, `.xlsx`, `.pptx`).

- File Content Extraction now writes fewer temporary files to disk when processing .docx, .xlsx and .pptx files. This change can improve performance significantly on Windows when you use a virus scanner that scans each temporary file as it is written.

- Performance has been improved for HTML and RSS files.

### Resolved Issues

- (Security update)The third-party expat library has been upgraded to version 2.7.1 to resolve known vulnerabilities, including CVE-2024-8176.

- (Security update)The third-party 7zip library has been upgraded to version 24.09 to resolve known vulnerabilities, including CVE-2024-11612.

- (Security update)The third-party libheif library has been upgraded to version 1.19.8 to resolve known vulnerabilities, including CVE-2024-4131, CVE-2025-43967 and CVE-2025-43967.

- (Security update)The third-party libxml2 library has been upgraded to 2.13.8 to resolve known vulnerabilities, including CVE-2024-56171 and CVE-2025-24928.

- File Content Extraction could terminate unexpectedly (in-process) or return an error (out-of-process) when processing certain RTF files.

- For iWork Numbers files, File Content Extraction would output some numbers with insufficient precision.

- When running in process, File Content Extraction could exit unexpectedly when processing some corrupt Microsoft Excel documents (.xls).

- Processing PDFs with pdfsr was on average slower than in 25.1.0.

- File Content Extraction output was missing spaces for some PDF documents.

## 25.2.0

### New in this Release

- Format detection has been extended, with support for 63 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the Export SDK Programming Guides.

- Text output is now supported for ActiveMime_Fmt documents.

- File Content Extraction can now extract the subfiles of `NuGet_Package_Fmt` files.

- When processing PDF files using the default pdfsr reader, File Content Extraction now extracts the replacement text from ActualText marked-content sequences, instead of the text enclosed by the sequence.

- The Outlook Personal Folders File (PST) reader `pstxsr` is now available on all supported platforms. The reader `pstnsr` is no longer available and OpenText recommends using `pstxsr` instead.

- The ODA third-party library has been upgraded to version 2024.12.

- The libxml2 third-party library has been upgraded to version 2.13.5.

- Precision has been improved in SVG output for AutoDesk_DWG_Fmt and AutoCAD_DXF_Text_Fmt files.

- File Content Extraction now supports export for Design_Web_Format_Fmt files.

### Resolved Issues

- (Security update) File Content Extraction could perform an invalid memory read when processing some PDF files.

- (Security update)File Content Extraction could perform an invalid memory read when processing some MSG files.

- (Security update)File Content Extraction could perform an invalid memory read when highlighting search terms.

- (Security update)File Content Extraction could perform an invalid memory write when processing certain MS_Works_Win_WP_Fmt files.

- (Security update) File Content Extraction could perform an invalid memory write when processing some multi-page TIFF files.

- (Security update)For some crafted input files, kwAD could perform a division by zero.

- (Security update)For some crafted input files of XML-based formats, the reader could perform an out-of-bounds read.

- (Security update)For some crafted input files, kpP97rdr had a memory leak, invalid free and out-of-bounds read.

- (Security update)For some crafted input files, mw6sr had out-of-bounds reads.

- (Security update)For some crafted input files, mw8sr had null dereferences, out-of-bounds reads, an overlapping memcpy, a use-after-free, and an infinite recursion.

- (Security update)For some crafted input files, xlssr had an invalid strtoul, a null dereference, and out-of-bounds reads.

- File Content Extraction could leak memory when processing some RSS files with embedded HTML.

- File Content Extraction returned `KVError_BadInputStream` for a small number of valid PDFs.

- File Content Extraction output incorrect values for Microsoft Excel (xlsx) pivot table caches that contained date, Boolean, error, or empty value types.

- File Content Extraction could potentially perform an overlapping memcpy when processing some GIF files.

- When performing some operations File Content Extraction could read uninitialized memory in a way that did not adversely impact behavior.

- Certain Apple iWork Numbers files could cause File Content Extraction to hang indefinitely in-process, or exit with a timeout out-of-process.

- File Content Extraction could leak memory when processing some PDF files.

- File Content Extraction could leak memory when processing some VSD files.

- File Content Extraction could miss text from some VSD files.

- File Content Extraction could leak memory when processing some MSG files.

- File Content Extraction could leak memory when extracting PST subfiles to MSG.

- File Content Extraction could leak memory when processing metadata from some RTF files.

- File Content Extraction did not handle escaped new lines in vCard (.vcf) files.

- When processing a corrupt EPUB file, File Content Extraction could stop responding in-process, or exit with a timeout out-of-process.

- RMS decryption would occasionally fail due to a sporadic SSL error when contacting the Microsoft server. When this occurs, File Content Extraction now automatically waits for one second and retries.

- File Content Extraction produced header and footer text output for Microsoft PowerPoint documents (.pptx) even when configured not to.

  NOTE: If your File Content Extraction session is not configured to output header and footer text, this change results in File Content Extraction outputting less text.

- Bounding boxes have been improved in cases where `XMLTextPositionGranularity` is set to word, such that they do not overlap with the following word, and do not cover the whitespace between words.

### Notes

- The following readers have been replaced by a single, new, reader (`wpsr`) that is capable of handling multiple word processor formats.

  - `afmsr` - Adobe Font Metrics
  - `axsr` - Applix Asterix
  - `cdsr` - Convergent Technologies DEF Comm. Format
  - `lyxsr` - LyX Word Processor
  - `nnsr` - NBI OASys Net Archive
  - `pfasr` - ASCII Printer and PostScript fonts
  - `pwsr` - PRIMEWORD
  - `swsr` - Informix SmartWare II Word Processor

  When you upgrade, update your `formats_e.ini` configuration file and replace any usage of these readers with `wpsr`.

## 25.1.0

### New in this Release

- Format detection has been extended, with support for 94 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the Export SDK Programming Guides.

- To improve ease-of-use, configuration parameter names in `formats``_e``.ini` have been made case-insensitive. In earlier versions of File Content Extraction, the parameter names were case-sensitive so setting (for example) `kvooprefresh` rather than `kvoopRefresh` would have no effect. The values of Boolean parameters ("True" or "False") are now case-insensitive, and a positive integer such as "1" is accepted instead of "True".

- The C sample programs include makefiles for all supported platforms.

- File Content Extraction can extract comments from ZIP files. ZIP files contain two types of optional comments. The ".ZIP file comment" is associated with the ZIP as a whole, and "file comments" are associated with individual subfiles. In the Filter SDK, document metadata for a ZIP file now includes the .ZIP file comment in the Comments standard field. In the Extract API, subfile metadata for a subfile of a ZIP now includes the file comment for that subfile in the Comments standard field.

- File Content Extraction extracts subfiles from RAR5 containers even when the calculated checksum for a subfile does not match the checksum stored in the container. This is to ensure that subfiles cannot be hidden by maliciously editing the file.

- Improved support for Microsoft Excel Binary (XLSB) files. File Content Extraction now supports XLSB files created using the beta version of Microsoft Excel.

- In XML Export, when you enable position information for PDF documents, you can optionally obtain the information for each individual word.

- The third-party Freetype library has been upgraded to version 2.13.3.
- The third-party ICU library has been upgraded to version 76.1.
- The third-party libpng library has been upgraded to version 1.6.44.

### Resolved Issues

- (Security update) The third-party OpenSSL library has been upgraded to version 3.4.0 to resolve known vulnerabilities, including CVE-2024-6119 and CVE-2024-5535.
- (Security update) The third-party expat library has been upgraded to version 2.6.4 to resolve known vulnerabilities CVE-2024-45492, CVE-2024-45491, CVE-2024-45490 and CVE-2024-50602.
- (Security update) File Content Extraction could return an error (when running out-of-process) or crash (when running in-process) when processing some `OPML_Fmt` files.
- (Security update) There were potential out-of-bounds reads and writes when performing character encoding detection and conversion.
- (Security update) There was a potential out-of-bounds read when processing specially crafted `XFDL_Fmt` files.
- (Security update) There was a potential out-of-bounds read when processing specially crafted `CGM_Binary_Fmt`, `CGM_Character_Fmt`, or `CGM_ClearText_Fmt` files.
- File Content Extraction failed to filter some PDF files that could be opened successfully in Adobe Acrobat.
- Metadata for .MSG files no longer includes the `PR_BODY` field, because it duplicates the filtered or exported text.
- File Content Extraction could fail to extract text from some cells in ODF Spreadsheet files.
- File Content Extraction could output the metadata of some UTF-8 encoded EML files in the wrong encoding.

- Some text from XPS files could be output without whitespace. This has been resolved on platforms other than MACOS_M1, MACOS_X86_64, and WINDOWS_ARM64.

- When a PDF file contained XFA forms with images in them, File Content Extraction could put base64-encoded image data in the output.

- In the Extract API, when running `fpGetMainFileInfo`, `fpGetSubFileInfo` or `fpExtractSubFile` out-of-process, the output structure would be allocated (and need freeing by `fpFreeStruct`) even if the operation failed.

- When processing an encrypted PDF (where printing was restricted), File Content Extraction would decrypt the document but did not decrypt the names of some form fields.

- When extracting a zero-byte subfile of a `PKZIP_Fmt` file to a `KVOutputStream`, File Content Extraction did not open and close the `KVOutputStream`.

- File Content Extraction could terminate unexpectedly when processing some TIFF images with bottom-to-top orientation and uneven strip sizes.

### Notes

- The PDF Export SDK version 25.1 is available only on Windows.

## 24.4.0

### New in this Release

- KeyView format detection has been extended, with support for 93 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- The consistency of text-positioning between platforms has been improved when SVG output is selected.

- KeyView now supports Metadata output for .mht files.

- A new reader, `codesr`, filters code comments (but not the code itself) from a selection of source code file formats. This reader is now the default reader for the formats that it supports. To filter both comments and source code, modify `formats_e.ini` and use the reader `afsr` instead - this will provide the same behavior as earlier versions of KeyView.

- In HTML Export, when you use the `pdf2sr` reader to extract images from pages in a PDF file, you can now configure the size of the images to produce.

- When KeyView detects a zip bomb, it now returns a more descriptive error code.

- The libxml2 third-party library has been upgraded to version 2.13.3.

- The Expat third-party library has been upgraded to version 2.6.2.

- The OpenSSL third-party library has been upgraded to 3.3.1 in most components. The optional cryptographyServices components (which is used for RMS decryption) uses OpenSSL 3.0.8.

### Resolved Issues

- (Security update) Several potential issues with readers were resolved:

  - The `kwAD`, `kpAGrdr`, `xmlsh`, and `kpP40rdr` readers had potential out-of-bounds reads.

  - The `kpP40rdr`, and `mwsr` readers had potential out-of-bounds writes.

  - The `kpAGrdr` and `xlssr` readers had potential memory leaks.

  - The `kpAGrdr` and `kpP40rdr` readers had potential issues that might have led to an interruption of service, or becoming unresponsive.

- For some Microsoft Word 95 files that were created using a later version of Microsoft Word, KeyView could return the `KVError_FormatNotSupported` error.

- When text in a PDF file was added by editing the PDF with Firefox, KeyView could miss the text.

- When KeyView encountered an OLE_Fmt file that did not contain metadata, it could return an error.

- In subfile metadata output, KeyView set incorrect values of `is_superseded` and `has_standard_alternative` for some documents of format MS_OEDBX_Fmt, Lotus_Domino_DXL_Fmt, ENT_Fmt, GWFS_Email_Fmt, Lotus_Notes_NSF_Fmt, MS_OutlookOLM_Fmt, Legato_Extender_ONM_Fmt, or TNEF_Fmt.

- During file format detection, KeyView could mark some PDFs as encrypted when a password was only required to edit, but not to read, the file contents.

- On the MacOS x86 64 platform, the 7z, libheif, and libde265 libraries did not have the correct minimum operating system version set.

- For MP3 files, KeyView did not always convert the metadata strings to the target encoding correctly.

## 24.3.0

### New in this Release

- KeyView format detection has been extended, with support for 30 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- The metadata API provides more information about metadata elements, so that you can identify non-standard elements that have a standardized alternative, and "superseded" elements that exist for backwards compatibility. Using this information, you can avoid processing the same metadata field more than once.

- When using the pdfsr reader, the detection of spaces between words in PDF documents has been improved.

- KeyView can now export video and audio formats supported natively by browsers.

- The third-party Lib ICU library has been upgraded to version 73.2.

- The third-party libpng library has been upgraded from version 1.6.37 to version 1.6.40.

- The third-party zlib library has been upgraded from version 1.2.13 to version 1.3.

### Resolved Issues

- (Security update) A maliciously crafted TIFF file could cause KeyView to temporarily allocate a large amount of memory (CVE-2023-52355).

- (Security update) The third-party libtiff library has been upgraded to version 4.6.0 to resolve security vulnerabilities (CVE-2023-40745, CVE-2023-3618, CVE-2023-2908, CVE-2023-26966, CVE-2023-3618 and CVE-2023-3316).

- (Security update) The third-party freetype library has been upgraded to version 2.13.1.

- (Security update) The third-party JasPer library has been upgraded to version 4.2.1 to resolve CVE-2023-51257.

- (Security update) The third-party ODA library has been upgraded to version 2025.1 to resolve CVE-2023-5179, CVE-2023-5180.

- (Security update) A jump on uninitialized value could potentially occur when processing some PDF files.

- (Security update) The third-party 7zip library has been upgraded to 23.01. This upgrade addresses CVE-2023-31102, and resolves a memory issue in the xz decoder, as well as a number of other issues. It also has potential speed improvements.

- (Security update) When processing some EML files, KeyView could sometimes perform an invalid write.

- (Security update) When processing DWG files, a memory leak could occur.

- (Security update) When using the pstsr reader, the subfile metadata for items within a PST included the PR_STORE_ENTRYID which was set to the location of the PST on disk at the time it was processed by KeyView.

- (Security update) A jump on uninitialized value could occur when processing some files that contained an embedded WMF or EMF file.

- (Security update) A resource leak could occur when processing Microsoft Word documents that contained charts.

- (Security update) When performing OCR on Windows, if the `libopenblas.dll` library was not present in the bin folder but was present in one of the folders on the PATH, KeyView loaded it from the folder on PATH.

- KeyView extracted the subfiles of some CAB files as empty files.

- A jump on uninitialized value could occur when processing some LZH files.

- A jump on uninitialized value could potentially occur when performing format detection on some zip-based files.

- KeyView could not extract subfiles from certain ZIP files that contained inconsistent specified lengths for those subfiles.

- KeyView sometimes exited unexpectedly (in-process) or returned an error (out-of-process) when extracting some self-extracting archives.

- KeyView reported a different subfile time during daylight savings time for zip-based formats when using the multiarcsr reader.

- When KeyView was configured to do detection in-process, if the first session was shut down and a new session started, detecting some iWork files could cause the calling application to exit unexpectedly.

### Notes

- KeyView is no longer available for Linux x86 (32-bit).
- KeyView no longer supports Java 7. The Filter and Export Java APIs require Java 8 to 17. KeyView Export also requires Java 8 to 17 for converting vector graphics to raster images on non-Windows platforms.

## 24.2.0

### New in this Release

- KeyView format detection has been extended, with support for 51 additional file formats. KeyView can now identify more than 2000 unique file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- Performance has been improved for large Rich-Text Format (RTF) files.

- KeyView can now present data from Pipe_Separated_Fmt files as a table.

- Optical Character Recognition (OCR) is now available on MacOS x86-64 platforms.

- The third-party libxml2 library has been updated to version 2.12.0.

- The third-party zStandard library has been upgraded to version 1.5.5.

### Resolved Issues

- (Security update) The third-party openssl library has been upgraded to version 3.2.1 to resolve security potential vulnerabilities including CVE-2023-4807,CVE-2023-5363, CVE-2023-5678, CVE-2023-6237, CVE-2024-0727.

- (Security update) The third-party sqlite library has been upgraded to version 3.45.1 to resolve known vulnerabilities, including CVE-2023-7104.

- (Security update) The third-party libde265 library has been upgraded to version 1.0.15 to resolve known vulnerabilities, including CVE-2023-27102, CVE-2023-27103, CVE-49465, CVE-49467, and CVE-49468.

- (Security update) The third-party libheif library has been upgraded to version 1.17.6 to resolve known vulnerabilities, including CVE-2023-49462, and CVE-2023-49463.

- (Security update) The third-party XMPToolkit library has been upgraded to version 2023.12 to resolve known vulnerabilities.

- (Security update) The third-party expat library has been upgraded to version 2.6.0 to resolve known vulnerabilities, including CVE-2023-52425 and CVE-2023-52426.

- When processing Microsoft Word (docx) files that contained charts, KeyView sometimes left files in the temporary directory when running in-process.

- KeyView sometimes output some nonsense text when processing the headers and footers of Microsoft Word documents (.doc).

- KeyView sometimes returned KVError_Success when attempting to process unsupported PSD documents. It now returns KVError_FormatNotSupported.

- When using the `tstextract.exe` program with the pstx reader, KeyView sometimes failed to extract any content from a PST file when one of the message-type attachments was not valid.

- When a PDF had an non-valid subform, it could lead to a bad input stream error for the whole file. KeyView now skips the non-valid subform and attempts to retrieve information from the rest of the file.

- The `xmlini` sample did not produce SVG output when configured to do so.

### Notes

- The KeyView macOS support has changed so that KeyView 24.2 supports macOS (x86-64) version 10.15 or later.

- KeyView 24.2 no longer includes the deprecated cebsr and lwpsr readers.

## 24.1.0

### New in this Release

- KeyView format detection has been extended, with support for 40 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- KeyView can extract embedded media files from PDF_Fmt documents.

- Metadata parsing has been improved for PDF documents to handle some additional non-standard methods of storing metadata.

- When processing a PDF file using the pdfsr reader, the annotations (also known as comments) output between each page of the document now include the title, author and modification date of the comment as a heading line.

- KeyView now outputs annotations from PDF files when using the pdf2 reader. Annotations are listed on a separate page immediately following the page that the annotations are attached to. You can disable annotations by using the `KVCFG_WP_NOCOMMENTS` configuration flag.

- KeyView now produces tabular output for TSV files.

- KeyView output now includes URLs in OpenDocument Spreadsheet (.ODS) documents and outputs them as hidden text.

- Text-only support has been added for the RSS syndication XML format (RSS_Fmt).

- When configured to display formula strings, KeyView now supports many more formulas from Microsoft Excel (.xls) files.

- When KeyView detects that it will output white text on a white background, it now outputs black text, so the information is still readable.

- The third-party `libpng` library was upgraded from version 1.6.37 to version 1.6.40.

- The third-party Lib ICU library was upgraded to version 73.2.

- The third-party zlib library was upgraded from version 1.2.13 to version 1.3.

### Resolved Issues

- (Security update) The third-party OpenSSL library was updated to version 3.1.4.

- (Security update) A potential security vulnerability was resolved for processing `WebP_Fmt` files or `TIFF_Fmt` files that use webp compression in HTML Export and XML Export. This change addresses CVE-2023-4863.

- (Security update) The `assr`, `awsr`, `kpcgmrdr`, and `orcsr` readers had potential buffer overruns.

- For some PDF files with particular font encodings, the PDF reader (pdfsr) would output some special characters incorrectly.

- In HTML Export, when outputting vector graphics to SVG, text and raster images from EMF files were vertically flipped.

- KeyView failed to detect spaces between words in some PDF documents.

- Processing some valid ODS files failed with the error `KVError_ArchiveFatalError`.

- For some Microsoft Word (DOCX) files, some left-to-right text was output as right-to-left.

- In Microsoft Word (DOCX) files, hyperlinks in the Table of Contents had hyperlink styling applied to them. In the Microsoft Word native application, Word does not apply this styling in Print View.

- KeyView did not use consistent naming conventions for mail subfiles across different file formats.

- On non-windows platforms, KeyView reported invalid bytes at the end of subfiles names for some ZIP-based formats, such as JAR files.

- MBox (.mbx) files that were signed but not encrypted returned `KVError_PasswordProtected`.

- Attempting to retrieve metadata from MSG files returned a `KVError_General`, rather than `KVError_FormatNotSupported`.

- KeyView could identify some files of type GDSII as MacWrite format.

- KeyView missed the content of some pages in PDF documents when they contained certain character encodings.

## 23.4.0

### New in this Release

- KeyView format detection has been extended, with support for 48 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- Handling of XLSX file has been improved when the same image data is referenced multiple times in the same input file. The extract images functionality now detects multiple references and outputs each image only once.

- KeyView now supports extraction of subfiles from iWork13 Pages, Numbers and Keynote files.

- KeyView now supports metadata extraction for current (2013 to the present day) Apple iWork Pages, Numbers and Keynote files.

- Text-only Export support has been added for the ZIP variant of Uniform Office Format word processor files (Uniform_Office_Text_Zip_Fmt).

- When converting PDF files to HTML with the pdfsr reader, Unicode private use area characters are now output as-is, rather than being translated to the configured replacement character (usually a question mark). This change means that symbols from symbolic fonts like Wingdings can now often be displayed correctly by the browser.

- KeyView can now perform text-only export for Yozosoft Yozo Office (Yozo_Office_Fmt) files.

- The `kvhtmlexport` sample program is now available on MacOS (x86 64 and M1).

- The PDF reader (pdfsr) has been improved for Arabic text in some circumstances.

  When you use Microsoft Print to PDF to convert Word documents that contain Arabic text in certain fonts to PDF, the resulting file is often incomplete, missing character mapping information that is required to interpret the text content. The pdfsr reader was previously able to reconstruct this missing information for most cases where the text was in Calibri font. The pdfsr reader can now also reconstruct the information for Sakkal Majalla font, and for additional Calibri cases.

  Furthermore, pdfsr now attempts to reconstruct the information when a character is mapped to the Unicode replacement character codepoint, rather than only when a character's mapping information is missing entirely.

- KeyView can now extract text from some PDF documents that contain Type 3 fonts without unicode character mapping information, rather than always converting all characters in those fonts to the configured replacement character. This process is not guaranteed to result in readable output for all such files.

- The sample programs now default to SVG output for vector graphics.

- The third-party openssl library has been upgraded to version 3.1.2.

- (Security update) The third-party libwebp library has been upgraded to version 1.3.1.

- (Security update) The third-party libxml2 library has been upgraded to version 2.11.4.

- (Security update) The third-party freetype library has been upgraded to version 2.13.1.

- The third-party libheif library has been upgraded to version 1.16.2.

### Resolved Issues

- On macOS, KeyView included a version of `libxml2.dylib`, which could make it difficult for calling applications to use their own or the system version of `libxml2.dylib`.

- KeyView did not set the `KVMainFileInfoFlag_HasContent` flag for `pFiles` (`RMS_Protected_Fmt`).

- When extracting subfiles from a PDF with extracted images configured to true, KeyView could output duplicate images.

- KeyView could incorrectly process some images in PDF files resulting in distorted images.

- KeyView sometimes failed to output the text from some cells in tables in current (2013 to the present day) Apple iWork Numbers and KeyNote files.

- When PDF Logical Reading Order was enabled using the `format_e.ini` file, processing PDFs would result in a `KVError_ReaderInitError`.

- KeyView could exit unexpectedly (in-process) or return an error (out-of-process) when extracting from certain MIME email files.

- KeyView could exit unexpectedly (in-process) or return an error (out-of-process) when processing certain PDF and ODS files.

- (Security update) The third-party ODA library was upgraded to 2024.7 on Windows and Linux platforms, and 2024.1 on Mac platforms to resolve known vulnerability CVE-2023-26495.

- KeyView leaked memory when using the text member of Document objects in the C++ and Python APIs.

- KeyView returned an error when retrieving headers and footers from certain MS Word (docx) documents.

- KeyView returned an error when processing PDF documents containing encrypted forms.

- KeyView returned an error when processing certain PDF documents.

- KeyView sometimes included duplicate text in the output when PDF documents contained the same text multiple times in the same location.

- KeyView sometimes exited unexpectedly while shutting down the `kpodardr` library when using the Export SDK on some AutoDesk AutoCAD Drawing file (AutoDesk_DWG_Fmt) documents.

- When using HTML Export on high resolution EMF (Enhanced_Metafile_Fmt) files that used page space to device mappings other than MM_TEXT, the resulting display was too small.

## 23.3.0

### New in this Release

- KeyView format detection has been extended, with support for 61 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- KeyView 23.3 expands support for the new metadata API that was introduced in KeyView 23.2. The new API has now been exposed through the Java API for Filter. You can also use the new API in the Java API for KeyView Export, but only when extracting subfile metadata.
- Source code identification is available on all KeyView supported platforms.

- The third-party sqlite library was upgraded to version 3.42.0.

### Resolved Issues

- When converting PDFs with a hidden text layer, such as those created by Media Server, invisible text was output in such a way that the transparency could not be overridden. As a result the text could not be highlighted by IDOL View Server.

- (Security update) KeyView depended on outdated LZMA code for detection of 7z encryption. This dependence has been removed.

- When using the pdfsr reader to process PDFs that contained fonts with certain predefined encodings, spaces sometimes appeared in the wrong places in output text.

- When using the pdfsr reader to process PDFs, output text was sometimes broken onto additional new lines or missed characters.

- KeyView leaked memory when filtering some Apple iWork Keynote (.key) (IWPG_Fmt) files.

- KeyView incorrectly identified some attachments to Outlook .msg files as being inline pictures rather than non-inline attachments.

- In HTML export, when exporting PDFs with both HiFi and OCR enabled, invisible text in the output document was not correctly aligned with the image text.

- Changing the global locale could cause KeyView to fail to process some file formats.

- When attempting to filter NIST_ITL_Fmt files, KeyView returned KVERR_FormatNotSupported.

- Extracting metadata or summary information from invalid OLE-based files could cause memory inconsistencies.

- KeyView could produce an unreadable subfile from PST files if no target character set was specified.

- When processing HTML files that specify an ISO-2022 character encoding, KeyView output some entities as unprocessed strings, rather than the correct unicode character.

## 23.2.0

### New in this Release

- KeyView format detection has been extended, with support for 56 additional file formats. By identifying a larger range of formats present in the enterprise, decisions can be made on how to route, filter, or alert on such documents. For the full list, refer to the KeyView Export SDK Programming Guides.

- KeyView 23.2 introduces a new metadata API. The new API:

  - reduces the number of function calls you need to make to retrieve all metadata.
  - performs field standardization. Field standardization returns metadata using a standard set of field names, so that the same metadata is returned in the same field regardless of the source file format. The new metadata API allows for the introduction of further standardization, in future releases, without breaking backwards compatibility.

  The new metadata API is available in KeyView Filter (C and C++). The new metadata API can also be used through KeyView Export (C), but only when extracting subfile metadata.

- Error reporting has been simplified in the C API. In earlier versions of KeyView, some functions could return the error code `KVERR_General`. You could then call `fpGetKvErrorCodeEx()` to obtain an "extended" error code. In KeyView 23.2 the error codes have been unified such that all error codes are included in the `KVErrorCode`enumeration. If a function returns an error code, there is no need to call a second function to obtain more information. This makes it easier to handle errors when an operation fails.

- KeyView has been simplified so that it is much easier to map file formats to readers. File formats no longer have an associated "category". The KeyView configuration files such as `formats.ini`, `formats_e.ini`, and `kvsdk.ini` now identify file formats using the same file format numbers that are returned by format detection.

  For example, when KeyView detects an Adobe PDF file it returns format number `230`. Imagine that you want to process PDF files with the reader `pdf2sr`.

  In previous versions of KeyView you had to find the associated format category (`200`) and use this to configure KeyView:

      200=pdf2

  In KeyView 23.2, this is no longer necessary and you instead use the same format number that is returned from format detection:

      230=pdf2

- KeyView can now extract all platform-specific embedded files from `PDF_Fmt` documents.

- When you enable 'show hidden text', KeyView can now output author names for comments in Rich Text Format (`MS_RTF_Fmt`) documents.

- KeyView can now process certain OpenOffice Text files that it would previously reject, and it can process image alt text in OpenOffice Text as hidden text.

- When getting mail metadata from EML subfiles, KeyView now reports the sent date as a date instead of a string.

- When getting subfile information from EML subfiles, KeyView now converts the file time to UTC, rather than an unspecified time zone.

- KeyView now supports TIFF (`TIFF_Fmt`) files that use WebP compression.

- Handling of Arabic diacritics (tashkil) has been significantly improved when using the pdfsr reader to process PDFs.

- Text ordering has been improved when using the pdfsr reader to process PDFs.

- The FreeType third-party library has been upgraded to version 2.12.1.

- The ODA third-party library has been upgraded to version 2023.12.

- The zlib third-party library has been upgraded to version 1.2.13.

- The libxml2 third-party library has been upgraded to version 2.10.3.

- The expat third-party library has been upgraded to version 2.5.0.

- The ICU third-party library has been upgraded to version 72.1.

- The openssl third-party library has been upgraded to version 3.0.8.

- The libde265 third-party library has been upgraded to version 1.0.11.

- The XMP-Toolkit third-party library has been upgraded to version 2022.06.

- The wavpack third-party library has been upgraded to version 5.6.0.

- The sqlite third-party library has been upgraded to version 3.41.0.

- The third-party libical library was upgraded to version 3.0.16.

- The third-party Apache Arrow library was upgraded to version 11.0.0. This change includes upgrades to the following dependencies:

  - boost was upgraded to version 1.75.0

  - brotli was upgraded to version1.0.9

  - jemalloc was upgraded to version 5.3.0

  - re2 was upgraded to version 2022-06-01

  - thrift was upgraded to version 0.16.0

  - utf8proc was upgraded to version 2.7.0

  - zStandard was upgraded to version 1.5.2

### Resolved Issues

- (Security update) The third-party libtiff library has been upgraded to version 4.5.0 to resolve known vulnerabilities, including CVE-2022-2056, CVE-2022-2057, CVE-2022-2058, CVE-2022-3452, CVE-2022-3570, CVE-2022-3597, CVE-2022-3598, CVE-2022-3599, CVE-2022-3626, and CVE-2022-3627.

- (Security update) The third-party protobuf library has been upgraded to version 3.21.12 to resolve known vulnerabilities, including CVE-2022-1941.

- (Security update) The libjpeg third-party library has been upgraded to version 9e to resolve potential vulnerabilities.

- (Security update) The libwebp third-party library has been upgraded to version 1.3.0.

- For password protected OpenOffice files (ODS, ODT and ODP), `fpOpenFile` did not return `KVERR_PasswordProtected`. Continuing with extraction could then result in invalid extracted files.

- KeyView could truncate long sections of text in `PDF_Fmt` documents.

- KeyView did not retrieve the Image Width, Image Height and Bits Per Pixel in summary information from Tagged Image File Format (TIFF) `TIFF_Fmt` files.

- For some Microsft Excel (XLSX) files with a lot of cells using Rich Data Types, KeyView output the names of those types incorrectly, using a number instead of a type name.

- Some C sample programs could loop endlessly when a bad argument was passed in.

- KeyView could skip some user defined properties in summary information for some OLE-based files like `MS_Project_2007_Fmt`.

- When using the pdfsr reader for text in right-to-left languages, diacritic characters were sometimes not extracted correctly.

- KeyView did not extract all the images from some Rich Text Format (`MS_RTF_Fmt`) documents.

- The extraction API `fpGetSubFileInfo` function did not correctly report the sizes of subfiles when they were larger than 2GB.

- Some PDF files took longer to process in version 12.13.0 of the SDK than in version 12.12.0.

- Heic and Heif format documents could not be processed on macOS.

- KeyView could return an error (out-of-process), or exit unexpectedly (in-process) when processing some Microsoft Visio (.vsd) files.

- KeyView missed text from some Microsoft Visio (.vsd) files.

- Some base-64 encoded attachments to ICS files were extracted incorrectly.

- When converting spreadsheet files to HTML, KeyView removed all empty rows even when `bRemoveEmptyRows` was set to FALSE.

- KeyView could report duplicate metadata from Tagged Image File Format (TIFF) files with multiple pages.

- When using `kvhtmlexport` to export container files, internal container subfile pages were misnamed as `subfilen.temp`.

- KeyView could output incorrect metadata names for some PDF files.

- KeyView could omit metadata entries for some PDF files.

- KeyView could be slow to start the out-of-process session if called on more threads than there were ports configured.

- When using the pdfsr reader to process PDFs that contained right-to-left (RTL) text, some text at the top of the file was not included in the output.

- KeyView could process some CSV files incorrectly, meaning fields were output in the wrong columns.

- KeyView would terminate unexpectedly (in-process), or return an error (out-of-process), when processing a PDF document with the reader `kpPDF2rdr`, if the input was an input stream that was not created by KeyView.
- The reader `kpPDF2rdr` was not thread-safe.
- The reader `kpPDF2rdr` failed to release memory each time a file was processed.
- The reader `kpPDF2rdr` could output incorrect values for page width and height.

### Notes

KeyView 23.2 is a new major version of IDOL, released in the second quarter of 2023. It is the first new major version since KeyView 12.0 was released in June 2018. KeyView 23.2 includes some changes that require you to update your license and application code. For more information about how to upgrade, see the KeyView upgrade guide.

## Deprecated Features

The following features are deprecated and might be removed in a future release.

Category | Deprecated Feature | Deprecated Since
--- | --- | ---
Target Encodings | Target encodings other than KVCS_UTF8 and KVCS_UTF16 are now deprecated. OpenText recommends that you use the common UTF-8 and UTF-16 encodings. | 24.4

Copyright 2025 Open Text
Version 25.3.0 | Last updated July 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: IDOL and KeyView OEM 25.3.0

Topic Title: Export SDK