In article <[EMAIL PROTECTED]>, John-Mark Bell <[EMAIL PROTECTED]> wrote: > The character set used for form submission is defined as follows:
> If there is an accept-charset attribute on the form, then use the most > appropriate entry in the list. > Otherwise, if there is a document character set, use that. > Otherwise, fall back to ISO-8859-1. Cheers for clarifying that. I'll add an accept-charset=UTF-8 to my form entry on the page that was failing, and see if that fixes the problem. > Other browsers encode unrepresentable characters as if they were HTML > entities (e.g. ‘), then percent encode that (so it comes out as > %26%238216%3B). This approach forces server-side processors to be HTML > entity aware for no good reason, That's probably why it worked ok when I tested it on a variety of Mac browsers. My form processor on the server-side has got fairly good entity processing in it, so decodes the received data ok. Paul
