Re: Russian charsets

From: Onime Clement (
Date: Sun, Nov 04 2001

  • Next message: Onime Clement: "Re: Bug in software"

    Date: Sun, 4 Nov 2001 13:23:42 +0100 (MET)
    From: Onime Clement <>
    Message-ID: <>
    Subject: Re: Russian charsets
    Hi Lena,
    After looking at this, it appears that lynx seem to prefer
    using the charset defined by the META headers as opposed to what is
    specified on the command line!
    The solution appears to be to strip the META header definition of charset
    Windows-1521 for get and send requests, this should force the use of the
    charset as defined by the user.
    Status: Fixed
    On Sun, 4 Nov 2001 wrote:
    > Hi Clement,
    > <> while executing GET command
    > still continues to transliterate Russian text by Latin characters
    > rendering text very inconvenient for reading. Specifying
    > XCHARSET doesn't help.
    > Two examples:
    > 1.
    > XDOCINFO gives just "Content-Type: text/html", without charset
    > specification. The page contains
    > <meta http-equiv="Content-Type" content="text/html; charset=windows-1251">
    > SOURCE command gives the page in windows-1251 charset.
    > 2.
    > XDOCINFO gives "Content-Type: text/html; charset=koi8-r".
    > SOURCE command gives the page in koi8-r charset.
    > For both these pages GET command gives the page transliterated
    > by Latin characters no matter how I specify XCHARSET:
    > xcharset koi8-r
    > xcharset windows-1251
    > xcharset auto
    > or without XCHARSET command at all, with
    > "Content-Type: text/plain; charset=us-ascii" in header
    > or the letter with GET command.
    > I last tried on October 30-31 (version pre3.0rc14c).
    > To read Russian text written by Latin characters is very
    > inconvenient and slow. Can Lynx be forbidden to convert
    > one charset into another?
    > Thanks,
    > Lena