From: Carsten K. <car...@us...> - 2002-10-28 19:13:07
|
Do you think it would cause any problems to just commit this change of FieldSeparator to '\xff'? I'm going to leave it this way on my Wiki for a while to see how it works out as a permanent change. If this is not a good idea, maybe add a check in config.php for CHARSET==utf-8 and set FieldSeparator accordingly? I'm amazed that I'm now able to use UTF-8 (Japanese etc) text in my personal wiki, even though my system has only MySQL 3.2.3.49 which does not support UTF-8, and is actually configured for iso-8859-1. The last time I tried to use UTF-8 in PhpWiki (over a year ago) I had to use PostgreSQL, and there were still lots of garbage display problems then. So far the only (minor) problems I see running PhpWiki CVS in utf-8 are the field names on the DebugInfo page and character translation problem on the Sign In page. I'm sure these two minor problems can be worked out, and if anyone volunteers to translate we could have Japanese/Chinese localizations included with PhpWiki too, the admin would just have to change CHARSET to utf-8 in index.php during installation. Carsten On Sunday, October 27, 2002, at 11:34 am, Jeff Dairiki wrote: > This is hackish, but: you might try changing > $FieldSeparator to '\xff' (which is an illegal > byte in UTF-8) or to one of the lesser used ASCII |