Okapi Components for WorldServer, 1.7

This release repackages some of the dependencies to avoid collisions with other dependencies in the target WorldServer environment.

Okapi Components for WorldServer, 1.6

This release upgrades the underlying Okapi components to release M34, with several major improvements.

• A MT Adapter for Google MT is now supported. The adapter will use Google NMT transparently when available.
• A filter for InDesign IDML files is now available. This is based on the rewritten IDML filter from Okapi M34, which fixes many issues in the previous implementation.

A note regarding downloads: Since the -deployable downloads have gotten quite large due to changes in bundled Okapi dependencies, I'm only attaching the bundles and the new components here. If you need individual components and are having trouble building them yourself, let me know.

XLIFF Filter for WorldServer, version 1.5.2

This is a bugfix release that fixes an issue that caused the XLIFF filter to write out an incorrect UTF-8 XML encoding statement when generating target files.

Other components were not affected.

Microsoft Translator MT Adapter for WorldServer, version 1.5.1

This is a bugfix release to address a regression in Okapi M32 that prevented the adapter from successfully performing translation into certain languages, including:

• Traditional Chinese
• Serbian (Cyrillic Script)
• Latin American Spanish

Other components were not affected, so you can continue to use Release 1.5 versions.

Okapi Components for WorldServer, 1.5

This release upgrades the underlying Okapi components to release M32, with several major improvements.

• The Microsoft Translator Hub MT Adapter now supports Azure-based authentication. You will need to update your MT Configurations with an Azure key, as DataMarket-based authentication is no longer supported. See the wiki for more details. For more information about migrating your Microsoft Translator account to Azure, please see the support information from Microsoft.
• The OpenXML filter now supports Microsoft Visio 2013 and later (*.vsdx) files.
• Added a new XLIFF filter and an automatic action to import bilingual XLIFF data into a project. See the wiki for more information.
• Support for user-defined remapping of locales when calling Microsoft Translator (see the wiki).

This contains the individual deployable JARS for each of the filters (JSON, PO, YAML, OpenXML, XLIFF), the MS Hub adapter, and the automatic actions, as well as bundles that allow more than one component to be deployed at once:

• okapi-ws-components-bundle to deploy all components
• okapi-ws-components-filters to deploy all filters

MS Translation Hub Azure Support - Preview 2

This is a preview release of Azure support for the MS Translation Hub adapter.

For information on migrating your Microsoft Translator account to Azure, please see the support information from Microsoft.

Warning: Deploying this component will overwrite your existing component. You will need to re-install a previous version to continue using DataMarket (ClientID/Secret)-based authentication. It is recommended that you deploy this adapter to a staging system for testing first.

New since Preview 1:

• Support for user-defined remapping of locales when calling MT (see the wiki)

MS Translation Hub Azure Support - Preview

This is a preview release of Azure support for the MS Translation Hub adapter.

For information on migrating your Microsoft Translator account to Azure, please see the support information from Microsoft.

Warning: Deploying this component will overwrite your existing component. You will need to re-install a previous version to continue using DataMarket (ClientID/Secret)-based authentication. It is recommended that you deploy this adapter to a staging system for testing first.

Okapi Components for WorldServer, 1.4

This release upgrades the underlying Okapi components to release M31 and adds two new components.

• An OpenXML filter is now supported. This supports Word, PowerPoint, and DOCX without needing FTS support. Currently, only a subset of Okapi's filter options are exposed in the WorldServer UI, but the selection will expand over time.
• The Microsoft MT Adapter has been improved through heavy changes of both the adapter code and the underlying Okapi library. Note that this release still uses the legacy DataMarket authentication method; an upgrade for Azure support will be coming in the next release.
• An automatic action has been added that provides even improved placeholder fidelity in MT output for source assets are HTML or XML, when working with the Microsoft Translation Hub.

For more information about the MT Adapter and the optional Hub AA, see this wiki page.

This contains the individual deployable JARS for each of the filters (JSON, PO, YAML, OpenXML), the MS Hub adapter, and the MS Hub automatic action, as well as bundles that allow more than one component to be deployed at once:

• okapi-ws-components-bundle to deploy all components
• okapi-ws-components-filters to deploy all filters

Okapi Components for WorldServer, 1.3

This release upgrades the underlying Okapi components to release M30, which provides improved logging for the Microsoft MT Adapter and a fix for JSON filter configurations that call a subfilter. It also improves the stability of the filters by caching configuration information used to extract content from source files. This will prevent situations where a change to the filter configuration could break projects that were already in progress.

This contains the individual deployable JARS for each of the filters (JSON, PO, YAML) and the MS Hub adapter, as well as bundles that allow more than one component to be deployed at once:

• okapi-ws-components-bundle to deploy all components
• okapi-ws-components-filters to deploy all filters

Changes since 1.2:

• Upgrade Okapi components to M30
• Filters will now cache configuration data for extracted files to ensure that the same settings are used during merge.

Okapi Components for WorldServer, 1.2

This release upgrades the underlying Okapi components to release M29, resulting in fixes to several filters. In particular, this takes advantages to improvements to the YAML filter made in M29 to handle multi-line values and several other edge cases.

This contains the individual deployable JARS for each of the filters (JSON, PO, YAML) and the MS Hub adapter, as well as bundles that allow more than one component to be deployed at once:

• okapi-ws-components-bundle to deploy all components
• okapi-ws-components-filters to deploy all filters

Changes since 1.1:

• Upgrade Okapi components to M29
• Add an option to all filters to enable WorldServer's sentence-breaking functionality
• Expose the "Extract Standalone Keys" option in the JSON filter
• Add several helper classes related to the WSAttributable WSSDK interface