We get our translation in XLIFF Format and have problems reading the file into our CMS.
The are two problems:
1. The XML contains a BOM at the beginning of the file. The Java CMS is using Xerces to parse and complains about an invalid prologue. Can I disable writing the BOM?
2. When the source of the translation is only a blank, the output file contains a translation unit with the < target/ > missing. The XLIFF standard says that there are pairs. Is there a workaround?
[Edited at 2013-09-21 12:35 GMT]
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
To report site rules violations or get help, contact a site moderator:
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
Modern desktop project management for freelance translators
BaccS makes it easy for translators to manage their projects, schedule tasks, create invoices, and view highly customizable reports. User-friendly, ProZ.com integration, community-driven development – a few reasons BaccS is trusted by translators!