[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Autoconf patch for S/390 (EBCDIC)
From: |
Leonid Pauzner |
Subject: |
Re: lynx-dev Autoconf patch for S/390 (EBCDIC) |
Date: |
Sun, 1 Nov 1998 00:07:31 +0300 (MSK) |
> * From: address@hidden
> o I use symbolic instead of numeric constants in many places.
> I consider some of this merely good coding practice, such as:
> CH_ESC instead of 27
> ' ' instead of 32 (or 040 or 0x20)
> CH_NBSP instead of 160
> CH_SHY instead of 173
> with the names defined in a header file. I couldn't do this
> uniformly -- at some points expanding numeric entities, the
> numeric use must remain. And 160 is a particular nuisance:
> "ch == 160" is probably a test for CH_NBSP, while "ch >= 160"
> is probably a test for the high range of control characters,
> for which I defined a different symbol, CH_HICTL.
^^^^^^^^
Character sets currently recognized by Lynx has "LYlowest_eightbit" value
which is used for testing of control characters (see chrtrans/*.h files:
e.g. windows-xxxx usually have this value at 129).
And ISO-8859-x have explicitely "UCT_ENC_8859" encoding
which assumes controls at <160.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: lynx-dev Autoconf patch for S/390 (EBCDIC),
Leonid Pauzner <=