New Release

OmniMark v13 reinforces Stilo’s status as a premier developer of software tools for content conversion pipelines. This new release provides support for additional modern platforms, important library updates, improved XML schema handling, and a number of reliability, compatibility, and security-related improvements for customers running OmniMark in current enterprise environments.

New Platforms

  • Red Hat Enterprise Linux 10 — Adds support for the latest Red Hat enterprise Linux platform, helping organizations keep OmniMark aligned with current long-term infrastructure standards and future server upgrade plans.
  • Amazon Linux 2023 — Provides support for modern AWS-based deployments, making it easier for customers running cloud-hosted content processing workflows to deploy OmniMark on current Amazon Linux environments.
  • Ubuntu 22.04 — Adds support for a widely used long-term support Ubuntu release, giving customers greater flexibility when deploying OmniMark in Linux-based development, testing, and production environments.
  • Ubuntu 24.04 — Extends support to the latest Ubuntu long-term support platform, helping customers modernize their Linux infrastructure while continuing to run established OmniMark processing pipelines.
  • Microsoft Windows Server 2022 — Adds support for a current Windows Server platform used by many enterprise IT teams, improving deployment flexibility for Windows-based OmniMark environments.
  • Microsoft Windows Server 2025 — Provides support for the newest Windows Server generation, helping organizations prepare OmniMark deployments for upcoming server refreshes and longer-term Windows infrastructure planning.

New in the Libraries

  • Improved XML schema error reporting in omxmlschema — If a dynamically loaded XML schema referenced by xsi:schemaLocation or xsi:noNamespaceSchemaLocation fails to compile, OmniMark now emits a markup error instead of silently ignoring the schema. This is important because it gives developers and production support teams clearer visibility into schema problems, making XML validation issues easier to diagnose and reducing the risk of unnoticed schema-related processing errors.
  • Updated Windows omvfs curl dependency — The Windows omvfs build now uses curl 8.19.0. This improves compatibility with current Windows build environments and helps keep OmniMark aligned with newer third-party library versions. For customers, this means better long-term maintainability and a more current dependency foundation for workflows that rely on virtual file system access, including network-based content retrieval.
  • Modernized HTTPS handling for Linux omvfs — The Linux omvfs library now uses the system libcurl-based HTTPS stack, replacing the legacy HTTPS dependency setup. This is important because it allows OmniMark to integrate more naturally with the host operating system’s maintained networking and security libraries, simplifying deployment and helping customers benefit from operating-system-level library maintenance.
  • Updated LDAP linking for omldap — On newer platform builds, the omldap library now links against host LDAP libraries using -lldap and -llber, replacing the legacy OpenLDAP dependency setup. This improves compatibility with modern Linux platforms and helps reduce reliance on older bundled dependency configurations. It is especially useful for organizations that integrate OmniMark processes with LDAP-based directory services.

Fixes

  • Whitespace handling in XML schema attributes — The omxmlschema library now ignores leading and trailing whitespace in schema attributes of built-in types such as xs:NCName and xs:URI. This improves tolerance when processing real-world XML schemas where insignificant whitespace may be present, reducing avoidable validation problems and helping content pipelines handle schema inputs more consistently.
  • Improved file URI handling in omoasiscatalogs — The omoasiscatalogs library now correctly handles file URIs with encoded spaces, such as %20, and other special characters. This matters because catalog-based resolution often depends on accurate file path handling. The fix improves reliability when working with file names or directory paths that include spaces or encoded characters, which are common in enterprise document repositories.
  • FTPConnectionRemoteInputFile stability fix on Linux — Using FTPConnectionRemoteInputFile could cause a segmentation fault on some Linux configurations; this has now been fixed. This improves runtime stability for OmniMark applications that retrieve input files over FTP, helping prevent unexpected process failures in automated content conversion workflows.
  • Improved Unicode filename handling on Windows — Handling of files with Unicode characters in their names has been improved on Windows. This is important for customers processing multilingual content or working with international file naming conventions, helping ensure files with accented characters, non-Latin scripts, or other Unicode characters are handled more reliably.
  • Corrected XML markup error line numbers on Linux — When parsing XML with a DTD, markup error line numbers could be incorrect on Linux if the input contained CRLF line endings. This has been fixed. Accurate line numbers are essential when diagnosing XML and DTD-related issues, so this improvement helps developers identify and resolve content problems more quickly.

Security and Dependency Improvements

  • Reduced exposure to older third-party dependency issues — OmniMark v13 updates and modernizes key dependency usage across omvfs and omldap. The release notes identify the historical use of curl 7.65.3 in previous omvfs configurations and OpenLDAP 2.4.23 in historical Linux omldap configurations. By moving to newer dependency approaches, including curl 8.19.0 on Windows and host library integration on newer Linux platforms, OmniMark v13 helps customers operate on a more current and maintainable software foundation.
  • Improved alignment with enterprise maintenance practices — Using current platform libraries and supported operating systems helps simplify security review, patch management, and IT compliance processes. This is particularly important for customers running OmniMark as part of business-critical content conversion, publishing, or data transformation pipelines.

Try OmniMark for free. Request a free 60-day* evaluation copy of OmniMark.

*strictly non-production use