| 1 |
|
| 2 |
Summary |
| 3 |
======= |
| 4 |
This document is primarily for people who will be using Lynx |
| 5 |
on a remote UNIX or VMS system via an MS-DOS based terminal program. |
| 6 |
|
| 7 |
|
| 8 |
General Information |
| 9 |
=================== |
| 10 |
Lynx comes with built-in translation tables to map the 8-bit character codes or |
| 11 |
character entities coming in from an HTML document to their equivalent codes, |
| 12 |
where possible, for various character sets. |
| 13 |
|
| 14 |
IMPORTANT: you should choose display character set in Lynx Options Menu |
| 15 |
according to your font installed locally. Probably it would be cpXXX. Please |
| 16 |
contact lynx-dev mailing list if you want any new codepage not listed there. |
| 17 |
|
| 18 |
Note that all points of the connection between the display at your end and Lynx |
| 19 |
at the remote end must be 8-bit clean. If the high bit is being stripped at |
| 20 |
any point in between, the only character set you can use (effectively) in Lynx |
| 21 |
will be "7 bit approximations". More on that later. |
| 22 |
|
| 23 |
|
| 24 |
MS-DOS character set weirdness |
| 25 |
============================== |
| 26 |
MS-DOS uses a bass-ackwards character set in which half the normal characters |
| 27 |
have been replaced by pseudo-graphic line and box-drawing characters, and in |
| 28 |
which almost all of the international characters are mapped to nonstandard |
| 29 |
numbers. It also contains Greek letters. |
| 30 |
|
| 31 |
Further confusing matters, there is more than one MS-DOS character set. The |
| 32 |
character sets are referred to as "codepages," each of which has a unique |
| 33 |
number. IBM PCs and compatibles come with one hardware-based default codepage |
| 34 |
and a keyboard to match. In the US market the hardware codepage is 437. PCs |
| 35 |
destined for other regions of the world often have a different default codepage |
| 36 |
which contains characters for other languages and keyboards. Under MS-DOS, one |
| 37 |
can load different codepages into memory and use one of them instead of the |
| 38 |
hardware default. |
| 39 |
|
| 40 |
If you are using Lynx through an MS-DOS based terminal program or telnet |
| 41 |
client, you should use an appropriate DOS codepage in Lynx and you need not any |
| 42 |
translation within terminal program (this is different from old-style behavior |
| 43 |
and works better because of superior Lynx translation support). |
| 44 |
|
| 45 |
Check your display by accessing Martin Ramsch's ISO-8859-1 table |
| 46 |
(iso8859-1.html in the Lynx distribution's test subdirectory). |
| 47 |
|
| 48 |
Ramsch's table describes each entity and shows examples of each. It should be |
| 49 |
immediately obvious that you are either seeing what you are supposed to, or |
| 50 |
you're not. If you see box and line-drawing characters and mismatched letters |
| 51 |
and so on, you are likely displaying 7 bit data, not 8. Ensure that all points |
| 52 |
of your connection are 8-bit clean: |
| 53 |
|
| 54 |
On any remote UNIX systems you must pass through, do |
| 55 |
'stty cs8 -istrip' or 'stty pass8'. 'stty -a' should list |
| 56 |
your settings. |
| 57 |
On any remote VMS systems, do 'set terminal /eightbit'. |
| 58 |
Make sure your terminal program or telnet client is not filtering |
| 59 |
8-bit data. You may found the choice between "VT-100 strict" |
| 60 |
and "VT-100 relaxed" emulation mode - use relaxed. |
| 61 |
Note: Procomm for DOS has a confusing "Use 7 bit or 8 bit |
| 62 |
ANSI" setting -- this has to do with ANSI sequences. If set to |
| 63 |
8 bit, some 8-bit character sequences, including those passed |
| 64 |
by Lynx as well as those which are for your terminal type |
| 65 |
(vt100, etc.) will be processed by Procomm as ANSI screen |
| 66 |
control codes and will most likely result in a garbled display. |
| 67 |
Set it to 7 bit. |
| 68 |
If going through a dialup terminal server, you may have to set the |
| 69 |
terminal server itself to pass 8 bit data. How to do this |
| 70 |
varies with the make of the server, and in some cases only a |
| 71 |
system admin in charge of the box will have the authorization |
| 72 |
to do that. |
| 73 |
SLIP or PPP connections should already be 8-bit clean. |
| 74 |
|