[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev Non-Japanese text with Japanese D.C.S. (was: Superscripts)

From: Klaus Weide
Subject: lynx-dev Non-Japanese text with Japanese D.C.S. (was: Superscripts)
Date: Wed, 7 Jun 2000 16:44:26 -0500 (CDT)

On Wed, 7 Jun 2000, Henry Nelson wrote:

> >    <>.
> > You'll have to set Assumed document character set to utf-8, since
> > the mailing list archive loses the charset information of mail
> > messages.
> > 
> > Henry, if you are reading, this (and other lynx-dev archive messages)
> > is also a good example where, with a Japanese display character set, you
> > would have to toggle Raw/CJK.  In this case, in addition to setting
>         ^^^^
> [The real reason I don't, however, is that unless I am behind a cacheing
> server, I would have to re-fetch the message, which in most cases is not
> worth the overhead. 

Re-fetching (from the network) does not happen if you have SOURCE_CACHE:
enabled AND the document in question is one subject to source-caching,
i.e. a HTML document retrieved via http or https.  If that is different
from your experience - whether you use '@' or the 'O'ptions Menu for
changing - you should report it as a bug.

> Another "discovery" is that the convenience of having
> the CJK/Raw toggle on the Forms O)ption Menu became apparent to me: if only
> a @-key toggle, you'd have to at least momentarily begin a re-fetch to do
> the toggle before doing the assumed charset change.]
> > assumed charset to utf-8.
> THANK YOU, Klaus, for this tip.  Now I know exactly what you have been
> saying all this time.  -- If I can only keep it in mind when I hit a page
> like this in the future!

The remaining problem is that you don't always know *what* charset to
assume...  sometimes trial and error is necessary.

> Just to be sure I did what is expected, here is a paragraph for
> comparison from files saved with the P)rint Save file to disk function:
[ snipped ]
Yes, as expected.
(Except for the fact that your mail, as I saw it here, didn't have
the raw bytes in the "Raw/CJK" version, but the result of attempting
to interpret them as EUC-JP and converting to ISO-2022-JP...  But I
can discount for that.)

> And I have been looking for ages for an easy way to do this conversion!
> Been staring me in the face all these years.

It ought not to be so cryptic...  SOmeone should wite up an easy to
understand HOWTO text...


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]