Sam Varshavchik writes:
If you want to get anal: this is your browser's bug.
I18n is completely broken in HTML forms, because the browser has no means to specify what charset/encoding it is using for sending stuff. It just says
Content-type: application/x-www-form-urlencoded (note: that header actually specifies the encoding!)
sqwebmail sends an html form, with the character set set to iso-8859-1.
Yes, in my case (after experimental content of CHARSET) in the HTTP headers it says Content-type: text/html; charset="utf-8" But on the top of my screen I see Content-Type: text/plain; format=xdraft; charset="iso-8859-1" and, using MSIE 6, I had to manually specify "utf-8" (if I say "automatically" it just chooses windows encoding...) (test: euro: €, pound: £, agrave: à, eacute: é)
I can turn this around and tell you that your browser should not allow an illegal iso-8859-1 character to be entered into an iso-8859-1 HTML form.
Of course, the browser will never convert the stuff being copied and pasted on the textarea. Perhaps it would mentsion what charset it belongs, had it a chance to do so. Browsers tend to be more buggy when they send data using the multipart/form-data format. However, that format allows MIME headers for each form field. IMHO, sqwebmail is buggy because it binds the CHARSET with the language. My language preference has nothing to do with the encoding my system uses (nor with the language of this message which is not the one I spoke in the cradle) I'm still using 0.39.3, not 20021212, so I don't know which items from the following wish list are there, if any: - each user can specify his/her default CHARSET - that charset is used to display folders, with possible conversions - option for using multipart/form-data in user's preferences - for each message/attachment , specify CHARSET _and_ language: "Check spelling" may or may not be available for the current message. Specifying CHARSET for a single message is needed in case, e.g., one replies to a russian mailing list. In that case it would not be possible to use a different charset for composing the message. Perhaps it is more feasible to compose the message in utf-8 and convert it to the target charset before sending? In that case, sqwebmail would have a chance to check that some content is illegal for the target charset and ask the user what to do... Ciao Ale ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
