From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Dave Page" <dpage(at)pgadmin(dot)org>, "Daniel Migowski" <dmigowski(at)ikoffice(dot)de>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #4198: The bugreport form has an encoding problem |
Date: | 2008-06-05 23:50:18 |
Message-ID: | 874p8730hx.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> It does have a problem, because the email sent does not contain a
>> charset header. It does look OK for me too -- as long as I use a UTF8
>> terminal. The fix is easy, just add this line to the message headers:
>
>> Content-Type: text/plain; charset=utf-8
>
> What happens if someone pastes text into the form that is *not* in UTF-8?
http form submissions include a content-type header too. I don't remember if
PHP (or is it mod_python?) automatically converts incoming strings to the
server encoding or if you're expected to do that yourself? Or if it isn't
being done for us we could just put that encoding in the email headers.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-06-06 05:49:38 | Re: BUG #4222: ERROR: cache lookup failed for relation |
Previous Message | Alvaro Herrera | 2008-06-05 23:13:34 | Re: BUG #4198: The bugreport form has an encoding problem |