Menu

#1315 Terminology issue raised when there's no target term in glossary

6.1
open
nobody
5
11 minutes ago
2026-02-06
msoutopico
No

Context

Glossary entries have three fields: source term, target terrm, definition or note

However, glossaries might be monolingual, including only term and definition (a definition helps the trarnslator understand the term).

In those cases, the target term slot is empty (e.g. in a TSV file):

term\t\tdefinition

Actual behaviour

Terminology check (i.e. glossary adherence) understands the empty target term slot as an actual term and expects to find that empty string in the translation, but doesn't find it and raises the issue.

Expected behaviour

No terminology check runs (and no terminology issue is raised) for glossary entries that don't have a target term.

Sample

OMT package attached.

1 Attachments

Discussion

  • feng

    feng - 19 hours ago

    I try to write some codes to implement this feature. Here is the link for this pull request: https://github.com/omegat-org/omegat/pull/2023

     
    • msoutopico

      msoutopico - 3 hours ago

      Hi @feng, thank you so much. I have run OmegaT from branch fix/bugs-1315-empty-target-term-warning in your omegat fork and I cannot reproduce the bug. I don't have the technical insight or the authority to review your PR but it seems a fix for the issue I was reporting. Congrats!

       
  • Jean-Christophe Helary

    Thank you @msoutopico for checking the code !

     

Log in to post a comment.

MongoDB Logo MongoDB