home *** CD-ROM | disk | FTP | other *** search
- .\ \Q
- .marg 2 80
- .nofj
- .\ \Q
- .fig 20
- .col
- |The JGPrint Set of Top Bit Bytes;
-
- &00 0=\!^@; 1=\!; 2=\!; 3=\!; 4=\!; 5=\!; 6=\!; 7=\!^G;
- &08 8=\!^H; 9=\!^I; 10=\!^J; 11=\!^K; 12=\!^L; 13=\!^M; 14=\!; 15=\!;
- &10 16=\!; 17=\!; 18=\!; 19=\!; 20=\!; 21=\!; 22=\!; 23=\!;
- &18 24=\!; 25=\!; 26=\!; 27=\! 28=\!; 29=\!; 30=\!; 31=\!
-
-
- &7F 127=\!;
- &80 128=€; 129=Ŵ; 130=ŵ; 131=◰; 132=☓; 133=Ŷ; 134=ŷ; 135=;
- &88 136=⇦; 137=⇨; 138=⇩; 139=⇧; 140=…; 141=™; 142=‰; 143=•;
- &90 144=‘; 145=’; 146=‹; 147=›; 148=“; 149=”; 150=„; 151=–;
- &98 152=—; 153=−; 154=Œ; 155=œ; 156=†; 157=‡; 158=fi; 159=fl;
- &A0 160= ; 161=¡; 162=¢; 163=£; 164=¤; 165=¥; 166=¦; 167=§;
- &A8 168=¨; 169=©; 170=ª; 171=«; 172=¬; 173=; 174=®; 175=¯;
- &B0 176=°; 177=±; 178=²; 179=³; 180=´; 181=µ; 182=¶; 183=·;
- &B8 184=¸; 185=¹; 186=º; 187=»; 188=¼; 189=½; 190=¾; 191=¿;
- &C0 192=À; 193=Á; 194=Â; 195=Ã; 196=Ä; 197=Å; 198=Æ; 199=Ç;
- &C8 200=È; 201=É; 202=Ê; 203=Ë; 204=Ì; 205=Í; 206=Î; 207=Ï;
- &D0 208=Ð; 209=Ñ; 210=Ò; 211=Ó; 212=Ô; 213=Õ; 214=Ö; 215=×;
- &D8 216=Ø; 217=Ù; 218=Ú; 219=Û; 220=Ü; 221=Ý; 222=Þ; 223=ß;
- &E0 224=à; 225=á; 226=â; 227=ã; 228=ä; 229=å; 230=æ; 231=ç;
- &E8 232=è; 233=é; 234=ê; 235=ë; 236=ì; 237=í; 238=î; 239=ï;
- &F0 240=ð; 241=ñ; 242=ò; 243=ó; 244=ô; 245=ÿ; 246=ö; 247=÷;
- &F8 248=ø; 249=ù; 250=ú; 251=û; 252=ü; 253=ý; 254=þ; 255=ÿ
-
- .stop Explanation of table
-
- .marg 10 70
- .jgfj
- .\ \P
- This table should be JGPrinted on your printer to see the effect of the vdu and
- top\-bit set bytes.
-
- There are two problems involved in this example: the effect of control\/vdu bytes
- on the printer; the effect of control\/vdu bytes on the editor.
-
- The first problem is dealt with by the backslash directive \\! which causes the
- Tochars command to be sent to the printer with a parameter of 1. The tochars
- code should be set in the configuration to cause the printer to take the next
- <n> bytes as printable characters, where <n> is a parameter, in this case 1.
-
- The second problem is the need to put in what would otherwise be treated as
- control characters by the editor. The solution is to use JGPrint's hatty
- dirictives, configuring the hatty values appropriately, viz ^^@ -> 0, ^^G -> 7
- .... ^^M -> 13. This seems sufficient for both JGEd and Edit.
-
- The mapping McPound => PrPound, defined in the configuration will make the
- table fail byte 163. The "See character set" prompt at the end of the
- JGPrint dialogue will get a similar printout without this mapping or '#' to Hash
-
- It may possibly be neccessary, with another editor, to extend this list.
- JGPrint, itself, has difficulties reading byte 0.
-
- You may have different configurations with different character sets, or
- you may have adapted JGPrint directives, eg \\x, \\y, \\z, which use the
- commands ChRam and ChRom, to do so within your text. You may therefore want
- several JGPrinted versions of the top\-bit set characters. Remember, you may
- need different 'font' files if you have done so.
-
- It would seem sensible to print out the top\-bit set bytes via !Printers so that
- you had a written record of how they appear on screen while you are inputting
- them. It appears that JGEd's preferred line seperators <cr><lf> produce a blank
- line between each line throughout. Therefore, you should execute 'ln;ft/text/'
- on the macroline, both to produce <ln> as the line seprator and to give
- !printers a filetype it is familiar with.
-
-