There are 3 things you can use the command line for:
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" "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.
If both Excel and Libre/Open Office are installed, the converter will try to use Excel. In rare cases, Excel does not work, even though it is installed. In that case, you can try to install Libre/Open Office, and enforce its use. To do so, pass in the command line parameter -l, or use the file GlossaryConverter_NoExcel.cmd that is by default installed in C:\Program Files (x86)\SDL OpenExchange\Glossary Converter.
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 Excel is 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: Full-featured EPub generator