the user agents in question are various mobile phones, which as you
might guess are premature technology and have their own ways with
things.

here is an example posting from a Samsung D600 which insists on
posting form data in UTF-8 even though i serve it ISO-8859-1 and it
claims to support all character sets.

[_POST] => Array
(
[message] => Norwegian characters: øá
)

[_SERVER] => Array
(
[HTTP_ACCEPT_CHARSET] => *
[CONTENT_TYPE] => application/x-www-form-urlencoded; charset=utf-8
[HTTP_USER_AGENT] => SAMSUNG-SGH-D600E/1.0
Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Browser/6.2.3.3.c.1.101
(GUI) MMP/2.0
)

i would consider switching to utf-8 if i knew how make the windows
version of emacs work fine with utf-8 text files (and still work with
iso-8859-1 files as well).

On 08/01/2008, Per Jessen <per@computer.org> wrote:
> Olav Mørkrid wrote:
>
> > i specify iso-8859-1 in both header and body:
> >
> > <meta http-equiv="Content-type" content="text/html;
> > charset=iso-8859-1"/> <form action="/" method="post"
> > accept-charset="iso-8859-1">
>
> Have you checked 1) what the webserver sends in the header and 2) what
> the browser actually uses? I'm pretty certain I've had issues where
> the meta tags were fine, but the server overrode me settings in the
> header.
>
>
> /Per Jessen, Zürich
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>