Menu

#621 Glossary items without translation do not lay out nicely.

SVN
closed-out-of-date
nobody
None
5
2026-02-05
2013-09-28
No

It is allowed to have a glossary item without a translation. For instance, solely for the sake of allowing the translator to understand what the term is about.

The layout goes wrong, an "=" is inserted nonetheless when no translation is present. See picture.

1 Attachments

Discussion

  • Guido Leenders

    Guido Leenders - 2013-09-28

    Also the number goes wrong. It stays at 1. I will upload patch.

     
  • Guido Leenders

    Guido Leenders - 2013-09-28

    Changes made:

    • Priority glossary translations are listed first, then the rest.
    • When no translations are defined, there is no "=".
    • Empty translations are skipped which looks better than "TERM = , TRANSLATION".
    • The number of definitions was often all the time a repeating '1', since the commentIndex was not increased before the "continue".
    • Long lists of translations and definitions are truncated after a number of elements to avoid 20+ entries being almost the same taking up precious screen space.
     
  • Guido Leenders

    Guido Leenders - 2013-09-28

    Patch and results.

     
  • Guido Leenders

    Guido Leenders - 2013-09-28

    Full file.

     
  • Guido Leenders

    Guido Leenders - 2013-09-28

    Patch

     
  • Didier Briel

    Didier Briel - 2013-11-08

    The layout goes wrong, an "=" is inserted nonetheless when no translation is present. See picture.

    There is a translation in the picture, for the second term.

    Empty translations are skipped which looks better than "TERM = , TRANSLATION".

    How do people know which one is which, if the separator is not shown?

    Long lists of translations and definitions are truncated after a number of elements to avoid 20+ entries being almost the same taking up precious screen space.

    I do not agree with that one.

    Didier

     
  • Guido Leenders

    Guido Leenders - 2013-11-14

    Hi, sorry, I was inaccurate.

    Regarding remark 1: Indeed there is a translation in the picture, it is for the second term.

    Regarding remark 2: Yes, good point. Maybe introduce an alternative for "empty string", such that it becomes: TERM = No translation <for definition="" 1="">, <translation definition="" 2=""></translation></for>

    Regarding remark 3: can you elaborate? Our problem is that we have many matches for rather trivial terms. Such as for "TO", which can be a country code or for verbs. One long glossary item pushes down all following glossary items, out of the screen. Therefore we started truncating it after some arguments.

     
  • Hiroshi Miura

    Hiroshi Miura - 2026-02-05
    • status: open --> closed-out-of-date
     
  • Jean-Christophe Helary

    That’s weird. Now OmegaT does not seem to allow for glossary items without target terms. Has there been a change in the code ?

     

Log in to post a comment.

MongoDB Logo MongoDB