There is an unrecognized paragraph or character tag used in a table or in your document that is not supported by the translator.

Solution: Don't use the tag.

A table can only have 26 footnotes.

Solution: Use fewer footnotes or split the information into multiple tables.

Character tags shouldn't be applied to whitespace (such as tabs and hard and soft returns). This error message indicates that you've applied a character tag to both parts of a hanging list, including the tab that separates them.

Solution: Apply Default Paragraph Font to the whitespace between the two parts of the hanging list. Tag each part separately.

A major structural error occurred.

Solution: Review the location where the error occurred for potential problems.

An internal warning that information saved about a cross reference was not used. After the translator is completed, this message may be disabled.

Solution: If no cross reference errors exist in the .full file, ignore this message.

An internal warning that should never occur. If it occurs, it is very likely that a cross reference error will exist in the .full file.

Solution: Contact techpubs@sgi.com for assistance.

The <override> tag is not used in the SGIDOCBK DTD and cannot be supported.

Solution: Reformatted the affected part of the document to avoid using the override marker.

A supported tag name could not be found in the listed value. This should be a very rare error.

Solution: Examine the document for potential problems. You can use character tags in variables, but you can't use any character tags that you couldn't use in ordinary text.

The specified tag is no longer supported or else should be tagged as PrintOnly to avoid translation for online display. Use of the tag may work, but should be replaced with an appropriate supported tag when possible.

Solution: Don't use the tag for online content. Find and replace all occurrences of such tags using FrameMaker's Edit > Find/Change tool.

The BNFTerm and BNFRule tags are no longer included in the IPTemplates used by SGI; however, the SGIDOCBK DTD can still translate them.

Solution: Either eplace the obsolete tags with a different paragraph tag such as HangingList or use a TabularList to format the information, or ignore this message.

The AV_error() function was called when the AV_msg string variable was not set.

Solution: This is a programming bug and shouldn't occur for end users.

The translator was unable to convert a special character value into a character entity.

Solution: Search the FrameMaker document for the special character—it may be easiest to find its location by first using grep to search for character_name in the MIF file—and replace it with a standard character. If the character must be used, contact the SGI tools people to update the translator or don't use the character.

This indicates a serious parsing problem occurred and is usually caused by an item being tagged that should not be tagged or by an uncompleted sequence of more than one tag. For example, your file might contain a hanging list that includes a list item without a body.

Solution: Check the tagging and ensure all the components of a structure are present. If the MIF file is valid, then the bug must be fixed in the program.

An anchored frame cannot be processed because it was set up incorrectly or because it is empty.

Solution: Verify that the anchored frame is question is set up correctly and import a figure into the anchored frame. See Chapter 4, “Working With Figures”, for instructions. If a figure isn't ready, you can ignore this error message, view your book without the figure, and import the figure when it becomes available.

A problem occurred while processing the specified frame, usually a margin figure.

Solution: Double check that the frame is used correctly. Margin figures are no longer supported by the translator, so attach the anchored frame to a Fig tag and set it up as you would an inline figure. See Chapter 4, “Working With Figures”, for instructions.

There is a predefined limit to the nesting of MIF tags. In normal usage that limit should never be exceeded.

Solution: The MIF file cannot be correctly processed.

The input MIF file is syntactically incorrect.

Solution: Use FrameMaker to verify if the MIF file is valid or recreate a new one from the original .doc file.

An unknown MIF tag type occurred. This is different than an unknown paragraph type occurring.

Solution: Check that the MIF file is valid.

The predefined limit for the nesting of paragraph types was exceeded. This should never occur in normal usage.

Solution: Verify that the MIF file is valid or contact techpubs@sgi.com for assistance.

This error should never occur with a valid MIF file.

Solution: Check that the MIF file is valid or contact techpubs@sgi.com for assistance.

The translator found MIF data that it could not process. The data is ignored unless other actions are taken.

Solution: The MIF file cannot be correctly processed.

The SGML structure programmed into the translator is flawed and causing an endless loop of elements.

Solution: The MIF file cannot be correctly processed.

The SGML structure programmed into the translator is flawed.

Solution: The MIF file cannot be correctly processed.

The translator code specified an unknown SGML element.

Solution: The MIF file cannot be correctly processed.

The GlossDiv structure is designed to be a container of multiple GlossEntry structures. If GlossDiv is used, it must be used before any glossary entries in order to correctly contain them.

Solution: Move the first GlossDiv paragraph before the first glossary entry or remove all GlossDiv paragraphs.

The use of a GlossaryDef tag or a GlossaryEntry tag has occurred outside of a glossary.

Solution: Move any GlossaryEntry paragraphs into the glossary document or retag the affected paragraphs with more appropriate paragraph tags.

The translator was unable to find all three parts of the part number in the DocNumber paragraph (in the front.doc).

Solution: Make sure the paragraph has a correct part number in the form of xxx-xxxx-xxx.

The revision paragraph is formatted such that it is impossible to determine what content is the rev number and date (in the RecRev.doc).

Solution: Verify that the revision paragraph is formatted correctly.

Heading paragraphs must be nested in the proper order. For example, this error could be caused by a Heading3 occurring after a Heading1 without a Heading2 in between.

Solution: Correct the ordering of the HeadingX paragraphs.

The title for an Example or Code block must come before the example or code block of text.

Solution: Move the title so it is placed directly before the respective block of example or code text.

The Msg paragraph tag is part of a construct for displaying error messages that consists of one or more Msg* paragraph tags followed by one or more MsgExpl paragraph tags. This error indicates that the MsgExpl tag was used without a preceding Msg tag. The MsgExpl paragraph can only be used when it follows either a Msg[1st] or MsgMargin[1st] paragraph.

Solution: Make sure the Msg* paragraphs are tagged and ordered correctly.

A figure is located in a paragraph not tagged as Fig.

Solution: Tag the paragraph containing the figure as Fig.

The translator couldn't find the information about the figure's filename.

Solution: Verify that the figure is imported-by-reference from the print dir and that the Fig paragraph is tagged correctly.

A paragraph tagged as TableTitle has been found outside of a table construct. The TableTitle paragraph can only occur directly before a table.

Solution: Make sure the TableTitle paragraph is located right before the table it labels.

A table figure has occurred outside of a table.

Solution: Make sure the figure in question is located and tagged correctly.

A footnote inserted in a table must be tagged with the TableFootnote tag rather than the Footnote tag.

Solution: Tag the paragraph as TableFootnote.

A nested list paragraph, such as any of the *Ind list paragraphs, must reside within another list.

Solution: Make sure the list paragraphs are ordered correctly.

The BulletSquareInd paragraph tag is only valid when nested in numbered lists. This requirement ensures the formatted SGML will look similar to the FrameMaker document.

Solution: Make sure a List[1st] paragraph occurs directly before the BulletSquareInd paragraph.

The list paragraph tags should be nested in the correct order. For example, a ListInd4.1st shouldn't occur directly after a List1st because it skips the level made up by the *Ind paragraphs.

Solution: Make sure the order of the list paragraphs is correct or reorder the list.

The ListInd4, BulletInd4, and ProcTitleInd4 paragraphs can not be used within a MsgExpl or HangingList.

Solution: Move the affected paragraphs or tag them as an acceptable paragraph type.

A list paragraph must be used before the indented ProcTitleInd paragraph in order for the tag to be valid.

Solution: Verify that a List paragraph occurs before the ProcTitleInd paragraph or use the ProcTitle paragraph instead.

A procedure must be started using the ProcTitle paragraph before ProcSubTitle can be used.

Solution: Ensure this is really a nested procedure that was started with a previous ProcTitle paragraph or change this paragraph to use ProcTitle.

The HangingListInd tag cannot structurally reside in this position in the FrameMaker file. For example, you can't legally put a HangingListInd tag inside a BulletInd list.

Solution: Restructure your list so the tag use is legal.

The translator was unable to create an open tag for the paragraph contents or was unable to create an SGML <PARAGRAPH> tag for a figure definition. This means the paragraph tag or figure definition (using the Fig paragraph tag) has been applied somewhere it's not supposed to be, such as before a ChapTitle. This is a very rare error message.

Solution: Verify that the paragraph structure is correct and that only the ChapNum or AppNum tags occur before a ChapTitle.

This message means that a single heading or other cross reference destination has multiple #9 cross reference markers attached to it. The SGML only allows one ID per tag. In this case, only the last marker ID value will actually be added to the SGML. This may break some cross references unless fixed.

Solution: Determine which marker is incorrect and remove it.

This message indicates a problem with your specification of an inline media object. The allowed types are SGIVIDEO, SGIRGB, SGIAUDIO, and SGIINVENTOR. It's also possible that there's a problem with your syntax: an inline media object should be specified as

type:referenced_filename

If you leave out the colon or introduce extraneous spaces or mistype the type or filename, you may get an error message.

Refer to “InSight Inline Object Tags” in Appendix A for more information.

Solution: Reformat the paragraph correctly.

An InlineTitle can only appear after a InlineObj paragraph.

Solution: Make sure a valid InlineObj paragraph exists.

An unsupported character tag was specified in an index term. You can use character tags in index markers, but you can't use any character tags that you couldn't use in ordinary text.

Solution: Remove the unsupported character tag.

Part of an index term marker seems to have no text.

Solution: Check the index term marker to ensure it has the correct text between the index term delimiters.

A single index term can only have three levels of nesting (for example, primary, secondary, and tertiary). This error is caused by having too many `:' delimiters within a single index term.

Solution: Restructure the index term to have, at most, three nesting levels. If a `:' appears in the index term text, and it is not a delimiter, insert a `\' character in front of it.

This is a very similar to error #212.

Solution: Remove the extra `sort as' information from the index term.

Index term markers cannot be used within a footnote.

Solution: Remove the index marker from the footnote and move it to another relevant part of the document.

The square brackets within an index term are unmatched. This error makes it impossible to correctly parse the index term.

Solution: Correct the syntax of the index term. Refer to “Cross References” in Appendix A and the FrameMaker documentation for more information on creating index markers.

The index term does not have the correct syntax for an index marker.

Solution: Correct the syntax of the index term. Refer to “Cross References” in Appendix A and the FrameMaker documentation for more information on creating index markers.

The content of marker #18 for external book links does not have a space character that delimits the short-title and the ID number. The correct syntax is:

<target_book_short_title><space><target_element_unique_id>

Solution: Correct the marker #18 content.

A marker type 18 with the correct content to start an external book link must occur before the marker type 19 that is placed at the end of the link text. The proper syntax is:

<marker#18>text<marker#19>

Solution: Make sure the proper markers are in the correct locations and that the document title and the markers are tagged as DocumentTitle.

A marker type 17 must have content to create the launchable link. The preferred syntax is:

Launchword:app:parms 

Solution: Correct the marker #17 content. Refer to “Creating Links to URLs” in Chapter 3 for more information.

A cross reference that shows only the generated text of a page number is useless within an online display environment. The link is broken and should be replaced with a more appropriate cross reference type.

Solution: Use a different cross reference format.

A currently unsupported cross reference type was encountered by the translator.

Solution: Change the cross reference to a supported type as shown in Table 3-2.

You can't make a footnote the target of a cross-reference.

Solution: Move the cross reference to point to content outside of the footnote.

The indicated FrameMaker target probably doesn't have anything pointing to it, or a marker #9 was encountered that doesn't have the five unique ID digits at the beginning of the string. It will be impossible to create a cross reference to that destination.

Solution: Remove the unused marker and double-check that the cross reference markers are set up correctly.

A problem occurred when creating an external book link.

Solution: Ensure the external cross-reference link has been established correctly or use the preferred linking method with Markers 18 and 19.