This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
A client says: "Can you clarify something about XLIFF for me: if we start with a Word document in English, you can provide an XLIFF document with both the English source and the Spanish translation? Are you also able to provide, within that same document, a French translation? The challenge we are facing is having to translate multiple documents into 5 languages as the project will entail translating a web site, then providing the developer with XLIFF files for import into the content management... See more
A client says: "Can you clarify something about XLIFF for me: if we start with a Word document in English, you can provide an XLIFF document with both the English source and the Spanish translation? Are you also able to provide, within that same document, a French translation? The challenge we are facing is having to translate multiple documents into 5 languages as the project will entail translating a web site, then providing the developer with XLIFF files for import into the content management system. What is the industry best practice for such a scenario?" Can anyone help me out with this? Thanks in advance! ▲ Collapse
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Robert Tucker (X) யுனைடட் கிங்டம் Local time: 23:27 ஜெர்மன் - ஆங்கிலம் + ...
I think the industry standard for the scenario is XML:TM.
My current guess is that the problems you are likely to encounter may be more to do with tools available than standards. ▲ Collapse
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Nicolas Coyer (X) கொலொம்பியா Local time: 18:27 ஸ்பேனிஷ் - ஃபிரன்ச் + ...
TagEditor
Feb 29, 2008
Why don't you work directly in TagEditor. I think it supports XLIFF files since version 2006 0r 2007 (they are XML-based).
Good luck!
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Rodolfo Raya Local time: 20:27 ஆங்கிலம் - ஸ்பேனிஷ்
XLIFF files are bilingual.
Feb 29, 2008
Robert Tucker wrote:
Although an XLIFF file can contain more than one language translation, it is highly recommended that an XLIFF file contain translation for one language only.
XLIFF files are bilingual. There can only be one <target> element per translation unit.
A new XLIFF file is necessary for each target language.
Regards,
Rodolfo
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.