There are 2 things you can use the command line for:

  1. Pass one or more files to the converter to automate conversion: termbases and optionally a settings file.
  2. Start in debug mode. This will create a log file, mostly with information about the process of initialising MultiTerm and Libre/Open Office

Batch Mode

If you want to automate the conversion of glossary files, you can use Glossary Converter in a batch file, passing in one or more file paths as parameters and (optionally) a settings file, like this:

GlossaryConverter.exe "C:\GlossaryConverter\testdata\LegalTerms.xlsx"

or this

GlossaryConverter.exe "C:\GlossaryConverter\testdata\LegalTerms.xlsx"  "C:\GlossaryConverter\testdata\GeneralGlossary.csv" -s:"C:\GlossaryConverter\testdata\settings.xml"

If no settings file is provided, the default settings are loaded from C:\Users\<user name>\AppData\Local\SDL OpenExchange\GlossaryConverter\settings.xml

If any user interaction is required, the dialogs (languages, overwrite file confirmation) will still be displayed. For silent conversion, make sure all languages and fields are defined in the settings file, and all target files have been deleted (to avoid the delete confirmation dialog). Also make sure that the flag  <AlwaysShowFieldsDialog> in the settings file is either set to false or missing altogether.

Start in Debug Mode

If there is an error that cannot be diagnosed by the error message and data alone, it's possible to start the program in debug mode. This will create a log file with more details. It is mainly useful if LibreOffice or MultiTerm are not properly loaded. To invoke it, pass in the command line parameter -d, or use the file GlossaryConverter_Debug.cmd that is by default installed in C:\Program Files (x86)\SDL OpenExchange\Glossary Converter. On program start, you will see a message with the location of the log file. You can send this file to support, together with any other details.

Created with the Personal Edition of HelpNDoc: Easily create CHM Help documents