Re: [PHP] Re: A Bug in string ' e

2005-06-26 Thread Jasper Bryant-Greene
Kevin L'Huillier wrote: > On 26/06/05, Jasper Bryant-Greene <[EMAIL PROTECTED]> wrote: > >>Kevin L'Huillier wrote: >> >>>Could you copy the relevant code into a message? >> >>Sure, either set the content-type to text/plain (to see the raw string >>rather than have the browser interpret it as HTML

Re: [PHP] Re: A Bug in string ' e

2005-06-26 Thread Kevin L'Huillier
On 26/06/05, Jasper Bryant-Greene <[EMAIL PROTECTED]> wrote: > Kevin L'Huillier wrote: > > Could you copy the relevant code into a message? > > Sure, either set the content-type to text/plain (to see the raw string > rather than have the browser interpret it as HTML), like this: Sorry, Jasper.

Re: [PHP] Re: A Bug in string ' e

2005-06-26 Thread Jasper Bryant-Greene
Kevin L'Huillier wrote: > Could you copy the relevant code into a message? Seeing > pseudo-script is different from seeing what you are actually > doing. Sure, either set the content-type to text/plain (to see the raw string rather than have the browser interpret it as HTML), like this: or ht

Re: [PHP] Re: A Bug in string ' e

2005-06-26 Thread Kevin L'Huillier
> Are you viewing this via a web server? It's probably returning > content-type text/html, which means that you might need to > htmlspecialchars() that string. That's what i was thinking. It looks like how some browsers would render that string. Could you copy the relevant code into a message?

[PHP] Re: A Bug in string ' e

2005-06-26 Thread Jasper Bryant-Greene
cchereTieShou wrote: > You can actually try to use this to verify the problem: > > echo ' e > What you get? I got > Quite confusing. Anyone think this is a bug or something I missed? Are you viewing this via a web server? It's probably returning content-type text/html, which means that you migh