A Command Line Interface is an older way of automating program output. A more modern way to automate program output is with an API (Application Program Interface). DBT has both a Command Line Interface and an API.
DBT can be run at the Command Line.
Here is an example: DBTW /braille:Romeo constitution.htm<Enter>
Here is the syntax:
Usage: Program Path
[/help]
[/print | /braille:Embosser Name | /simulate | /brf:<name> | /prf:<name>]
[/Pagesize:<rows>x<columns>]
[/Copies:nn]
[/Template:<name>]
[/wordstylemap:<name>]
[/RemoveEmbosserInfo | /RemovePrinterInfo /RemovePageInfo]
[/dumpstyles:<name>]
[files]
Some carriage returns to make this readable. The brackets indicate that this material is optional. The vertical bar (|) means you can choose between options (print output, braille output, simulated braille, braille file, or print file)
Some options, such as RemovePageInfo have been added to help generate "generic documents" for wide distribution. Some of these options have been added to aid the process of writing the documentation to DBT.
/RemoveEmbosserInfo -- Removes the embosser information embedded in the document(s), including all settings in Document, Embosser Setup. Saves the result(s) back in-place. Exits if no further processing is required.
/RemovePrinterInfo -- Removes the ink printer information embedded in the document(s), including all settings in Document, Printer Setup. Saves the result(s) back in-place. Exits if no further processing is required.
/RemovePageInfo -- Combines the effects of /RemoveEmbosserInfo and /RemovePrinterInfo. Note that it isn't actually possible to use the two separate switches together; /RemovePageInfo is *required* if you want strip both printer and embosser information from a document.
/dumpstyles:<name> -- Writes the styles definitions for a document into the specified "dump" file. The behavior of the switch is undefined if more than one document file is specified after this switch. After this switch is processed, DBT will exit if there is no further processing to be done.
/dumpstyles_xml:<name> -- This works just like /dumpstyles, except that the "dump" file is an XML format.