Re: BUG #4198: The bugreport form has an encoding problem

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: BUG #4198: The bugreport form has an encoding problem
Дата
Msg-id 874p8730hx.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: BUG #4198: The bugreport form has an encoding problem  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Alvaro Herrera <alvherre@commandprompt.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #4198: The bugreport form has an encoding problem
Следующее
От: "Heikki Linnakangas"
Дата:
Сообщение: Re: BUG #4222: ERROR: cache lookup failed for relation