On Fri, January 26, 2007 7:24 am, Jochem Maas wrote:
> Dave Goodchild wrote:
> that said you should probably opt to output everything as UTF-8 - all
> decent
> browsers will return data in the same encoding as the page was given
> to them in
> by default - this requires you to have php send the cor
On Fri, January 26, 2007 3:33 am, Dave Goodchild wrote:
> Hi all, I posted a question a couple of days ago regarding a web app I
> have
> wherein users are able to indicated prices and concessions via a text
> field,
> and the resulting encoding issues I have experienced, the main one
> being
> see
# [EMAIL PROTECTED] / 2007-01-26 21:09:34 +:
> # [EMAIL PROTECTED] / 2007-01-26 09:33:13 +:
> > Hi all, I posted a question a couple of days ago regarding a web app I have
> > wherein users are able to indicated prices and concessions via a text field,
> > and the resulting encoding issues
# [EMAIL PROTECTED] / 2007-01-26 09:33:13 +:
> Hi all, I posted a question a couple of days ago regarding a web app I have
> wherein users are able to indicated prices and concessions via a text field,
> and the resulting encoding issues I have experienced, the main one being
> seeing the pound
# [EMAIL PROTECTED] / 2007-01-26 14:29:52 +0100:
> I don't think you are able to detect your users character encoding
> with php only (at least not rock-solid). Just some days ago, there
> was a discussion about that issue (at least concerning Safari) on the
> Apple web dev mailing list.
>
>
Hi Dave.
I don't think you are able to detect your users character encoding
with php only (at least not rock-solid). Just some days ago, there
was a discussion about that issue (at least concerning Safari) on the
Apple web dev mailing list.
Have a look at:
http://lists.apple.com/archives/
Dave Goodchild wrote:
> Hi all, I posted a question a couple of days ago regarding a web app I have
> wherein users are able to indicated prices and concessions via a text
> field,
> and the resulting encoding issues I have experienced, the main one being
> seeing the pound sign as £ if viewing th
Hi all, I posted a question a couple of days ago regarding a web app I have
wherein users are able to indicated prices and concessions via a text field,
and the resulting encoding issues I have experienced, the main one being
seeing the pound sign as £ if viewing the results in a browser with the
8 matches
Mail list logo
