you don't have to have your files in utf-8 for it to work, just the
browser header.
although any utf-8 characters in your files will look funky. it just
depends where the content comes from... you could always use ®
for the (r) registered symbol for example.
i'd be more apt to figuring out how to
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 ch
On Jan 8, 2008 1:31 PM, tedd <[EMAIL PROTECTED]> wrote:
> Last night I read a chapter in the book "Core Web Application
> Development with PHP and MYSQL" by Wandschneider who said basically
> that -- a good read, btw.
I'm guess it was his name which comprised the first chapter.
--
Daniel P.
At 11:57 AM +0200 1/8/08, Arvids Godjuks wrote:
To author:
You'r going the wrong way.
Make your page utf-8, all text on it. Set utf-8 encoding and treat all
incoming data as UTF-8. If some agent (definetly not some browser - they all
know UTF-8) doesn't understand that (that could be some "hacke
Olav Mørkrid wrote:
> i specify iso-8859-1 in both header and body:
>
> 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 s
To author:
You'r going the wrong way.
Make your page utf-8, all text on it. Set utf-8 encoding and treat all
incoming data as UTF-8. If some agent (definetly not some browser - they all
know UTF-8) doesn't understand that (that could be some "hacker" writing
it's own bot) - that's his problem. The
Olav Mørkrid wrote:
i specify iso-8859-1 in both header and body:
if two different people post the norwegian phrase "Godt nytt år"
(happy new year), it may appear in the following variations:
[CONTENT_TYPE] => application/x-www-form-urlencoded;charset=iso-8859-1
$_POST["input"] = "Godt nytt
I have to ask... WHY are you forcing ISO-8859-1? If anything, you should be
forcing UTF-8. Then you can send, receive, and store data in UTF-8 ad cover
most human languages without having to change character set.
On Monday 07 January 2008, Olav Mørkrid wrote:
> i specify iso-8859-1 in both h
maybe look at iconv functions
but the content-type is the only thing i set, and it works 100%
fine. all javascripts, forms, etc. inherit it from the looks of it
properly.
On 1/7/08, Olav Mørkrid <[EMAIL PROTECTED]> wrote:
> i specify iso-8859-1 in both header and body:
>
>
>
>
> if two differe
i specify iso-8859-1 in both header and body:
if two different people post the norwegian phrase "Godt nytt år"
(happy new year), it may appear in the following variations:
[CONTENT_TYPE] => application/x-www-form-urlencoded;charset=iso-8859-1
$_POST["input"] = "Godt nytt år"
[CONTENT_TYPE] =>
>
>
> My experience is that this does not affect only the displayed
> characters, but the way the form fields are transported.
>
> But perhaps I am wrong,
> Iv
This works for me as well.
Put in utf-8 and you should be good to go.
You don't -technically- need to even change your database fields
Olav Mørkrid wrote:
hello
does php have any built-in functions to convert post data from
whatever format it arrives in to whatever format i wish?
example:
i use iso-8859-1 internally, and even specify
accept-charset=iso-8859-1 in my html, but some browsers (phones) send
utf-8 anyway.
do i hav
hello
does php have any built-in functions to convert post data from
whatever format it arrives in to whatever format i wish?
example:
i use iso-8859-1 internally, and even specify
accept-charset=iso-8859-1 in my html, but some browsers (phones) send
utf-8 anyway.
do i have to manually check if
13 matches
Mail list logo
