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.
Also the number goes wrong. It stays at 1. I will upload patch.
Changes made:
Patch and results.
Full file.
Patch
There is a translation in the picture, for the second term.
How do people know which one is which, if the separator is not shown?
I do not agree with that one.
Didier
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.
That’s weird. Now OmegaT does not seem to allow for glossary items without target terms. Has there been a change in the code ?