Error messages
UDO prints all error messages, warnings and hints that appear when
converting the source file to files with the suffix
.ul?. Each message is constructed the
following way:
Error: :
Warning: :
Hint: :
If you want to avoid these errors, warnings and hints open the
printed file, go to the printed line and try to find the error. Start
with the first printed error and convert your source file once again.
A lot of messages will disappear because they depend on earlier
errors.
...
called twice
-
The printed command was used twice or more inside the source
file even if it is only to be used once.
...
expected
-
UDO has expected the printed command. Please check if all
environments were finished with the correct command or if a
!begin_* is missing.
...
followed by ...
-
You have finished an environment with an incorrect command or
you have forgotten to finish it. Another possibility is that you have
misplaced the !end_* command
...
ignored inside preamble
-
It is only allowed to use the printed command inside the main
part of the source file. That means you have to place it after
!begin_document.
...
ignored outside preamble
-
It is only allowed to use the printed command inside the
preamble of the source file. That means you have to place it before
!begin_document.
...
maybe not available in (!LaTex)
-
The printed character cannot be used for LaTeX. Please try to
use another character
...
not active
-
A text style or a footnote shall be finished even if it isn't
active. Please note that the placeholders contain a capital letter for
activating a text style. The placeholders that finish a text style
contain a small letter.
...
not available in ISO Latin 1
-
ISO Latin1 doesn't contain the printed character. Thus, UDO
cannot convert the printed character.
...
not available in this charset
-
The printed character isn't available in the system character
set. Thus, UDO cannot convert it. Please try to avoid the printed
character.
...
still active
-
A text style or a footnote shall be started even if it is still
active. Please note that the placeholders contain a capital letter for
activating a text style. The placeholders that finish a text style
contain a small letter.
...
without ...
-
You wanted to finish an environment even if it wasn't started
before.
- !else without !if
-
You have used the !else command but you
haven't started a query with !if,
!ifdest etc.
- !endif without !if
-
Your source file contains an !endif command
but you haven't startet a query with !if,
!ifdest etc. You will also get this error message if
you use !end_ignore without according
!begin_ignore.
!item
outside environment
-
You have used the !item command outside an
itemization, enumeration, description or list.
- check this paragraph
-
UDO prints a filename and a line number where you can find the
reason for the upper printed error message.
- couldn't open <file> (pass1)
-
UDO couldn't open the printed file in the first of two passes.
- couldn't open <file> (pass2)
-
UDO couldn't open the printed file in the second pass. Please
check the filename you have used for !include.
- couldn't open destination file
-
UDO couldn't open the destination file. Please check the
filename or remove file protection of the existing file.
- couldn't open hypfile
-
UDO couldn't open the hyphenation file. Please check the
filename or remove file protection of the existing file.
- couldn't open logfile
-
UDO couldn't open the log file. Please check the filename or
remove file protection of the existing file.
- couldn't open source file
-
UDO couldn't open the source file. Please check the filename.
- couldn't open treefile
-
UDO couldn't open the tree file. Please check the filename or
remove file protection of the existing file.
- couldn't read BMP header
-
The printed file isn't a Windows Bitmap or the file doesn't
exist.
- couldn't read IMG header
-
The printed file isn't a GEM image or the file doesn't exist.
- couldn't read MSP header
-
The printed file isn't a MSP image or the file doesn't exist.
- couldn't read PCX header
-
The printed file isn't a PCX image or the file doesn't exist.
- couldn't replace (!ilink)
-
A manual image link couldn't be replaced. You are allowed to
use up to 200 internal and external links and internal images
inside each paragraph. Split up the paragraph in two or more parts or
delete some links.
- couldn't replace (!img)
-
An internal image couldn't be replaced. You are allowed to use
up to 200 internal and external links and internal images
inside each paragraph. Split up the paragraph in two or more parts or
delete some links.
- couldn't replace (!link)
-
A manual link couldn't be replaced. You are allowed to use up
to 200 internal and external links and internal images inside
each paragraph. Split up the paragraph in two or more parts or delete
some links.
- couldn't replace !xlink
-
An external link couldn't be replaced. You are allowed to use
up to 200 internal and external links and internal images
inside each paragraph. Split up the paragraph in two or more parts or
delete some links.
- couldn't write IMG header
-
UDO couldn't open the printed file for changing the image
information. Maybe the file doesn't exist or it is write protected.
- definition contents longer than ... characters
-
The contents of a definition exceeds the maximum number of
characters. Please shorten your definition contents.
- definition name longer than ... characters
-
The name of a definition exceeds the maximum number of
characters. Please shorten your definition name.
- language ... not supported
-
The printed language isn't supported by UDO (yet) or you have
written the language in a wrong way.
- link destination undefined
-
The destination of a manual link isn't defined. That means
there's no chapter or label exisiting with the given name
- macro contents longer than ... characters
-
The contents of a macro exceeds the maximum number of
characters. Please shorten your macro contents.
- macro name longer than ... characters
-
The name of a macro exceeds the maximum number of characters.
Please shorten your macro name
- memory allocation failed
-
The destination of a manual link isn't defined. That means
there's no chapter or label exisiting with the given name.
- missing parameter(s)
-
A command needs a specific numer of parameters and you have
used not enough parameters. Check the command and add the needed
parameters.
- odd number of ''
-
The source file contains an odd number of double apostrophes.
UDO will find this error at the end of a chapter so check the chapter
above the printed line number.
- odd number off ""
-
The source file contains an odd number of double quotes. UDO
will find this error at the end of a chapter so check the chapter
above the printed line number.
- overfull line
-
A line of a verbatim environment is longer than the value of
!parwidth. Try to cut the line or increase the paragraph
width.
- source and destination file are equal
-
You have tried to read and write the same file. Check your
command line options.
- string buffer overflow
-
Please contact the author.
- too many aliases used
-
Your source file contains too many !alias commands.
Please delete some unimportant aliases or contact the author to get a
special version of UDO.
- too many columns used
-
Your source file contains a table with too many columns.
- too many defines used
-
Your source file contains more than 128 definitions.
- too many environments used
-
You have used too many environments nested into one another.
Try to layout your source file less complex.
- too many files opened
-
During the conversion too many files were opened. Check your
source file if you constructed a recursive include.
- too many hyphens used
-
Your source file contains too many Hyphenation patterns. Delete
some of them and use local Hyphenation marks
- too many items inside enumeration
-
You have used too many items inside an enumerate environment
where items are marked with letters. Reduce the ammount of items to 26
or use an itemize environment instead.
- too many labels used
-
Your source file contains too many !label
commands. Because UDO handles chapters and aliases like labels, too,
this error message can appear when using only some labels. Please
delete some unimportant labels or aliases or contact the author to get
a special version of UDO.
- too many labels used in table
-
Your source file contains too many !label
commands.
- too many macros used
-
Your source file uses more than 1000 macros
- too many nodes used
-
Your source file uses too many chapters. If possible try to
merge some chapters or contact the author to get a special version of
UDO.
- too many parameters used
-
A command or placeholder was called with too many parameters.
Check the command and look for additional information inside the
command index.
- too many rows used
-
Your source file uses a table with too many rows.
- too many words used inside paragraph
-
A paragraph of your source file uses too many words. Try to
split up the paragraph into two or more parts.
- too short line
-
The printed line is too short and you will see an ugly right
margin. If you use justification this error message says that there
were inserted too many blanks. Try to insert Hyphenation marks or use
the !sloppy command to suppress this type of error
message.
- unexpected end of line in command
-
Your source file contains a placeholder that wasn't finished
correctly.
- unknown command
-
UDO doesn't know the printed command. If you want to use a word
a the beginning of a line that begins with an exclamation mark you
have to mark it with a slash (
/
).
- use (!V) and (!v) in one line
-
Something's still missing here...
- use (!xlink [text] [topic@foo.hlp])
-
The construction of an external link for Windows Help is
incorrect
- wrong number of parameters
-
You called a command or placeholder with the wrong number of
parameters. Check the command index for additional information
- xlink needs WinHelp destination topic
-
The construction of an external link for Windows Help is
incorrect. Here the name of the page is missing.
- xlinks needs WinHelp destination file
-
The construction of an external link for Windows Help is
incorrect. Here, the name of the Windows Help file is missing.
Copyright © www.udo-open-source.org (Contact)
Last updated on May 19, 2014