Menu

#421 Losing all progress when using the same language code as source and target

open-fixed
None
5
2025-02-23
2024-06-09
No

I created a project to to translate a literary text from an old version of a language to its contemporary version. As this is the same language (Neapolitan), I used the same language code (nap) in the Source and Target fields when creating the project. This did not throw any warnings and I translated the first chapter over the following days, without ever closing OmegaT.

However, when I closed it and then reopened, I found out that all my translated segments had gone - the whole chapter was highlighted in blue instead. The glossary I added was still present, and occasionally the fuzzy matching would identify some translation memories, so I could recover some of my work. Rolling back to backups didn't fix the issue.

What fixed the issue was creating a new project and using two different language codes in the Source and Target fields. So it seems that OmegaT can't have the same language code in those fields; however, this is not explicit.

Would it be possible to:
1. throw an error if the user inserts the same language code in the two fields when creating the project
2. or at least mention this in the user manual?

Discussion

  • Jean-Christophe Helary

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,6 +1,9 @@
     I created a project to to translate a literary text from an old version of a language to its contemporary version. As this is the same language (Neapolitan), I used the same language code (nap) in the Source and Target fields when creating the project. This did not throw any warnings and I translated the first chapter over the following days, without ever closing OmegaT.
    +
     However, when I closed it and then reopened, I found out that all my translated segments had gone - the whole chapter was highlighted in blue instead. The glossary I added was still present, and occasionally the fuzzy  matching would identify some translation memories, so I could recover some of my work. Rolling back to backups didn't fix the issue.
    +
     What fixed the issue was creating a new project and using two different language codes in the Source and Target fields.  So it seems that OmegaT can't have the same language code in those fields; however, this is not explicit.
    +
     Would it be possible to:
     1. throw an error if the user inserts the same language code in the two fields when creating the project
     2. or at least mention this in the user manual?
    
    • assigned_to: Jean-Christophe Helary
     
  • Jean-Christophe Helary

    Thank you Andrea for the tracker. This item will handle your second point.

    For the first one, should be registered separately in the Feature request tracker, with a link to this one.

     
  • Jean-Christophe Helary

    • status: open --> open-fixed
     
  • Jean-Christophe Helary

    • status: open-fixed --> open
     
  • Jean-Christophe Helary

    • status: open --> open-fixed
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.