Idea Delivered Partially

There are several methods:

- Use XLIFF - this is a standardised bilingual XML format and can handle partial translations out of the box

- Use macros/tools as discussed here in comments

- Develop a bilingual file type using a) developer community or b) inhouse development

Setting to "Delivered partially".

Provide filetype for bilingual (or even multilingual) XML

  We often have XML files that are bilingual e.g. like this (its a Safexpert XML file for translation, by the way):

<Item>
    <de>German text</de>
    <en>English text</en>
</Item>

Or it could also be like this:
<item language="de">German text</item>
<item language="en">English text</item>

Yes, we know this link and the method described there: https://multifarious.filkin.com/2015/11/22/a-little-learning/. We also know, that it is possible to save the XML file as a bilingual Excel file.

The problem is that

  1. Some of the English/target language elements already contain translations that need to be preserved.
  2. We need to re-import the XML file after translation.

So, none of the above workarounds works.

We need it like that way, that the text from the <de></de> element is taken as source language and the translation is written into the <en></en> element.

I can't imagine why Trados is not able to handle these bilingual XML files. You are able to do it with Excel, so why is it not also possible with XML?

Please provide a filetype for translating bilingual XML.

Tamara Roth
Parents

  • I don't think any of the proposed methods addresses the problem:

    - method 1: Is it possible to convert an existing XML file to XLIFF and re-convert it after translation? Or can the XLIFF filetype be used for any bilingual XML? If yes, how?

    - method 2: the method Christine Eulriet uses, is  basically, what we have to do now in default of other options. It's, what is described here: multifarious.filkin.com/.../. As I already stated, it is not only a workaround, it does not even solve the problem. Some target language elements in the XML file already contain translations. These will be deleted, when copying the source text into the target language elements.

    - method 3: "We" are not an agency. We (which is 'me and my collegues') are a documentation department. We don't have the means to develop anything by ourselves.

Comment

  • I don't think any of the proposed methods addresses the problem:

    - method 1: Is it possible to convert an existing XML file to XLIFF and re-convert it after translation? Or can the XLIFF filetype be used for any bilingual XML? If yes, how?

    - method 2: the method Christine Eulriet uses, is  basically, what we have to do now in default of other options. It's, what is described here: multifarious.filkin.com/.../. As I already stated, it is not only a workaround, it does not even solve the problem. Some target language elements in the XML file already contain translations. These will be deleted, when copying the source text into the target language elements.

    - method 3: "We" are not an agency. We (which is 'me and my collegues') are a documentation department. We don't have the means to develop anything by ourselves.

Children
No Data