HTML is one of the most used target formats being created by UDO. It is also one of the most used formats for online documentations. Therefore, HTML output format generates the most questions, too. Here is the FAQ collection:
In contrast to the other formats UDO saves a separate HTML file for each chapter by default. UDO names these files by using the chapter numbers. The title page and the table of contents will be saved in the file you passed in the command line.
Using the switches !html_merge_nodes, !html_merge_subnodes, !html_merge_subsubnodes or !html_merge_subsubsubnodes you can tell UDO not to save a file for each chapter.
If you use !html_merge_nodes inside the preamble UDO will save only one HTML file that contains the whole text. You should use this option only for small source files.
If you use !html_merge_subnodes UDO will save separate files only for chapters. All sections, subsections and paragraphs of a chapter will be saved inside this file, too.
If you use !html_merge_subsubnodes UDO will save separate files for chapters and sections. The subsections and paragraphs of a section will be saved in the file that contains the text of the upper section.
Finally if you use !html_merge_subsubsubnodes the paragraphs of a subsection will be saved in the file that contains the text of the subsection. UDO will save separate files for chapters, sections and subsections.
Using the command !html_name inside a chapter, section, subsection or paragraph you can tell UDO which filename it shall use instead of using a filename like "01020304.html".
UDO will print on every HTML page a headline that contains the title of the documentation and hypertext links to the previous, next and upper page. UDO uses GIFs for these links that are saved by UDO automatically. The filenames of these GIFs are udo_lf.gif, udo_rg.gif and udo_up.gif.
Using the switch !no_headlines [html] inside the preamble you can tell UDO not to generate these headlines.
If you want to make your own headlines or bottomlines you can use macros at the beginning of each chapter. The following example shows how I added bottomlines to my WWW pages. These pages contain links to the chapters that contain my address, the descriptions of my software and links to other web sites.
!ifdest [html] !define HR
!macro HEAD [ Software | Contact address | Links ] (!HR) !macro FOOT (!I)Last updated (!short_today)(!i) !else !define HR !macro HEAD !macro FOOT !endif
!node Software !html_name software (!HEAD) [...] (!FOOT)
If you convert the source file to HTML, UDO expands the macros that contain the text of the headlines and bottomlines. Because UDO insert links automatically you can jump to the other pages by clicking the entries of the bottomline.
If you don't convert to HTML empty macros are used so that nothing will appear when using !HEAD or !FOOT.
Unfortunately HTML only allows to use tables with or without frames. You cannot use table lines where you want to.
To print a table with a frame you have to add !hline to the line that contains !begin_table. If you don't want a frame don't use !hline. That's all.
By default UDO uses the suffix of the --outfile you used in the command line:
| -o index.htm | .htm |
| -o index.html | .html |
| -o INDEX.HTML | .HTML |
If you use the option (!code [-o !]) UDO uses .htm on operating systems with 8+3-filenames and .html on operating systems with long filenames.
If you use UDO on an operating system that doesn't support long filenames but you have used (!code [--outfile index.html]) and you copy the saved .htm files to a web server, remember this:
outfile. If you use a HTML browser for TOS or DOS this browser will open index.html without any problems even if there's only a file named index.htm.
Use the command !html_bgsound.