The following messages are caused by problems with footnotes in topic files.
4211 Footnote text exceeds limit of 1023 characters.
PROBLEM: The footnote text cannot exceed the limit of 1023 characters.
RESULT: The compiler ignores the footnote.
SOLUTION: Reduce the length of the footnote text, and then recompile.
4251 Browse sequence not in first paragraph.
PROBLEM: The browse sequence footnote is not in the first paragraph of the topic.
RESULT: The compiler ignores the browse sequence footnote.
SOLUTION: Move the browse sequence footnote so that it is first, and then recompile.
4272 Empty browse sequence string.
PROBLEM: The browse sequence footnote for the specified topic contains no sequence characters.
RESULT: The compiler ignores the browse sequence footnote.
SOLUTION: Add sequence characters to the browse sequence footnote, and then recompile.
4292 Missing sequence number.
PROBLEM: A browse sequence number ends with a colon (:) for the specified topic.
RESULT: The compiler ignores the browse sequence footnote.
SOLUTION: Remove the colon or enter a minor sequence number, and then recompile.
4312 Browse sequence already defined.
PROBLEM: A browse sequence footnote already exists for the specified topic.
RESULT: The compiler uses the first browse sequence footnote and ignores the duplicate footnote.
SOLUTION: Remove the duplicate browse sequence footnote, and then recompile.
4331 Title not in first paragraph.
PROBLEM: The title footnote ($) is not in the first paragraph of the topic.
RESULT: The compiler ignores the title footnote, and the topic does not have a title.
SOLUTION: Move the title footnote to the beginning of the topic, and then recompile.
4352 Empty title string.
PROBLEM: The title footnote for the specified topic contains no characters.
RESULT: The compiler ignores the title footnote, and the topic does not have a title.
SOLUTION: Open the footnote window and type the title string next to the topic title footnote character for the topic, and then recompile.
4372 Title defined more than once.
PROBLEM: There is more than one title footnote in the specified topic.
RESULT: The compiler uses the first title footnote and ignores the duplicate title footnote.
SOLUTION: Remove the duplicate title footnote, and then recompile.
4393 Title exceeds limit of 128 characters.
PROBLEM: The title for the specified topic exceeds 128 characters.
RESULT: The compiler truncates the title string at 128 characters.
SOLUTION: Shorten the length of the title string, and then recompile.
4412 Keyword string exceeds limit of 255 characters.
PROBLEM: The keyword string exceeds the limit of 255 characters.
RESULT: The compiler ignores the keyword footnote.
SOLUTION: Shorten the length of the keyword string, or add another keyword footnote for the extra keywords, and then recompile.
4433 Empty keyword string.
PROBLEM: There are no characters in the keyword footnote.
RESULT: The compiler ignores the keyword footnote, and the topic does not have any keywords.
SOLUTION: Open the footnote window and type some keywords next to the keyword footnote character for the topic, and then recompile.
4452 Keyword(s) defined without title.
PROBLEM: The topic has a keyword assigned to it, but no title.
RESULT: The topic will appear as >>Untitled Topic<< in the Search dialog box and in the history list.
SOLUTION: Add a topic title footnote to the topic if you want a title to appear in the Search dialog box when the user selects this keyword.
4471 Build tag footnote not at beginning of topic.
PROBLEM: The build tag footnote marker, if used, has to be the first character in the topic.
RESULT: The compiler ignores the build tag footnote, and the topic is not assigned a build tag.
SOLUTION: Move the build tag footnote to the beginning of the topic, before other footnotes, and then recompile.
4492 Build tag exceeds limit of 32 characters.
PROBLEM: A build tag for the specified topic exceeds the limit of 32 characters.
RESULT: The compiler ignores the build tag assigned to the topic.
SOLUTION: Shorten the length of the build tag to 32 or fewer characters, and then recompile.
4551 Entry macro not in first paragraph.
PROBLEM: The ! footnote (for executing a macro) is not in the first paragraph of the topic.
RESULT: The compiler ignores the macro footnote.
SOLUTION: Move the macro footnote to the beginning of the topic, next to the other footnotes, and then recompile.