Menu

#323 Document how to use TBX glossary

3.1.8 - user manual
closed-fixed
3
2014-12-02
2013-11-12
No

I am trying to test OmegaT's TBX capabilities (see this page), and do not understand how to use a TBX glossary. This documentation page does not specify how. Since it doesn't have special directions, I thought maybe I could go to project -> properties -> writable glossary file and select a TBX file (with the .tbx extension, and containing XML entries). When I added another entry and saved the glossary however, it was saved as plain text with a .tbx.txt extension.

I apologize if I have missed the documentation on this. When I opened the mentioned page of documentation, the first things I searched for were the words import and export, so adding a section called Import/Export with adequate explanations on choosing different file types would be ideal.

Discussion

  • Didier Briel

    Didier Briel - 2013-11-13

    Ticket moved from /p/omegat/feature-requests/914/

     
  • Didier Briel

    Didier Briel - 2013-11-13

    I have moved to documentation. TBX glossaries in OmegaT are read-only.
    See in changes.txt 2.2.2

    From changes.txt,in 2.5.2, the ability to use a UTF-8 extension was also added.

    Didier

     
  • Didier Briel

    Didier Briel - 2014-11-24
    • assigned_to: Vincent Bidaux
    • Group: 2.6 --> 3.1.8 - user manual
     
  • Vincent Bidaux

    Vincent Bidaux - 2014-12-02

    Added in Glossary Page:

    In addition to the plain text format, TBX format is also supported as read-only glossaries format. The location of the .tbx file must be within the /glossary folder, but it can be in a deeper folder (e.g., glossary/sub/MyGlossary.tbx).

     
  • Didier Briel

    Didier Briel - 2014-12-02
    • status: open --> closed-fixed
     
  • Didier Briel

    Didier Briel - 2014-12-02

    Closed in the 3.1.8 documentation.

    Didier

     

Log in to post a comment.

MongoDB Logo MongoDB