![]() Implemented support for Trados Studio packages Switched to synchronized classes in XML package Suppressed output for confirmed empty targetsĪdded support for Adobe InCopy ICML and SRT subtitlesįixed JSON encoding fixed import of XLIFF matchesįixed handling of TXLF files and improved XML catalogĪdded conversion of 3rd party XLIFF improved support for XLIFF 2.0 fixed issues with Trados Studio packagesĪdded improvements required by Swordfish IV.Īdded 5 Machine Translation (MT) engines (Google, Microsoft Azure, DeepL, MyMemory & Yandex) Improved support for Trados Studio packages Improved validation updated language managementĪllowed concurrent access for XLIFF Validation Improved round trip 1.2 -> 2.0 -> 1.2 Ignored untranslatable SVG in DITA maps Improved support for XLIFF 2.0 Switched to Java 17 Improved validation of XLIFF 2.0 Added SVG statistics for XLIFF 2.0 Moved server code to XLIFF Manager projectįixed handling of nested untranslatables in DITA Improved XLIFF 2.0 support Updated dependencies and improved validation of XLIFF 2.x Improved support for Trados Studio Packagesįixed conversion of third party XLIFF filesĪdded remove all targets added feedback for Fluenta on DITA filterĪdded copy source to target Fixed DITA conversion and merge Improved support for DITA from Astoria CMSįixed joining of XLIFF 2.0 files and improved PHP Array supportĬonverted HTML fragments in Excel & Word files to tagsĪdded configuration options to JSON filter Added scripts to approve all segments Updated language list Ignored tracked changes from Oxygen XML EditorĪdded "xmlfilter" parameter to conversion options JavaPM a set of scripts for localizing Java.Fluenta a Translation Manager that uses OpenXLIFF Filters to generate XLIFF from DITA projects.XLIFF Validation web-based XLIFF Validation Service.TMXEditor relies on OpenXLIFF Filters XML support for processing TMX files.Stingray uses OpenXLIFF Filters for extracting the text to align from supported monolingual documents.RemoteTM uses OpenXLIFF Filters to handle all TMX processing.Swordfish IV uses OpenXLIFF Filters to extract translatable text from supported formats and manage XML documents.XLIFF Manager implements an easy to use free UI for creating, merging and validating XLIFF files in a graphical environment. ![]() Its code has been ported to Java 11 and enhanced with support for XLIFF 2.0. XLIFFChecker, an open source XLIFF validation tool, is now part of OpenXLIFF Filters. With OpenXLIFF Filters you can create XLIFF files that don't use proprietary markup and are compatible with most CAT (Computer Asisted Translation) tools. Happy to exchange emails with you if you need any more advice.An open source set of Java filters for creating, merging and validating XLIFF 1.2 and 2.0 files. you cannot upload into what seems like an exact copy that may have been shared with you). There are some nuances with the xlf (XLIFF / XML) files that RISE produces and you should be aware that you can only upload the xlf from RISE into the exact course it was exported from (i.e. Other options in no particular order - although mate cat is open source. We use memoQ but I am not on any form of commission. What you probably need to search for online is CAT tools (computer assisted translation).ĭependent on your needs (volume ongoing requirements) there are two main industry tools. Sorry if the above doesn't help much but at least it is an honest answer. Your best way forward (if you do not have a Translation Memory) would be to try and leverage the translation you have as a resource if this is bilingual and possibly align this document (with the aid of a CAT tool) to produce a resource that could help lower the cost of creating a new XLIFF. (By the time you have done this unless the course is thousands of words you are probably as well trying to copy across the translated text where this can be done. You could export a new XLIFF from Rise > Import into a CAT tool > Export a blank bilingual (rich text format generally) document > copy across the text > Import back into the CAT tool > Export an XLIFF for import into RISE. If you re-export your Rise course (create a new xliff) and supply to your translator they may have created a Translation memory when translating the first xliff file and could possibly populate the new xliff with the stored translation in the Translation Memory > they should then be able to export the results (after checking all is translated) to a new Xliff that should then upload to your course.Ģ. On the premise they have created a Translation memory. There are a couple of solutions but both are manual and would require a CAT (Computer Assisted Translation) tool.ġ. I am just the messenger, but you cannot convert a word document to xliff and upload to your RISE course.
0 Comments
Leave a Reply. |