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 (before version 3.0 of the converter) , 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 which 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



Since version 3.0, though, 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



  • When you have multiple fields of the same type on the same level (for example two Note fields for one term), they will be exported to one spreadsheet column, separated by "/" . If you convert such a spreadsheet back to a termbase, this merge is not reversed, there will just be one field with the combined value. For example the following table could result from an entry with two Note fields on the term level. When converting back to a termbase, you would just get one field with the combined column content as its value.

Domain

English

Note

Electronics

power cable

Need to verify US English / Redefined in 2010


  • You need to define a type for each field before you can ignore it. This is necessary because the program needs to know which columns are languages, to properly assign fields. If you close the dialog with any language columns not properly defined, the results may be wrong.
  • 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