This section lists the messages produced by mmltomif, along with their explanations. Words in italic indicate variable words in a message. A line number is printed along with most messages when they appear on the screen.
MML MSG: Message_String.
Not an error; generated by a user <Message> statement.
MML: Bad Option: Character.
mmltomif did not recognize this option character. The option is ignored.
Bad Boolean: Unexpected_String.
mmltomif expected to see Yes or No. The value No is assumed.
Bad LRCD: Unexpected_String.
mmltomif expected to see Left, Right, Center, Decimal, or LeftRight.
Bad Real Number: Unexpected_Char.
A nonreal number character appeared in the middle of a real number.
Bad Style: Unexpected_String.
mmltomif expected to see Arabic, LCRoman, UCRoman, LCAlpha, or UCAlpha.
Bad Unit: Unexpected_String.
mmltomif expected to see a valid unit (inch, cm, and so forth).
Bad Spacing: Unexpected_String.
A unit or number used to define the spacing before or after a table or paragraph is not valid. See discussion under unit.
Bad Language: Unexpected_String.
Language specified in the <!DefinePar> statement is not supported by FrameMaker.
Bad TMB: Unexpected_String.
You made a table cell entry without a top, bottom, or middle definition.
Bad Place: Unexpected_String.
In your paragraph or table definition, the placement value given is invalid.
Bad Title Place: Unexpected_String.
The placement value given for the table title is invalid.
Bad Angle: Unexpected_String.
The font statement given for the font angle is invalid.
Bad Digit: Unexpected_String.
You have provided an invalid number for a command.
Bad Hex Digit: Unexpected_String.
You have expressed something in hexadecimal representation and the representation is invalid. An explanation of valid representations is under the DefineChar command.
Can't Find File filename.
mmltomif can't find the specified input file. Make sure that the file exists, and that you have read access to it; then try again.
Didn't Find End Comment n.
The comment that began on the specified line did not end by the time the file was completely read.
Can't Open File filename.
mmltomif couldn't find the named include file. Make sure that the file is in the correct format and that you have read access to it; then try again. If this message still appears, close some open files or windows and try again.
Cant Open Tmp File.
mmltomif couldn't open its temporary file. Make sure you have write access to
/tmp, your home directory, or the current directory; then try again. If this message still appears, close some open files or windows and try again.
Cant Write File filename.
mmltomif couldn't open the specified output file for writing. Make sure you have write access; then try again. If this message still appears, close some open files or windows and try again.
X Needs Ending Space.
Characters specified with \x must end with a space.
Expected String Unexpected_Char.
mmltomif expected to see a string starting with a double quotation mark (") rather than the unexpected character shown in the message.
Fatal.
mmltomif encountered a problem from which it can't recover. Write down the error message and contact your Frame technical support representative.
Input Stack Overflow.
There are too many nested include files (maybe in an include loop). The maximum nesting depth is 100.
Internal Error
mmltomif encountered an internal error. Please contact your Frame technical
support representative.
Junk At End: Junk_String.
mmltomif expected to see a a right angle bracket (>).
Keyword Too Long.
While looking for a macro name or other keyword, mmltomif found a very long token (over 1,000 characters). Check the MML file for a syntax error and try again.
Not Finished Defining Character.
mmltomif encountered a <!Define...> statement within a <!Define...> statement (for example, a <DefineChar> statement within a <!DefinePar> statement). You must finish the first <!Define...> statement before beginning another.mmltomif ignores the first <!Define...> statement and continues reading the file. The results, however, are not likely to be what you intended.
Out Of Memory
mmltomif was unable to complete the translation of the MML file because it ran out of memory. To free memory for mmltomif, quit some FrameMaker document windows or terminate other processes.
String Too Long.
A very long string was found. The maximum string length is 1000 characters; characters beyond that are truncated.
Tab Stops
The statements <TabsStopType>, <TabStopLeader>, and <TabStop> can appear only within a <TabStops> statement.
Too Many I Options.
The maximum number of -I options is 100. mmltomif exits.
Unexpected Right Brace.
A right angle bracket (>) with no matching left bracket (<) has appeared.
Undefined Macro: Macro_Name.
There is no definition for this macro. The undefined macro is ignored.
Undefined PgfTag: Paragraph_Name.
The default paragraph tag used for the table cell has not been previously defined in a <!DefinePar> statement.
Undefined TblTag: Table_Name.
No <!DefineTbl> statement exists for this table tag.
Undefined Ruling: Rule_Name.
The rule named has not been defined in a <!DefineRule> statement.
Null Name
There are name tag indicators, <>, with no name between them.
Hash Table Overflow
You have given more definitions (macro, paragraph, font, and/or table) than the program can accommodate. The limits are 10,000 for Unix systems and 3,000 for Macintosh.
Tab Buffer Overflow
You have entered too many tab stops in your paragraph definitions. The limit is 1000 characters.
Usage: mmltomif [-Ipath] [input [output]]
You started mmltomif in a shell window without any parameters. Restart
mmltomif with the parameters shown, where path is the path of the MML input file, input is the input filename, and output is the output filename.