Menu

#969 Alternative translations are not taken into account if no default translation is set

5.3
closed-fixed
None
5
2020-08-14
2019-12-19
No

If the "Auto-propagation of Translations" checkbox is set in the project properties, alternative translations present in the project_save.tmx are not loaded correctly.
oreover, if a translation of the segment is present in the source file (in case of a Xliff file for example), this translation will be displayed.

To illustrate the problemn in the attached project, the segment in the file SCI002.xlf appears as ERROR - 456 but it should be A - 456 as it is defined in project_save.tmx. The same problem appears on the third file.

Looking at the method org.omegat.core.data.RealProject.importTranslationsFromSources() it appears that the alternative translations are only used when the auto-propagation is not set.

As the alternative translations are always more precise in term of context, I think it would make more sense if these translations would be given a higher priority than the default translation, whether auto-propagation is checked or not.

1 Attachments

Discussion

  • Briac Pilpré

    Briac Pilpré - 2020-04-28

    Fixed in [f4282b].

     
    👍
    1

    Related

    Commit: [f4282b]

  • Briac Pilpré

    Briac Pilpré - 2020-04-28
    • status: open --> open-fixed
     
  • Briac Pilpré

    Briac Pilpré - 2020-04-28
    • assigned_to: Briac Pilpré
     
  • Aaron Madlon-Kay

    • Group: 5.2 --> 5.3
     
  • Aaron Madlon-Kay

    • status: open-fixed --> closed-fixed
     
  • Aaron Madlon-Kay

    Fixed in OmegaT 5.3.0.

     

Log in to post a comment.