On 9/16/05, Ron Korving <[EMAIL PROTECTED]> wrote:
> Damn.. I feel stupid now... Sorry guys.
> Is it normal for DOM to output everything in UTF8 without an ability to
> influence this?
For the record, DOM does not output anything using UTF-8, it does
convert the input to UTF-8. It's a slighty diff
On Fri, 16 Sep 2005, Ron Korving wrote:
> Damn.. I feel stupid now... Sorry guys.
> Is it normal for DOM to output everything in UTF8 without an ability to
> influence this?
Yes.
> I figured that it wouldn't be a UTF8 problem because it
> outputs 2 bytes, and I thought UTF8 was just 1 byte (henc
On 16.9.2005 10:06 Uhr, Ron Korving wrote:
> Hi,
>
> I found a bug in DOM. It surprises me that it's never been seen and/or fixed
> before. I can't find anything about in the PHP bugtracker anyway. The reason
> why I'm posting here and not writing a bugreport, is because I'm not sure if
> this i
""messju mohr"" <[EMAIL PROTECTED]> schreef in bericht
news:[EMAIL PROTECTED]
A thank you to you as well.
In general:
By the way, wouldn't it be time for trim() to start trimming off ascii
characters 160 too since that's what represents? It's no biggy, but
maybe something to consider.
Ron
--
Damn.. I feel stupid now... Sorry guys.
Is it normal for DOM to output everything in UTF8 without an ability to
influence this? I figured that it wouldn't be a UTF8 problem because it
outputs 2 bytes, and I thought UTF8 was just 1 byte (hence the name UTF8).
Guess I was wrong.
Sorry again, I reall
On Fri, Sep 16, 2005 at 10:06:40AM +0200, Ron Korving wrote:
> Hi,
>
> I found a bug in DOM. It surprises me that it's never been seen and/or fixed
> before. I can't find anything about in the PHP bugtracker anyway. The reason
> why I'm posting here and not writing a bugreport, is because I'm not
