1
0
mirror of synced 2026-04-18 17:27:25 +00:00
Files
Interlisp.medley/library/lafite/docs/users-guide/LAFITEMANUAL-SEC12.TEDIT
Larry Masinter 1af56ddaa2 Add .tedit files for Lafite manual and release notes -- PDFs on Google Drive (#1209)
* Add .tedit files for Lafite manual and release notes -- PDFs on Google Drive

* use 'docs' for subfolder name; wliminate dup

* Remove duplicate LAFITEMANUAL-GLOSSARY-CUSTOMER.TEDIT

---------

Co-authored-by: Nick Briggs <nicholas.h.briggs@gmail.com>
2023-05-16 19:30:15 -07:00

35 lines
28 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
1
A USER'S GUIDE TO LAFITE
1
A USER'S GUIDE TO LAFITE
TROUBLESHOOTING LAFITE PROBLEMS
1
TROUBLESHOOTING LAFITE PROBLEMS
1
12. TROUBLESHOOTING
LAFITE PROBLEMS
6
Although Lafite is a robust system, you may occasionally encounter minor problems when using it. This chapter describes the most common Lafite problems and how to prevent and/or recover from them.
2
Lafite Confuses You With a Previous User
1
If you log into Lafite with the correct name and password but the Browse menu shows no folders or shows someone else's folders, Lafite may be confusing you with a previous user. If you are running in a sysout in which someone else has been using Lafite, you need to take some action to get Lafite to work on your mail files and in your name. When you change the user identity by logging in as yourself, Lafite notices that the current user has changed and attempts to authenticate you. However, Lafite still doesn't know how you want your Lafite customized; in particular, what your known mail folders are.
To get Lafite to recognize your identity, you should first turn Lafite off by choosing Quit from the status window or by calling (LAFITE 'OFF). Then log in again. Type (GREET) in the executive window; you will be asked for the name of your initialization file if there isn't one on your workstation's disk. When this has been loaded, restart Lafite.
2
File Server Is Slow
1
If your mail files are stored on a remote file server that is particularly unresponsive, the mail server connection over which new mail is retrieved may time out (that is, end communication with your file server) before the file server acknowledges receipt of the messages. The usual consequence of this is that your in-box is not flushed, so your new mail is in two places: your in-box, awaiting retrieval, and your mail file, to which it was just retrieved. A less common occurrence is that the mail server times out partway through the retrieval process, resulting in a Lisp break. You can type ^ after the prompt in the break window to return to the state before the Get Mail started.
If this is often a problem for you, you may want to adopt the following procedure to maintain the flexibility of remote mail files while utilizing the speed and reliability of the local disk. Keep most of your mail files on the remote server, as usual, but keep your Active Mail file, the one to which you usually retrieve mail, on your local disk. Retrieve mail to this file and dispatch from there to your remote files (using Move To) some or all of the messages you wish to keep. Mail files on disk have very predictable performance during Get Mail, which is good for both you and the mail server. Files on disk are also less subject to other vagaries of remote servers (e.g., sudden crashes) that sometimes cause problems with mail files (see figure 27). And if you tend to delete much of your incoming mail after reading it once, you may find it faster to keep your Active Mail on disk, even if your remote server isn't unreliable.
Ðÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿø0_ÿÿßÿþÿÇú÷Áïÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþýîýµ§í¾ç_~í»àwß×ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþýõýµÛm¼[Ïõ÷Ã×ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþýûýU¶Ûj¾Û~í÷õ÷ß»ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþýûþí¶Ûw~Û~í»À÷߃ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþýûþí·÷~çíÇëðA}ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ00ÁˆCç‡qáÄN>@ˆ|qà@@ÅJ•*TˆBB†É Ø „
"!
Š@ÀÇ8¨âŇBB†É Ø „
"!
Š@!@ÅJ•*T¨&A& @<40>à…O<¨ „
 £À
Š@ @Á¨òA"@¹@…H<E280A6> ©  ¢
@@ÀQA"B ‰ …H<E280A6> ©ð„" ¢
Ÿ@@ÀQA&BB…H<E280A6> ©" B
@`@ÀACäGqÄO>@‰ÇÈpCá|!ðÀ@ À00@ÀÀÀ@8!À@À@@@ÀŽqaÅ€XÃ<>4‰aņ€ðàC€XˆâÀ8°@GÀ<08>"‰’&@"dL‰<4C>FI€@ D@"d‰ DÈ@ÀˆÀ
<EFBFBD>ä@"@RD‰DH€@ GÀ >@Qò0ˆGˆÀ
@"@RD‰DH€"@ D @Q"ˆHˆ"À"‰’$@"@¢„‘L™DI€"@ D@"@!<08>"DˆÀȉ"ÀqaÄ@@¢ƒ4iDF€@ C€@ â8ˆ@G†À@ÀÀÀÀ@ÀÀ@@ÆÇXpC‡Å@dˆDHˆÅGDFÅHŠD€DAÅHŠdˆDH‰ÅG„XpC‡ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÁD!â#ˆŽò8ÅJ•*DQ! BÇTQ! BÀpÅJ•*TQâ¡
<EFBFBD>C$@ˆÁT‰B¡
B'ÀøÀ(ù"a B$À(‰a B$@ˆÀ(‰#ˆŽB#€pÀÀÀÀÀÀÁž8 !LJ8@ù! qñÄO€"qÁD B$B$@€ƒb(ˆ@„H6(!ÁD $B$@€Cb(ˆ@„H6(!Á0!<@ð"¢‚(€@<>*(!<00>Æå"@€"¤BD€@ˆ*D!ÁD $"@€B§Â|ˆ@ˆ*|!ÁD B$B"@€¤BDˆ@<40>*D!<01>Á8 !ÄG<|ù$G DpAÁ„"Dqð‡ÀÁ ÀÀÀÀÀÀp À ÀޱaÄG"8,8hÄO,8p£‡,XpâÆ„À<08>"É’$A"DL2D˜$D2ˆ`ˆ<>2dˆ$I„À
<EFBFBD>â<>"0HŸ"|ˆ$D"<`"DøòÈ„À
<02>" H<>"@ˆ$D"D <20>"D<>À"É!&D L"D˜$Ä€"Dˆ`ˆ2d‰I„À±Á8@"8hÃC"<p ‡,Xpò†„À@ @À @ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþ
Figure 27. A warning window opened by Lafite after a file server crash. The folder has ``disappeared'' because the file server is down, therefore the mail folders on it cannot be accessed by Lafite
You can also choose to keep most or all of your mail files on disk, backing them up to a file server periodically. The Lisp Library package CopyFiles is helpful for doing the backup automatically.
2
Mail File Does Not Parse
1
The first time Lafite browses a mail folder, or any time that it suspects that the folder's table of contents is obsolete, it tries to parse the folder. A good mail folder consists of a set of messages, each set off by some internal information about the message's length and status. Parsing a folder consists of scanning for this internal information and building a table of contents from it. If a folder has been damaged in some way, the parsing operation fails, most commonly because a message's stated length is inconsistent with what is actually stored in the file (see figure 28). In this case, Lafite aborts the Browse command and prints a message in the browser window describing how far it got. The information Lafite prints includes the header of the last message parsed and a byte pointer (character position) in the file where the problem was encountered. The mail file is valid up to that pointer position.
"zÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÀÀÀÀÀÀÇ€À8ÀÄ@ÀÄG8°ÐÀÄ@™"É0&Dȉ0ÀLJ<C387>"|€ùÀÄ<08>"@€<08>ÀÄ<08>"‰0&D€@<40>‰0€ÀÄ<07>ˆÐ8€@<40>pЀÀÀÀÀàÀÀÀÀÀÀÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀàÀà ÀàÌ ?`Œ0 üÀc0ã€àÆ>p
<EFBFBD>Àà ` 1€` Œ0 pÀÀc0ã€Æc`p<01>Àà l÷Ìã1žgŸ<<01>ñóÌóç€qñìÌóàÀóìÌãçÀc8ùóÇŸ1€÷žc<‡€ÆøùÇÏ`<øó<><C3B3>Àà ml31³lÌf<01>6m™ŒÀÙ›,Í›`ùlÌ3lÀ Û6lÙ±€÷³cfŒÀÆÍ˜cgf`ðÍ<C3B0>Àà mÆlñ°1¿oÌ~<01>7íù<C3AD>ÀÙ›†ÙûÁ›Øó Àc<Ã6 ٛݳ6~ŒÀÆÍ™ãc~`³Í<C2B3>Àà lvm° 1°l `<01>6
<EFBFBD>Œù˜çùƒÁ›ù³ ÀclÃ6 يݳ6`ŒÀÆÍcc``¶Í<C2B6>Àà m6m°à1³lÌf<01>6m™ŒÀ<01>šc1Á› ÀclÃ6lَݳfŒÀÆÍcgf`¶Í<C2B6>ÀàÍçÌø@?g‡<ù™óÌðç€<01>Ã0óÀóÀc>ÁóÇŸÉž<‡€|øùñÏ;<8<33>ÀàÀ,ÀÀàÀÀàÀÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿ÷ÿÿÿÿÿÿÿÿóÿÿüÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀûïþýÿÿÿÿÿŸÿî ;<3B>~Ço°ïƒ{ï{}àÞ‡¾Á½ß{Ûþ?ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀùÎvüu<C3BC>¶3¯¹×îýÛw}½»g7o¿¹Î»~ïí»~íœß<C593>ßÎuÛíßÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀùͶý±mµí<C2B5>Çî;Ÿ{¿‡g0ï‡Ùλaó»œÃ­ßÎuÛïßÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀú®6ý·mVa¿¶ßžýÛï—±»j·o¿ê­Û¯ó‡~íªßµßÕnÛþ?ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀú­¶ý·nﯿ¶ßîýÛw{¹»j·o¿Ú¬oí¿~íªß¹ßÕ`ÛýÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀûlVüwžìq¿¹ßî
Û<EFBFBD>}Å»m°àƒ»këàÞ¿í¶Á½ÞÛ_X$ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿïÿÿÿ~ÿÿÿÿÿÿÿÿýÿÿÿÿÿÿÿÿþÿÿÿ÷ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿóÿÿüÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿïÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÀÀÀÀÀÀÀ8!À>xpà€‡ä@<40>ò'<27>žà@à ÀÄ@@@@ D!<10>l
Š@A$Hl<><6C>
Š@`ÀÄG,8ðËðàC€ D!l
Š@!DHl<><6C>
Š@!,ØáÇ
 ÀÄ™2D@ L"@ D@<x À„ÀŠŠ@à„OTñP€
Š@ H<>2©$@“" ÀÄ"D@ >@ GÀ P d T‰Š‘@‡ˆT<>P€
@@O<> ©ñƒ> ÀÄH"D@$H @ D H!T‰
Ÿ@!DT<>0€
Ÿ@H ©@ˆ ÀÄH"DH$H"@ D@ D!<10>T‰
@A$T<>0<EFBFBD>
@aH ©$H“" ÀÇ‘"80ÃÈ@ C€>Dpà€‡Dñóä|<7C>ò$<10>|!ðG ¨áÇ<C383>øÀÀ ÀÀ@ÀÀÀÀÀÀÀÀÀ  AÀÀ"xp` 8ˆáÁ4aÆŽ,q`"8qÀ
Ž8pÑÀ,4ñ`XpâŇ<ÀÀ" ˆ  "!L I2<>L"
"D 2 2LA<4C>ˆ€d‰&HÀÀ" ø Ÿ <ˆÃàDãÈŸ H
Ÿ0yà"DAD<><0F>ÀÀ <08> Dˆ""DH<> H@
<EFBFBD>"DA<00>D<>ÀÃ$ˆ "D™!"L$I H‰2
"D‰2 "LIˆ€D‰ÀÁpÀ <háÁ4ÃÆŽ qˆpÑÀ
Ž8xÑÀ"41Dpâ ÀÁÀÂ0à8ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÀ
Figure 28. A browser window showing an error message printed by Lafite when it was unable to parse the mail folder
The most common way to get a mail file into an inconsistent state is to abort a Move To or Update command somewhere in the middle (either manually, or because a remote server crashed). In the case of Move To, the problem is usually that the last message in the file is ``too short,'' since it was never completely written. If the first operation you perform on the destination file after the crash is to browse it, Lafite will (usually) detect this situation and let you browse the file anyway, with a warning that the last message is truncated. Updating the file then corrects the length of the last message. If you neglect to browse the destination file before moving additional messages to it, however, your mail file will not parse.
Another way you can damage a mail file is to get it into a TEdit file, edit it, and save it under the original name. The next time you browse that mail folder, Lafite will be unable to parse the file.
The solution to ``mail file does not parse'' problems is to scavenge the mail file with the Lisp Library package Mail Scavenger, following the instructions in chapter 14, ``Using Lafite-Related Lisp Library Packages.''
2
Table of Contents Is Inconsistent With Mail File
1
Lafite breaks with a message to this effect when it tries to operate on a message that isn't where Lafite thought it was in the file. The most common cause of this is aborting the Expunge command. The appropriate action is to close the browser, select Don't Update, delete the table-of-contents file (the file with -LAFITE-TOC appended to the name) from your directory, and then browse the file again. If this is not successful, you may need to scavenge the file with Mail Scavenger. If you made many changes to the browser (deletions, for example) that you would rather not lose, you can try selecting Write Out Changes Only when you close the browser. This may succeed if the inconsistencies in the table of contents did not intersect with your changes. (LIST ((PAGE NIL (PAPERSIZE Letter FOLIOINFO (ARABIC ) STARTINGPAGE# 51) (0 0 612 792) ((FOLIO NIL (PARALOOKS (QUAD RIGHT) CHARLOOKS (SUPERSCRIPT 0 INVISIBLE OFF SELECTPOINT OFF PROTECTED OFF SIZE 10 FAMILY MODERN OVERLINE OFF STRIKEOUT OFF UNDERLINE OFF EXPANSION REGULAR SLOPE REGULAR WEIGHT MEDIUM INVERTED OFF USERINFO NIL STYLE NIL) FORMATINFO (ARABIC )) (270 12 288 36) NIL) (HEADING NIL (HEADINGTYPE FOOTINGR) (54 27 558 36) NIL) (TEXT NIL NIL (54 54 504 723) NIL))) (PAGE NIL (PAPERSIZE Letter FOLIOINFO (ARABIC)) (0 0 612 792) ((FOLIO NIL (PARALOOKS (QUAD LEFT) CHARLOOKS (SUPERSCRIPT 0 INVISIBLE OFF SELECTPOINT OFF PROTECTED OFF SIZE 10 FAMILY MODERN OVERLINE OFF STRIKEOUT OFF UNDERLINE OFF EXPANSION REGULAR SLOPE REGULAR WEIGHT MEDIUM INVERTED OFF USERINFO NIL STYLE NIL) FORMATINFO (ARABIC)) (54 12 288 36) NIL) (HEADING NIL (HEADINGTYPE FOOTINGV) (54 27 558 36) NIL) (HEADING NIL (HEADINGTYPE VERSOHEAD) (54 762 558 36) NIL) (TEXT NIL NIL (54 54 504 684) NIL))) (PAGE NIL (PAPERSIZE Letter FOLIOINFO (ARABIC)) (0 0 612 792) ((FOLIO NIL (PARALOOKS (QUAD RIGHT) CHARLOOKS (SUPERSCRIPT 0 INVISIBLE OFF SELECTPOINT OFF PROTECTED OFF SIZE 10 FAMILY MODERN OVERLINE OFF STRIKEOUT OFF UNDERLINE OFF EXPANSION REGULAR SLOPE REGULAR WEIGHT MEDIUM INVERTED OFF USERINFO NIL STYLE NIL) FORMATINFO (ARABIC)) (270 12 288 36) NIL) (HEADING NIL (HEADINGTYPE FOOTINGR) (54 27 558 36) NIL) (HEADING NIL (HEADINGTYPE RECTOHEAD) (54 762 558 36) NIL) (TEXT NIL NIL (54 54 504 684) NIL)))))(<00><00>ø(ZZø(ääÚ(ÌÌø/ÌÌøøT(ÌÌø(ÌÌø )ø2T)øT(ÌÌøf)ÌÌøTBøø PAGEHEADING VERSOHEADBøø PAGEHEADING RECTOHEADAøø PAGEHEADINGFOOTINGVAøø PAGEHEADINGFOOTINGRMODERN
MODERNMODERNMODERN
?1(DEFAULTFONT 1 (GACHA 10) (GACHA 8) (TERMINAL 8))
 HRULE.GETFNMODERN
 HRULE.GETFNMODERN


 HRULE.GETFNMODERN
   HRULE.GETFNMODERN
  HRULE.GETFNMODERN
Æ HRULE.GETFNMODERN +  HRULE.GETFNMODERNdc HRULE.GETFNMODERN   HRULE.GETFNMODERN®'  BMOBJ.GETFN3?1(DEFAULTFONT 1 (GACHA 10) (GACHA 8) (TERMINAL 8))
ÈÆ HRULE.GETFNMODERN   HRULE.GETFNMODERN!h BMOBJ.GETFN3?1(DEFAULTFONT 1 (GACHA 10) (GACHA 8) (TERMINAL 8))
tçÊÛ HRULE.GETFNMODERN 1  HRULE.GETFNMODERNæbzº