Glossary Converter is not designed to be a lossless roundtrip converter between different formats (although it's getting closer...). Field support is mainly there to allow the display of fields when a termbase is used in Studio. There are unfortunately a few restrictions in field handling.


  • For a standard spreadsheet (no annotated headers), you can not have fields of the same name on multiple levels. For example you can't have a Note field on both term and index level: two columns with the same name will be treated as multiple fields on the same level. When you convert a termbase with such a setup to a spreadsheet, you get just these multiple columns with the same header, A lossless round trip with such data is not possible. For example, a termbase with a Note field on both index and term level would result in the following table. On conversion back to a termbase, both notes would be either term or index level. 

    This will put both fields on the same level in the termbase:

English

Note

Note

power cable

Need to verify US English

Redefined in 2010



This can be fixed by using annotated field headers. The following table is created, which then will correctly convert back to a termbase with fields on two levels: 


>>L<<English

>>I<<Note

>>T<<Note

power cable

Need to verify US English

Redefined in 2010



  • Fields with line breaks in them are handled OK in xlsx and xls format. In txt or csv formats, the line breaks are removed, since Excel itself does not handle this very well.

Created with the Personal Edition of HelpNDoc: Full-featured multi-format Help generator