UDO universal characters are now properly output in table
Table cells may now have a maximum of 700 lines height.
UDO now supports 18 1-byte codepages and Unicode (UTF-8). Most
important difference to former UDO versions: UDO manages all codepages
internally in Unicode format. Thus you will not get too many
conversion losses any more.
Encodings of UDO documents and target formats can now be
clearly defined by two new commands, independent from the UDO binary:
If an UDO source document line ends with
!\, the following line will be seen as
sequel of the current line. You can even let UDO concatenate multiple
real! lines to a longer logical line. These sequel lines
can be used everywhere in an UDO source document, even in macros and
definitions. If !\ is not found at the very end of a
line, it will be simply ignored and output like normal text.
Chances are that you want to divide the content of a table cell
into multiple lines, in order to get a better readability of the UDO
Outputs all list environmentscompressed (which means
without additional empty lines between paragraphs).
These four new switches offer to make much more distinctions on
environment formatting, compared to the general switch
!use_short_envs. But if you use this general switch, the four
switches mentioned above are without effect, being subsets of it.
Use this additional option with the option mentioned above and
define which symbol should be used as folder in front of
the navigation bar. We recommend to use e.g. the program icon when you
write a program manual.
#54: Former versions inserted a comment with the
file creation date at the very beginning of each HTML file, e.g.
<!- last modified on 29.01.2004 –>. Now a
META tag for file creatione date/time will be added to the HTML
header, when you use this switch.
Until now the anchor UDOTOC"> was
output in front of the table of contents which could be linked to
inside of raw environments.
Now the UDOTOC label will be created whenever a TOC has to be
created for HTML. So you can link to UDOTOC from everywhere inside the
UDO source document without errors.
Bugfix #12: No unnecessary spaces behind tags any
Bugfix #44: When !no_numbers is used,
no chapter numbers are output in front of the chapter names inside the
<link> element of the HTML header.
Bugfix #56: Wrong image size calculation in RTF
output fixed. By mistake the height parameter got the width
Bugfix #17: Error message: couldn't read BMP
header of . No such file or directory. New state: When the first RTF output didn't find the UDO link
image udo_mw.bmp, UDO informs you to
output to RTF once more to create all missing files.
The UDO image will now also be found on TOS compatible platforms.