- From: Gavin Thomas Nicol <gtn@rbii.com>
- Date: Thu, 11 Sep 2003 16:44:21 -0700
- To: www-tag@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Anyone have any other possible solutions? :-)
Good to see that this is *finally* getting some attention, as it's been a
well-known problem for 10 years or so! [1]
One more possible solution is to include an extra field in the submitted GET
data that indicates the character encoding of the submitted data.... kind of
a "hidden field" as it were.
It might look like:
GET
/foo.html?Content-type=application/x-www-form-urlencoded;charset=ancd;field1=abcd;field2=...
HTTP/1.1
assuming the field is called "Content-type".
1.http://www.mind-to-mind.com/library/papers/multilingual/multilingual-www.html#ID-2BCA821C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/YQjWCr0YCppBUuQRAiVMAJ9Nkt7N2aCcPWwPznZlLmWgso2X4QCfZFO7
bucKZABDkYDwzDz9UCa//cI=
=Vv5k
-----END PGP SIGNATURE-----
Received on Thursday, 11 September 2003 19:48:46 UTC