I understand you would like to make phpinfo() output confirm XHTML.... My suggestion is leave small problems and let browser detect/use appropriate font/charset. This will work mostly since users are using browser optimized for their language. If browser detect wrong, user still be able to manually set correct charset.
Hard coding charset causes problems and the behavior is different from browser to browser... Char to entity conversion function only supports few encoding... Detecting charset is a bit unreasonable, but using internal encoding/charset ini directive is more reasonable. However, it means phpinfo() depends on mbstring (or make internal encoding directive to core_globals at least) Please note "charset != internal encoding". These ini directives do not have to be the same. I'm not sure if we should try, but we can try to make phpinfo() perfectly confirm XHTML once multibyte char support is fully integrated to PHP/Zend. -- Yasuo Ohgaki Colin Viebrock wrote: > Would this problem be solved if the META tag that defines the character > set is hard-coded to use US-ASCII or ISO-8859-1, instead of going > through the process it does now to try and determine a charset? > > - Colin > > Yasuo Ohgaki wrote: > >>First problem, CSS should not contain specific font >>name. Otherwise, characters may be broken under some >>browsers when font does not have type faces needed. >> >>Second problem, phpinfo() output should not automatically >>converted to html entity unless correct charset is used >>when chars are converted to entity. Otherwise, characters >>may be broken. Please do not try to use UTF-8 always to fix >>since UTF-8 does not support everything. >> >>Due to these two problems, phpinfo() output is much less >>useful for me than used to be. >> >>I hope someone responsible will fix it. >> >>-- >>Yasuo Ohgaki >> > > > > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
