[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev lynx and other character sets
From: |
Leonid Pauzner |
Subject: |
Re: lynx-dev lynx and other character sets |
Date: |
Wed, 30 Jun 1999 02:38:02 +0400 (MSD) |
26-Jun-99 20:20 Klaus Weide wrote:
> ----
> When display character set is NOT 'UNICODE (UTF-8)' (and not CJK or
> transparent either), I notice something strange for all the scripts
> Lynx doesn't understand (Armenian, Devanagari, Bengali, ...):
> Those characters are not shown in any way, there is no indication
> that something was missing. Some earlier version would show
> something like
> Armenian
> U531 U532 U533 U534 U535 U536 U537 U538 U539 ...
> instead. Leonid, was this a concious decision? Seems like a bug
> to me.
I thought such indication was too technical for average lynx user
and not very useful in fact (say, I run into japanese text
with any european display charset). Instead, this can be indicated
from Info Page: [7bit chars only] / [7bit approximation was used]
/ [few not recognized characters filtered out] or so.
>From the other hand, this hide a bug:
when we switch "\" for source mode we got a different output
for few notrecognized 8-bit characters when we uncomment the code
you are asking for (have not remember details now).
> ----
> Another observation: in the situation of the provious section,
> force Raw Mode on. This has to be done from the 'O'ptions screen,
> since '@' is now disable for explicit charset. The missing characters
> (or some of them) are now shown in some kind of 'raw' way. This is
> also the case in an earlier lynx version I keep around for reference
> ("2.7.1ac-0.91"), but in a different way. I think I found this
> somewhat useful a long time ago for certain kinds of broken "utf-8"
> documents, that's why it was there, and apparently it has survived.
I have a little experience with "utf-8" pages
but seems documents in normal "8bit charsets" feel good without this mode.
> Leonid, I mention this since (as I seem to remember) you asked some
> months ago if there was a case where 'Raw Mode' makes a difference
> for explicitly charsetted documents. This is one. (Maybe the only
> one, or the only surviving one.)
I grep the code for LYRawMode and found only a couple of matches
for unrelated things in GridText.c
> If you want to pursue this further, I can try to dig up the page(s)
> where I found this useful.
Please give examples.
You mean to overload "Raw Mode" key for `visualizing' (few)
unrecoverable characters while the usual meaning of that key is another...
> Klaus