Samuel Thibault <[EMAIL PROTECTED]> writes: > As I said, I submitted it in the bugzilla.
Yes, thank you. I just meant it was good to do both. >> - encoding form data in HTTP POST requests. > > I'm not sure what you mean by this. I mean, if there is a document encoded in BIG5 and it contains <form action="foo.cgi" method="POST" enctype="multipart/form-data" accept-charset="BIG5">, and the user then presses the Submit button, must ELinks use iconv to translate the value of each form field to BIG5 from whatever charset ELinks uses internally? Or can it just note that BIG5 is not a built-in charset and choose something else?
pgpdcoqQDlzLD.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
