as-ascii

Yes, it is possible by design. Every parser like DOC parser, DOCX parser, EML parser or others can emit tag::File during the parsing process and it will be processed by...

Hello, The issue was confirmed: #121 . The code for extracting a lot of metadata from eml file, including the subject is embedded inside the SDK, however tag::Metadata is not...

Hello, The problem was found and fixed but it was not merged yet to the main branch as it is part of larger changes that are under performance testing. We...

The branch with the fix was merged. Currently if you receive tag::Document from the SDK you can use metadata function field to parse and retrieve metadata. Metadata exporting was added...

Thank you for your report and investigation. C-API was removed from new versions of DocWire SDK as we currently focus mostly on modern C++ API. It will return if the...

GitHub Continuous Integration builds are fine for [2024.01.05](https://github.com/docwire/docwire/tree/2024.01.05) and current "head" as well.

We suspect a long directory path or a dot in the directory name because of the following notice in vcpkg documentation https://github.com/microsoft/vcpkg?tab=readme-ov-file#quick-start-windows: "First, download and bootstrap vcpkg itself; it can...

Hello, The only limitation in theory that we know so far is the UTF-8 encoding, because internal character encoding in the SDK is UTF-8. If necessary font&encoding information are embedded...

Under investigation. We will probably convert some shorter examples from OCR automatic tests to other formats like pdf and other office formats to fix it and disallow regressions.

Splitting the SDK into a larger number of smaller libraries is planned to be done soon: #103. The final solution will be not to link the docwire_pdf library.