From: Christian R. R. <ki...@as...> - 2001-06-08 19:18:13
|
On Fri, 8 Jun 2001, Jeff Dairiki wrote: > PhpWiki specifies the charset in a <meta http-equiv> tag > in the HTML headers on each and every page: > > <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> > > As you note, the charset currently is not specified in the HTTP headers. > If that is causing problems with some browsers (is it?), that's easy enough > to fix (we should probably fix that anyway). It doesn't break any browser that _looks for_ Content-Type _and_ supports Latin-1, which probably makes this a non-issue. There could be browsers that ignore the META tags and thus need the HTTP headers, but since META is defined in everything since HTML2.0 I deem these browsers as broken. Your point is taken. > I suppose entitizing upon output as you suggest doesn't hurt anything, > but it still seems unnecessary to me. Apparently (and to me, surprisingly), you're right (as far as you set Content-Type, which we do). It's probably just one of those pedanticisms you acquire over time. :-) > (I know there have been many requests for multi-byte character support, > but that's not an easy fix. I think that pretty much requires switching > to using unicode/UTF-8 internally, and this won't be practical without > unicode support compiled into PHP and its regexp libraries.) And the database, if it does string matching, additionally (using LIKE, ~ and whatnot). Take care, -- /\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil ~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311 |