Re: Re: cvs: php4 /ext/standard info.c

> And I wonder why do you think it is so important to show the characters > like é or ä in every browser... ? For me, to show correct > multibyte characters in the gpc section would make more sense. > Therefore I think the best solution is to keep the best visibility in the > user's native charset / encoding. phpinfo() no longer encodes accented characters to é or ä. I changed this on Wed Oct 9 10:39:39 2002 in version 1.215 of info.c. > As I said before, IE and Mozilla automatically changes the font > preference if no suitable glyph for a character is found on rendering. > So with some charsets, specifying the face name in CSS declaration has > no effect. And? Isn't that what phpinfo() does now? No charset/encoding is specified, so IE/Moz automagically changes it. > Please look at the attached HTML file and the image (the file would be > dropped in the list). The HTML file is encoded in UTF-8 and the image is > rendered by IE5.5 . Note that the font used to render the Japanese > characters are not "Arial Unicode MS" but "MS PGothic". Hope it helps. Well, it renders nicely under Mozilla for me too. I don't understand the point though, so here are my questions: 1) what is wrong with the way phpinfo() works *right now*? 2) what could/should be changed to fix it? If I call a page with phpinfo(), and pass it a query string with encoded chars, then I do see the _GET["var"] part of the info in the Japanese characters, and all the rest of the page looks fine. i.e.: http://devel.easydns.com/~cmv/.info.php?var=%E6%97%A5%E6%9C%AC%E8%AA%9E This is under Moz 1.2 on my machine. - Colin