Menu

#409 Glossary: unclear display if combined entries contain a ","

2.0
closed-fixed
Interface (55)
5
2009-05-14
2009-02-22
No

In the glossary, combined entries (e.g., drive = lecteur, disque, unité de disque) are separated by a comma.

This can lead to an unclear display, especially with regards to numbered comments, if one of the entry contains a comma.
drive = lecteur
drive = disque, unité de disque
are combined as
drive = lecteur, disque, unité de disque

To solve this, combined entries containing a comma should be bracketed by ".

With the above example, this will give
drive = lecteur, "disque, unité de disque"

(Entries containing ; or " are already bracketed by " automatically.)

Didier

Discussion

  • Didier Briel

    Didier Briel - 2009-02-22

    Fixed in SVN (/trunk).

    Didier

     
  • Didier Briel

    Didier Briel - 2009-02-22
    • status: open --> open-fixed
     
  • Nobody/Anonymous

    I know you already put some hard work into this, but I would like to comment anyway.

    An alternative is to use a character that one would very like never find in a glossary, and my vote would be on the pipe (or more properly, a pipe with a space on either side).

    So:

    drive = lecteur | disque, unité de disque

    or you could also end with a pipe:

    drive = lecteur | disque, unité de disque |

    -- leuce

     
  • Didier Briel

    Didier Briel - 2009-02-23

    I considered this option (using the |) and nearly did it that way.

    But then, what happens if the entry contains the pipe? I would still have to do something.

    And what I have done is in line with what Java/OmegaT does already automatically when an entry contains ";".

    (In the end, having the combined entries separator configurable would be the better solution, but it is costly in terms of development time/documentation.)

    Didier

     
  • Didier Briel

    Didier Briel - 2009-05-14
    • status: open-fixed --> closed-fixed
     
  • Didier Briel

    Didier Briel - 2009-05-14

    Closing...
    This bug was corrected in the just released version 2.0.2 of OmegaT.

     

Log in to post a comment.