Download 10 - Docu + Design Daube

7
Other special files
Using hypertext links
When FrameMaker creates a log file, where possible it includes hypertext links as an
additional debugging tool. Each message in a log file has one of the forms shown in the
following examples:
-> /usr/vpg/ch1.fm;
Invalid property specified for element "AFrame".
or
/usr/vpg/ch1.sgm; line 25;
Required attribute "lang" is missing for element "list".
The first part of the message indicates the location of the problem in the source document;
it always includes the source document’s filename. If the source is a FrameMaker
document, such as a rules document or a FrameMaker document being imported or
exported, there is an arrow to the left as in the first example. The arrow indicates a hypertext
link. If you activate the link, the software opens the document to the page containing the
problem. If the source isn’t a FrameMaker document, there is no hypertext link. In this
situation, the description includes the line number in the file, as in the second example. You
must open the file in an appropriate editor.
The second part of the message describes the particular problem encountered. This part of
the message always contains a hypertext link to an explanation of the message.
Setting the length of a log file
Processing documents can produce extremely large log files. In practice, you are unlikely
to look at all pages of an extremely large log file. For this reason and to save space and
time, FrameMaker limits the number of messages it sends to the log file for a given
document. For information on how to change that number, see “Limiting the length of a log
file” on page 70.
Other special files
There are several other file types you must work with in creating a structure application.
These files are discussed in other chapters. For information on creating an EDD, see Part
II, “Working with an EDD.” For information on creating read/write rules files, see Chapter 14,
“Read/Write Rules and Their Syntax.” For information on ISO public entity set files, see
Appendix F, “ISO Public Entities.”
Working with Special Files
72