• TBX Dialect: This affects 2 things:
    1. The TBX file header, against which validity is checked
    2. The available predefined TBX fields in the mapping. If you choose Core, you have (almost) no mapping options, while Basic provides the most detailed list of fields.
  • Resolve Note Fields: This is a non-standard convention that Glossary Converter defines to allow round trip conversions Glossary -> TBX -> Glossary for undefined fields. If you have a field in your source (for example Excel) that is not valid in TBX, like Customer, it gets converted to a generic note field. Normally that would be <note>Acme</note>, and you'd lose the original field name. So instead it is converted like this: <note>Customer: Acme</note>. On back-conversion, the value is split at the first colon, and the left part is used as the field name.

This obviously only works if TBX note fields follow the convention, i.e. when they were created by the Converter. If there is no colon in the value, it will just convert to a field called note in the glossary.

  • Use TBX V3 Mapping File: If you don't use a mapping file, your data will be treated as follows:
    • glossary -> TBX: all fields become generic note fields
    • TBX -> glossary: all TBX fields will be created with their original field names and values

The only difference between dialects in that case is the TBX file header.


Created with the Personal Edition of HelpNDoc: News and information about help authoring tools and software