Double quotes of the source file will be converted to typographical quotes if they are supported by the destination format. The following ASCII simulation demonstrates how it works:
Double ""quotes"" 66 99 Double quotes
If you want to display two quotes you have to use ("")text("") instead.
Please note:
Like double quotes UDO can convert double apostrophes into typographical apostrophes:
double ''apostrophes''
will become
double `apostrophes'
If you want to display two apostrophes you have to use ('')text('') instead.
Please note: The switch !no_quotes [ ] switches off the conversion of these double apostrophes, too.
If you want to insert non-breaking spaces between two words you have to use the tilde (~). Non-breaking spaces are also useful to stop UDO and the other formats from breaking lines between two words.
Converting to an ASCII format UDO replaces this tildes by blanks. Converting to other formats UDO replaces this tildes by commands that have the same effect.
LaTeX: | ~ |
HTML: | |
RTF: | \~ |
WinHelp: | \~ |
If you want to display a tilde you have to use !~ instead.
Please note: If you use a tilde inside an external link UDO won't convert it.
UDO supports — did you think anything else — dashs like in this sentence.
Dashs are supported by LaTeX, Windows Help and RTF. Converting to other formats UDO will replace `---' and `--' by a single `-'.
If you want to display three or two `-' you have to use (---) or (--).
In an UDO source file you can use "higher" characters without having to know how a character has to look like in a destination format like LaTeX or Windows Help. So you can enter a German `ß' without any fear, UDO converts it for you and it knows that this has to be ß for HTML or {\ss} for LaTeX.
UDO expects files containing chars of the system charset of your operating system. If you run UDO on a MS-DOS computer UDO expects text files that are written with the IBM PC character set by default. If UDO runs on an Atari computer UDO will expect the TOS character set by default.
But UDO can manage file that are written with another character set, too. You have simply to tell UDO which character set your source file uses with the following commands:
!code_dos: | IBM-PC, MS-DOS |
!code_hp8: | HP Roman 8 |
!code_iso: | ISO Latin 1, Windows ANSI |
!code_mac: | Apple Macintosh |
!code_tos: | Atari ST |
There are some things you have to remember. Some character sets contain characters that aren't available in another one. So you shouldn't use characters from the PC graphic character set or the Hebraic characters of the Atari character set because they can't be printed in formats like LaTeX, Windows Help, RTF or HTML. In this case UDO prints an error message. You should remove these characters from your source file and find another solution.
If source files are converted that don't use the character set of the operating system UDO is running on the limitations are even higher. In the first step UDO will convert the characters into ISO Latin 1. In the second step UDO will convert the ISO Latin 1 characters into the character set of the current operating system. In some cases there's is no possibility to convert the characters without any loss. In such a case UDO will print an error message.
Please note: If I've forgotten any character or a character is converted in a wrong way please send a bug report!