Re: LYNX-DEV charsets

[Foteos Macrides]

Drazen Kacar <address@hidden> wrote:
>I thought that Klaus' Unicode support will make it into 2.7, but if it
>won't, I think that present charset handling needs a little patching.
>Lynx 2-6FM (last mod. 01/29/97) is the first browser that announces
>transparent negotiation capability via
>
>   Negotiate: trans
>
>header, but it doesn't always send meaningful q values. When the user
>selects charset(s) to send in Accept-Charset header, Lynx will append
>", iso-8859-1;q=0.001, us-ascii;q=0.001", which is the lowest possible
>quality value for these code pages.
>
>If the server takes that into calculation, ISO 8859-1 or US-ASCII pages
>don't have a chance. It's a bug and needs to be corrected. I've written
>quick and dirty hack, untested, of course, use at your own risk. Variable
                                            ^^^^^^^^^^^^^^^^^^^^
                                            ||||||||||||||||||||

        Well put!
        
        Study the Lynx code until you understand what it actually is
doing, and study the IETF drafts and the discussions about them in the
relevant IETF WGs

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;