Re: [PHP] PLEASE help, this is driving me crazy - is saveHTML() etc not UTF-8 capable?

2009-02-18 Thread Addmissins Development
mike wrote: > On Tue, Feb 17, 2009 at 4:26 PM, mike wrote: >> i tried that kind of stuff - it did not seem to work. >> >> i will try again... if anyone has any ideas i.e. "use iconv to convert >> to A, then use DOM stuff, then use iconv to move it back to UTF8..." >> etc. i am all ears. > > Nope

Re: [PHP] PLEASE help, this is driving me crazy - is saveHTML() etc not UTF-8 capable?

2009-02-17 Thread mike
On Tue, Feb 17, 2009 at 4:26 PM, mike wrote: > i tried that kind of stuff - it did not seem to work. > > i will try again... if anyone has any ideas i.e. "use iconv to convert > to A, then use DOM stuff, then use iconv to move it back to UTF8..." > etc. i am all ears. Nope - for example this is t

Re: [PHP] PLEASE help, this is driving me crazy - is saveHTML() etc not UTF-8 capable?

2009-02-17 Thread mike
i tried that kind of stuff - it did not seem to work. i will try again... if anyone has any ideas i.e. "use iconv to convert to A, then use DOM stuff, then use iconv to move it back to UTF8..." etc. i am all ears. On Tue, Feb 17, 2009 at 12:46 PM, Nathan Nobbe wrote: > On Tue, Feb 17, 2009 at 1

Re: [PHP] PLEASE help, this is driving me crazy - is saveHTML() etc not UTF-8 capable?

2009-02-17 Thread Nathan Nobbe
On Tue, Feb 17, 2009 at 12:40 PM, mike wrote: > Pardon the messy code, but I got this working like a charm. Then I > went to try it on some Russian content and it broke. The inbound was > utf-8 encoded Russian characters, output was something else > unintelligible. > > I found a PHP bug from year

[PHP] PLEASE help, this is driving me crazy - is saveHTML() etc not UTF-8 capable?

2009-02-17 Thread mike
Pardon the messy code, but I got this working like a charm. Then I went to try it on some Russian content and it broke. The inbound was utf-8 encoded Russian characters, output was something else unintelligible. I found a PHP bug from years ago that sounded related but the user had a workaround.