#989 Allow using <trans-unit> ID as identifier of alternative translations in XLIFF filter

3.1
closed-fixed
5
2016-04-23
2014-04-21
No

The XLIFF filter uses the previous and next paragraphs as identifiers for alternative translations.

In some circumstances, this is not discriminating enough, and <trans-unit> id provides a unique identifier. An option in the XLIFF filter should allow using the <trans-unit> id as the identifier for alternative translations.

Didier

Discussion

  • Didier Briel

    Didier Briel - 2014-04-21

    Implemented in /trunk.

    In Options > File Filters > XLIFF > Options, it's possible to choose between "Previous and next paragraphs" and "<trans-unit> ID" for the identifier used for alternative translations.

    Didier

     
  • Didier Briel

    Didier Briel - 2014-04-21
    • status: open --> open-fixed
     
  • Didier Briel

    Didier Briel - 2014-05-19
    • status: open-fixed --> closed-fixed
     
  • Didier Briel

    Didier Briel - 2014-05-19

    Closing.

    Implemented in the released version 3.1.1 of OmegaT.

    Didier

     
  • Héctor Cartagena

    I have been testing this functionality and run into a "problem". There is an alternative translation in my project_save.tmx that is paragraph-based. I created it when my xliff file filter configuration still was "Previous and next paragraphs". Then, I changed the configuration for the file filter to "<trans-unit> resname attribute when available", reloaded the project and the alternative translation is not shown anymore in the Editor, but neither in the Fuzzy Matches pane, the Multiple Translations pane, and even when I search it, I can't find it. I double-checked by opening project_save.tmx in Gedit and I confirmed that the alternative translation is still there. Finally, I created a new "alternative translation" for the same segment using the new configuration and it does appear in the corresponding places. I understand that the previous translation does not appear anymore in the Editor after changing the configuration, but am I wrong to expect it to appear as an "orphan segment" in Fuzzy Matches and Text Search, and as an "alternative translation" in Multiple Translations?

     
  • Didier Briel

    Didier Briel - 2016-04-23

    even when I search it, I can't find it

    I tested, and I can find it OK with a search. (Are you sure you didn't uncheck orphan segments?)

    It appears also in the Multiple Translations pane for the corresponding segments.

    It does not appear in the Fuzzy Match pane for the same source segments (alternative translation never appear for exact matches in this pane), but it does appear when appropriate for similar segments.

    In other words, I cannot reproduce an issue.

    Didier

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks