[sclug] Character encoding

[David Given]

Sean Furey wrote:
[...]
> To me the correct thing to do would be put the charset in the HTTP
> headers, not a META tag, but that's not always possible, so I'd be
> interested if you found any solutions using the META tags...

Incidentally, as a related question:

When I have a web page containing a form, and the user types in some text and
the form gets submitted, what encoding is the text in?

The answer, as far as I can work out, is 'whatever the user's web browser was
set to'. And it *doesn't* tell you what that is. Which means, given that the
user can change the encoding any any point, it's impossible to tell what
character set the submitted text is in.

Am I wrong, or is this a horrific hole in the HTTP spec?

-- 
???David Given???McQ?? "There are two major products that come out of
???dg at cowlark.com????? Berkeley: LSD and Unix. We don't believe this to be
??(dg at tao-group.com)?? a coincidence." --- Jeremy S. Anderson
???www.cowlark.com????

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.tmdg.co.uk/pipermail/sclug/attachments/20061207/db7cb63e/signature.bin