You are currently working on UAT 

Different file formats and reuse of translation memory

We are currently looking for a translation program to translate the language resource files of our software. Probably these will be .properties files.

Another point concerns the documentation.

We'll probably have to proceed this way:

1. building a translation memory when translating Help and Manual (that's an XML format that unfortunately uses a lot of inline formatting, so I want to get rid of it).
2. reuse this Tanslation Memory for translation into:
- Word files
- Flare Projects
- Asciidoc (more or less plain test)
- .properties files

Generally speaking, can I reuse the translation memory? Or do format-specific information prevent reuse?

Parents Reply
  • Lets say I have a in different filetye a sentence, which contains a bold formatet part:

    • Help- and Manual XML: <para styleclass="Normal"><text styleclass="Normal" translate="true">Activate the licence under the </text><text styleclass="Bold" translate="true">registry</text><text styleclass="Normal" translate="true"> tab.</text></para>
    • HTML/Flare XML: <p>Activate the licence under the <strong>registry</strong> tab.</p>

    Let's assume that I manage to create filters that are useful for Help and Manual XML. The translation memory is first created when the Help and Manual sentence is translated. Then the same translation memory is used for a flare document. Would I get a 101% hit for this example?

Children