DOKK / manpages / debian 12 / udo / udo.1.en
udo(1) General Commands Manual udo(1)

udo - convert files from UDO into different formats

udo [-adDghHilmnpqrstvwWxy] source file
udo [-adDghHilmnpqrstvwWxy] -o destination file source file

UDO converts files from the UDO format into Apple-QuickView, ASCII, HTML, Texinfo, Linuxdoc-SGML, Manualpage, Pure-C-Help, Rich Text Format, ST-Guide, LaTeX, Turbo Vision Help or Windows Help.

Using the first method UDO prints the destination format to the standard output (STDOUT) and error messages to the standard error output (STDERR). Using the second method UDO writes the destination format to the destination file and error messages to a log file with the suffix .ul?.

You have to pass single options to UDO : -al isn't the same as -a -l!

The name of the source file has to be the last option.

The source file will be converted to ASCII.
The source file will be converted to AmigaGuide.
The source file will be converted to Apple QuickView.
A C sourcecode will be generated from the source file. Normal text becomes comment, the content of the sourcecode environment becomes C code.
Additional checkings will be activated.
Suppresse the generation of index files.
The source file will be converted to David's Readme Compiler format.
Set the symbol `symbol' which can be tested in the source file with !ifset
Force files with long file names.
Force files with short file names (8+3).
The source file will be converted to PDFLaTeX sourcecode.
The source file will be converted to HP Helptag SGML.
Outputs a help page and quits.
The source file will be converted to HTML.
The source file will be converted to HTML-Help.
You have to press a key before UDO finishes.
The source file will be converted to GNU Texinfo.
The source file will be converted to OS/2 IPF format.
The source file will be converted to LyX.
When using the Option -o UDO doesn't save a log file.
The source file will be converted to a manualpage.
Generate a C header file with jump id's for the WinHelp format.
Generate a GFA Basic header file with jump id's for the WinHelp format.
Generate a Pascal header file with jump id's for the WinHelp format.
Generate a VisualBasic header file with jump id's for the WinHelp format.
The source file will be converted to Nroff.
UDO writes the output into the file named "F".
A Pascal sourcecode will be generated from the source file. Normal text becomes comment, the content of the sourcecode environment becomes Pascal code.
The source file will be converted to Pure C Help.
The source file will be converted to PostScript.
UDO won't print anything to STDOUT or STDERR.
The source file will be converted to RTF.
Generate an additional project filr (.upr). There information about outfiles, infiles, nodes and index entries are listed.
The source file will be converted to ST-Guide.
When using this option UDO won't save a destination file.
The source file will be converted to LaTeX.
When using this option UDO will save a file with the suffix .ut?. In this file you will see a tree with all files your source file includes.
Generate one file in udo format containing all included source files. This allows one to put all source files into one udo file.
UDO will print some status information wile converting the source file.
Outputs version information and quits UDO
The source file will be converted to Turbo Vision Help.
The source file will be converted to Windows Help.
The source file will be converted to Windows Help 4.
Warnings will be suppressed. Error messages will still be printed.
The source file will be converted to Linuxdoc-SGML.
UDO doesn't save a file with syllabification hints (.uh?) when using the option -o.
-@ F
UDO will read the options from the file named "F".

Convert the source file `file.u' to ASCII (default) and print the output to the standard output and error messages to the standard error output.

Convert the source file `file.u' to LaTeX and write the output to the file named `output.tex'. Warnings, error messages and additional information will be written to the log file named `output.ult'.

Convert the source file `file.u' to ST-Guide and write the output to `file.stg'. UDO won't save a log file or a file with syllabification patterns.

UDO looks for the file udo.ini in your home directory if

UDOPATH doesn't exist.

Sets the language UDO shall use for error messages if neither LC_ALL nor LC_MESSAGES exists.
If this is set to `german' UDO prints German messages. If this variable doesn't exist LC_MESSAGES it tested instead.
See LC_ALL If this variable doesn't exist, too,

LANG is tested instead.

UDO looks for the file udo.ini in the directory defined by this variable. If UDOPATH doesn't exist HOME is tested instead.

0
Everything was OK.
>0
An error has appeared.

Copyright (c) 1995, 1996, 1997 by
Dirk Hagedorn (Dirk Hagedorn @ MK2, DirkHage@aol.com)

November 8, 2003 webmaster@udo-open-source.org