[Top][All Lists]

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

Re: lynx-dev Re: msg00798.html (was: 0x2276 handling)

From: Nelson Henry Eric
Subject: Re: lynx-dev Re: msg00798.html (was: 0x2276 handling)
Date: Wed, 6 May 1998 10:53:42 +0900 (JST)

> However, I tracked down a URL for the FAQ (would have been nice if he had
> included it the the message):

Sure would have.


Thanks, Fote, I wanted to but didn't have the time to look for it.

> do, and is wrong.  The server is returning "Content-Type: text/plain"
> without a charset parameter, so the assumed charset should apply, and

This mixed-bag page seems a "natural" for Asada's wizardry, and indeed
is pretty much rendered correctly by using Lynx in CJK mode on either
SunOS or Windows95.

> characters, as the v2.7.2 code did?).  Also, when I set the assumed
> charset to euc-jp or shift_jis (it's not clear which the FAQ is using),
> I get different, but still 8-bit characters.

Cut-n-paste of my options menu from Lynx 2.8rel.3 (SunOS4.1.3):
     preferred document lan(G)uage: ja,en
     preferred document c(H)arset : ISO-2022-JP
     ^A)ssume charset if unknown  : euc-jp
     display (C)haracter set      : Japanese (EUC)
     Raw 8-bit or CJK m(O)de      : ON

On MS Windows, you'd probably want the display (C)haracter set set
at Japanese (SJIS).

The truth is, however, I am not having a lot of luck using Win32 Lynx
2.7.1ac-0.81, if there is a meta tag describing the character set, e.g.,
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=x-euc-jp">.
Without a meta tag, a document is rendered okay.  Guess it means I need
to upgrade to 2.8.


reply via email to

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