Good news for the XLIFF user community: memoQ 9.7 comes with an import filter for XLIFF 2 files! Files exported in this format can now be added to memoQ and configured for better segment and meta data management.
Make it your own: flexible filter configuration options
You spoke, we listened: memoQ 9.7’s new import filter tackles some of the biggest pain points our users face when handling XLIFF 2 files. No need for workarounds, quick fixes or XML hacks anymore.
Translate the segment status information stored in XLIFF 2 files into memoQ statuses with ease. When importing a document, our latest product version allows you to map XLIFF-specific statuses, including initial, translated, reviewed and final, or missing status into one of nine native segment statuses you can see in the translation editor.
In multilingual files, not all languages or language variations are relevant to localization specialists. By default, memoQ scours files for texts in the main languages of a project. In memoQ 9.7, users also have the option to import content from XLIFF 2 files only if there’s an exact match for language and dialects, or import content no matter the language.
Managing segmentation is also a key import configuration. Depending on the source the XLIFF 2 file is exported from, segment boundaries can encompass anything from a sentence through a paragraph to the entire file. Users can both decide if segment boundaries can or should be modified, and if memoQ should revise XLIFF segmentation and re-segment the text.
memoQ for developers: advanced whitespace and meta tag management
Making contextual information visible to translators in XLIFF 2 files has been a top-of-mind issue for some of our users, especially those in the software localization industry. In our latest product version, the content of note and mda:meta tags appear as comments to preserve the contextual data of XLIFF 2 files used in software translation projects.
Another challenge software translation specialists face is managing whitespace. UI strings are often full of spaces that are just as crucial as text elements. To make sure these are handled properly in both XLIFF 2 and XLIFF 1 files, users can choose whether or not to import segments where the source is empty or made up entirely of spaces, or spaces at the beginning and end of source and target segments.
