[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV minor display problem (?character 0xA2?)
|
From: |
Klaus Weide |
|
Subject: |
Re: LYNX-DEV minor display problem (?character 0xA2?) |
|
Date: |
Fri, 2 May 1997 16:28:29 -0500 (CDT) |
On Fri, 2 May 1997, Bela Lubkin wrote:
> Klaus Weide wrote:
>
> > > not occur when using "wy60". Lynx set up for IBM PC character set, raw
> > ^^^^^^^^^^^^^^^^^^^^
> > > translated to 0x9b on output. The SCO ANSI console takes 0x9b as CSI,
> > ^^^^^^^^^^^^^^^^
> > > Control Sequence Initiator, same as ESC [. This is pretty standard
> > > behavior for ANSI terminals of various sorts.
> >
> > The IBM PC character set (cp437) contains a visible character at that
> > position. Since you are telling Lynx that that is your display character
> > set, when apparently it is not, you shouldn't be surprised about unusual
> > results.
>
> Aye, perhaps you are right.
>
> Yet other reports indicate that the Linux console behaves similarly; a
> significant part of Lynx's audience is affected by this problem.
A significant part of Lynx's audience is affected by the "problem" that,
when Lynx Options are set in a certain way, Lynx will believe the user
and act according to the Options setting.
Now what is the way you suggest so that Lynx can detect, in a universally
applicable way across all terminal, terminal emulators, and windowing
systems, what display character set is in use and what translations may
happen on the way between Lynx's output and what the user sees, so that we
can get rid of the "display character set" field on the Options screen
and avoid the "problem" that some users insist on setting it *wrong*?
> Try the following:
>
> <html>
> this is a test (1) ... ¢2J
> this is a test (2) ... ¢=155g
> </html>
>
> On my system, using IBM PC character set and iso-8859-1 (assumed), the
Why oh why do you insist on using "IBM PC character set" when that is
obviously not the right setting for your circumstances???
> I *can* display the ¢ character by sending "ESC [ = 1 5 5 g", a SCO
> specific sequence which means "display character 155 (decimal) without
> any special interpretation". The second line shows this. The Linux
> console probably also supports that, being modeled after the SCO
> console. Hmmm.
And you are guessing wrong. Hmmm.
> I think all other chars in the 0x80..0x9f range can be displayed
> directly. Also, IBM PC chars in the range 0x01..0x1f can be displayed
> with the "ESC [ = <decimal> g" sequence. This might be useful...
Apparently a vendor specific hack. Linux has other specific hacks to
enable display of some glyphs in that range. And so on.
Klaus
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
Re: LYNX-DEV minor display problem (?character 0xA2?), Dan Strychalski, 1997/05/03