cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Service Information Manager: Translation Managements Enhancements

Service Information Manager: Translation Managements Enhancements

Hello!

We consider the following issues major and important improvements to the translation management:

  • Multilanguage-document support: 1 (in word: ONE) document in multiple languages.
  • Editing of translated documents: It would be nice to rightmousebutton on the Information and Publicationstructure and change the *Structure to a target language (with some little language flags), so that the author can easily review, edit, etc. the target languages. This would reduce search-time for a specific translation object. A language edit of the *Structure should update the related XLIFF, so that the not nice to read XLIFF should not be opened by the user.
  • Translate only changed content INSIDE a module: When a revised version of a module is send out for translation, the translation process should mark the sections, for translation, the unchanged text shoud be marked not to be translated.
    Example: A module has four paragraphs. Only the 2nd paragraph was changed. The translation process should mark the 2nd paragraph for translation (and/or the other three not for translation), so that the translation service won't translate the same paragraphs again. Or even better: Translation should already replace the unchanged paragraphs with the translation and leave the changed para in the authoring-language with a DO TRANSLATION note for the translation vendor. This should reduce costs of translation as well.

Thank you very much,

WindchillTeam@DATACOPY

2 Comments

Hello- just wanted to make some quick comments about some of your ideas.

1-. This is a long term improvement we will consider.

2- Today you can see a Structure in different translated language, but you can't edit the IEs that make up the structure. We do have the Translation Content tab that will allow you to quickly go to the translated version of an object in order to open it up for editing. It is on our long term roadmap to provide more of a integrated XML editing environment- that might be able to address some of your use case as well.

3. We do not delve into the content itself to determine what has changed. This is work that is typically left up to the LSP to do. In most cases, translation memory banks at the LSP will make sure the same paragraph or content is not translated again, cutting down on costs.

Community Manager
Status changed to: Archived