how Windows browsers encode URL [Re: why the % cruft?]
Germain Garand
germain at ebooksfrance.com
Wed Jul 10 17:35:48 BST 2002
Le Mercredi 10 Juillet 2002 15:40, Hetz Ben Hamo a écrit :
> Waldo, could you add a simple check-box to enable UTF-8 sending instead of
> ISO8859-1 please?
>
That won't solve the Google problem, because still, if you have no
"preference" cookie, it will parse your Accept-Language and User-Agent
string and send you a form with
<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=YOUR_LOCALE">
<INPUT TYPE=hidden name=ie value="YOUR_LOCALE">
Browsers shouldn't enforce UTF-8 encoding in FORMS, or when clicking a link :
they should use whatever the HTTP-EQUIV meta tell them to.
Now, UTF-8 can be used when entering new URLs, indeed, but that won't solve
much problems...
The only solution here is to bug Google for having the Accept-Charset parsed
correctly.
Also, if the Encoding as been forced in konqui by the user (as opposed to
Auto), the Accept-Charset should reflect that, which is not the case
currently.
G.
More information about the kfm-devel
mailing list