Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#963 Mark auto-populated segments

3.1
closed-fixed
None
5
2014-05-26
2014-03-03
Didier Briel
No

When an untranslated segment is matched by an exact match from a TMX contained in the auto folder, the translation is inserted automatically.

For some translation teams, this corresponds to a specific situation which should be identified visually.

In addition, when the translation has not been manually edited and a new translation is available, the newer translation should replace the existing one.

Finally, in some specific cases, it should be necessary to distinguish between ICE (In-Context Exact) matches, identified exact matches and normal exact matches (without any specific identifier).
This will work only for source documents with an ID, for instance the XLIFF filter (but it works with other source documents with IDs). To differentiate, a property in the TMX will contain the following value: <prop type="”x-ice”"> for an ICE match and <prop type="”x-100pc”"> for an identified exact match. To know to which source segment these matches correspond, one must compare the <trans-unit id=""> of the XLIFF source segment with the ID contained in the <prop type="”x-ice”"> or <prop type="”x-100pc”"> of the TMX match.

Furthermore, in the case of a round-trip, it may be necessary to allocate specific translations to specific segments of the XLIFF source document. These specific translations will be identified by <prop type="”x-id”">.

In the View menu, a Mark Auto-Populated Segments entry will be created. When checked, the background of all segments where the target segment has been auto-populated will be displayed in orange if the match is marked as x-ice, medium orange for x-100pc and light orange otherwise.

As soon as the content of the segment is changed (i.e., edited by the user), the "auto-populated" status will be empty.

Whether the property is saved to project_save.tmx or not will depend on an option defined in Editing Behaviour: Save auto-populated status. The default option will be off. If this option is not checked, as soon as the project is saved and reloaded, the property will be lost. That is, no segment will appear as auto-populated, even if has not been modified. If this option is checked, the property will be saved to project_save.tmx as a <prop>. That way, even when a project is saved and reloaded, the segments will still appear as being auto-populated. The only way to change that status will be to modify them, or by unchecking the option, in which case the next save will remove all auto-populated status.

Didier

Discussion

  • Didier Briel
    Didier Briel
    2014-03-03

    Translation from tm/auto/ that contain x-ice or x-100pc will be used as alternative, not as default translation since we always need ID. Translations without x-ice or x-100pc will be used as default, with <prop type="x-auto"/> to be able to change translation when it will be changed in tm/auto/.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-03-10

    • status: open --> open-fixed
     
  • Didier Briel
    Didier Briel
    2014-03-10

    Implemented in /trunk.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-04-14

    Implemented in the released version 3.1.0 of OmegaT.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-05-26

    Closing.

    Implemented in the released version 3.1.0 of OmegaT.

    Didier

     
  • Didier Briel
    Didier Briel
    2014-05-26

    • status: open-fixed --> closed-fixed