>> a) Fonts. Some people didn't like Arial, so I reverted to letter the >> browser decide. Some people didn't like that, and they'd like the font >> specifications back in. > > This will simply break output under some browser. > It's more important to show info, but show a little nicely on some > systems while printing garages on some systems.
But the "old" phpinfo() specified fonts, so are you saying it was broken then too? > If anyone prefer any specific font, they should use their own CSS. But I bet 99% of the people will have versions of either Arial or Verdana or Helvetica that *will* work. Why not make life easier for the majority, since the 1% is going to have to specify their own font anyway? >> I don't know what the solution to this is. My instinct is to ask "why >> don't we just hardcode the pages to use US-ASCII, or ISO-8859-1?" Would >> this not solve the charset issues? > > No. > > Why you bother? > > Letting browser decide is more feasible and most importantly, > it works. Okay ... so don't output the charset meta tag at all? > If you are not certain how to make phpinfo() work under most > environment, I can help. If you can make it work under most environment *and* look good (i.e. as much like it used to, sans-serif fonts and all), then great! CVS is a wonderful thing. :) - Colin -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
