4.10 Messages

4.10.1 Messages related to reading and parsing commands

4.10.2 Messages related to reading the rules file

4.10.3 Messages related to reading the lexicon file

4.10.4 Messages related to reading the grammar file

4.10.5 Messages related to recognizing or generating a form

4.10.6 Messages related to memory

This section lists the various error and warning messages you may encounter. They are listed in numerical sequence and are generally grouped according to the type of error or warning. A warning means that the operation in progress has successfully completed, but an anomalous condition may have resulted. An error means that the operation in progress could not be successfully completed and was therefore prematurely terminated. Only in the case of a memory error is the PC-KIMMO program aborted and control returned to the operating system. Note that in the following error messages the words printed in italics are not literal but are cover terms for a set of items of the type suggested by the term. For instance, when the error message "Missing keyword in command-name command" actually appears on the computer screen, the term command-name will be replaced by a specific command name, such as load or set.

4.10.1 Messages related to reading and parsing commands

ERROR 101 Ambiguous command: command-name

command-name did not specify a unique command. Type more of the command name to insure that it is not ambiguous.

command-name is not a valid command. Type ? or help for a list of valid commands.

Expected a keyword to be used with the command. Type the command name followed by ? for a list of valid keywords.

Expected an argument to complete the command. Type help followed by the command name for an explanation of what arguments the command needs.

keyword did not specify a unique keyword. Type more of the keyword to insure that it is not ambiguous.

keyword is not a valid keyword. Type the command name followed by ? for a list of valid keywords for that command.

argument was not valid for the command. Type help followed by the command name for an explanation of what arguments the command needs.

Expected a file name with the command.

Cannot find the file filename. Check to see if the file is in the current directory or the path you specified in the command. The command may also be expecting a different default file name or extension.

Check to see if the file is in the current directory or in the path you specified in the command. The command may also be expecting a different default file name or extension.

The rules file must be loaded before the lexicon in order to verify the lexical forms in the lexicon against the alphabet defined in the rules file.

TAKE files can only be nested three deep.

command-name is not a valid command. Type ? or help for a list of valid commands.

Result of issuing the CLOSE command when no log file has been opened.

Occurs when the LOG command is issued when a log file is already open.

EDIT command must specify a file to be edited.

ERROR 118 Bad pathname for CD command

ERROR 119 No grammar loaded

4.10.2 Messages related to reading the rules file

Check to see if the file is in the current directory or in the path you specified in the command. The command may also be expecting a different default file name or extension.

The rules file is incomplete. Check to see if the last table in the file has fewer states than expected.

The first declaration in a rules file must be the ALPHABET declaration.

The ALPHABET keyword does not have any characters listed after it.

The alphabet can contain a maximum of 255 characters.

A character has been repeated in the ALPHABET declaration.

A single character must appear after the NULL keyword.

The character specified for NULL may not also be declared in the ALPHABET.

There is more than one NULL declaration.

ERROR 210 Value given for NULL symbol was already declared for BOUNDARY

ERROR 211 No value given for ANY keyword

A single character must appear after the ANY keyword.

The character specified for ANY may not also be declared in the ALPHABET.

There is more than one ANY declaration.

ERROR 215 Value given for ANY symbol was already declared for BOUNDARY

ERROR 216 No value given for BOUNDARY keyword

A single character must appear after the BOUNDARY keyword.

The character specified for BOUNDARY may not also be declared in the ALPHABET.

There is more than one BOUNDARY declaration.

ERROR 220 Value given for BOUNDARY symbol was already declared for ANY

ERROR 221 Subset name not given

Occurs if there is a SUBSET keyword with nothing after it until the next keyword.

A subset name, if it is a single character, cannot be the same as one of the characters specified in the ALPHABET, NULL, ANY, or BOUNDARY declarations. If the subset name is more than one character, then it is a duplicate of another subset name already declared.

ERROR 224 Subset subset-name contains a nonalphabetic character: character

All characters used in subsets must be listed in the ALPHABET declaration, with the exception of the NULL symbol, which can appear in a subset but is not included in the ALPHABET list.

A character has been repeated.

The only valid keywords in a rules file are COMMENT, ALPHABET, NULL, ANY, BOUNDARY, SUBSET, RULE, and END.

Are you sure the rules do not use an ANY symbol?

Are you sure the rules do not use a NULL symbol?

The BOUNDARY declaration is obligatory. Even if the BOUNDARY symbol is not used in the rules file, it must be used in the lexicon file.

The first nonspace character after the RULE keyword is the opening delimiter of the rule name. A matching delimiter (identical character) was not found in the same line; thus PC-KIMMO will use everything up to the end of the line as the rule name. This is because the rule name must be contained in one line.

Must be a number greater than zero.

Must be a number greater than zero.

State (row) numbers must start with 1 and ascend consecutively.

A state (row) number must be followed by colon (:) or period (.) with no intervening space.

number must not be greater than the specified number of states for the table.

A character in a table's lexical character list is not a member of the alphabet declared earlier in the rules file.

A character in a table's surface character list is not a member of the alphabet declared earlier in the rules file.

Expected a numeric state table entry but found a nonnumeric character.

Occurs if a column header consists of a BOUNDARY symbol is paired with anything but another BOUNDARY symbol; only #:# is allowed.

Either there are no rules in the file or the rules contain only subset correspondences. In the latter case, simple rules listing all the default correspondences are needed.

There is an overlap between two columns of the state table. Issue a show rule command for the rule causing the warning and examine the set of pairs specified by each column header.

The entire set of feasible pairs must be specified by each table. The table is probably missing an ANY:ANY column.

NULL:NULL is not a legal column header, since it cannot be a feasible pair.

ERROR 245 Value given for COMMENT symbol was already declared as alphabetic: character

ERROR 246 Value given for COMMENT symbol was already declared for NULL

ERROR 247 Value given for COMMENT symbol was already declared for BOUNDARY

ERROR 248 Value given for COMMENT symbol was already declared for ANY

ERROR 249 Invalid keyword for twolc rules files: keyword

ERROR 250 SUBSETs not allowed in twolc rules file

ERROR 251 Missing opening delimiter for the name of a rule

ERROR 252 No rules defined: filename

ERROR 253 Invalid column number number in alignment for correspondence pair char:char

ERROR 254 Pair occurs in alignment twice: char:char

ERROR 255 Too few columns in alignment for correspondence pair char:char

ERROR 256 Too many columns in alignment for correspondence pair char:char

ERROR 257 RULE number (name) - no feasible pairs specified for column number

4.10.3 Messages related to reading the lexicon file

Check to see if the file is in the current directory or in the path you specified in the command. The command may also be expecting a different default file name or extension.

ERROR 302 Missing alternation name

The ALTERNATION keyword must be followed by an alternation name.

An ALTERNATION keyword was found with no following alternation name or list of lexicon names.

ERROR 305 No lexicon sections in lexicon file filename

A lexicon file must contain sublexicons.

The keyword LEXICON must be followed by a sublexicon name.

This will not necessarily result in a processing error if this is what you intended to do.

A lexical entry is missing its continuation class element.

A name appearing in the continuation class field of a lexical entry must be the name of an ALTERNATION that has already been declared.

Each lexical entry must have a gloss element.

The gloss element must be bracketed by matching delimiters (identical characters).

Each character used in lexical items must be listed in the ALPHABET declaration of the rules file.

A lexicon file must as a minimum have a sublexicon named INITIAL.

An INCLUDE file cannot call another INCLUDE file.

An INCLUDE keyword must be followed by a file name.

ERROR 317 Invalid lexicon file keyword: word

The only valid keywords in a lexicon file are ALTERNATION, FEATURES, FIELDCODE, INCLUDE, and END.

ERROR 319 First argument name already used

ERROR 320 Cannot use second argument category twice

ERROR 323 Ignore FIELDCODE fieldcode : no double gloss definition

ERROR 324 Expected lexical item

ERROR 325 No features

ERROR 326 Feature name already defined

ERROR 327 Feature name name not found

ERROR 328 Lexicon name already used in alternation name

4.10.4 Messages related to reading the grammar file

ERROR 501 Grammar file is empty

ERROR 502 Let abbreviation ... has no be

ERROR 503 No rules found in grammar

ERROR 504 Unexpected token before token

ERROR 505 Token not defined by Let

ERROR 506 Let abbreviation be ... has incompatible paths

ERROR 507 Grammar does not begin with Let or rule. It begins with: token

ERROR 509 Features of name produce FAIL

ERROR 510 Too many nonterminals in rule rule

ERROR 511 Incompatible features name

ERROR 512 Feature name not defined by template in grammar

ERROR 513 Incompatible features on node

ERROR 516 + used in grammar rule (repetition not implemented yet).

ERROR 517 expand_psrs called with NULL delimiter.

ERROR 518 Unmatched token in the following formula:

ERROR 519 Attempt to pop_path when current_last is NULL.

ERROR 520 Label label in path not found in rule

ERROR 521 Unexpected token before token

ERROR 522 Incompatible alternatives on path path

ERROR 524 Empty path

ERROR 525 Path not followed by equal

ERROR 526 Invalid disjunction

ERROR 527 structure fails to unify

ERROR 528 Non-number token after $

ERROR 529 Zero reference number number

ERROR 530 Reference number greater than number

ERROR 531 Label name has empty path

ERROR 532 Reference $label not defined above

ERROR 533 Reference not allowed before atom

ERROR 534 Unexpected token ; Skipping to...

ERROR 535 token not defined in Let; Skipping to...

ERROR 536 End of file reached before expected ']' found

ERROR 537 End of file reached before expected '>' found

ERROR 538 Failure to unify < path>

ERROR 539 Let abbreviation redefined

ERROR 540 End of file reached before expected '}' found

ERROR 523 need_nonterm() not found

4.10.5 Messages related to recognizing or generating a form

A lexical:surface pair in a pairs comparison file is missing the surface form.

ERROR 512 Feature name not defined by template in grammar

ERROR 513 Incompatible features on node

ERROR 541 Cannot parse forms without a grammar

ERROR 800 Form [ form ] contains character not in alphabet: character

An input form contains a character that was not listed in the ALPHABET declaration in the rules file.

Could happen if a table does not have an ANY:ANY column.

Probably will never occur!

There are no lexical entries in the named sublexicon.

The lexicon is not loaded.

ERROR 806 Cannot recognize forms without rules

4.10.6 Messages related to memory

The rules and lexicon are too large to fit in memory.

Occurs when the generator or recognizer gets into an infinite loop due to an incorrectly written rule or lexicon continuation.