dkl at redhat.com
Mon Jan 6 22:53:21 UTC 2003
Seems to be working for us here using 2.17.1. I created the database and
told it to use UTF-8 for the database encoding. Then added the following
META tag to the header template
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
People have since been able to view and input international characters
if the browser supports it.
On Mon, 2003-01-06 at 17:38, David Miller wrote:
> There's some folks at Netscape who have a strong interest in making
> Bugzilla be completely i18n in the near future.
> Seems like the most obvious thing to do would be to force everything to be
> UTF-8, everywhere.
> However, digging around and doing a little research, it looks like we'd
> need to use perl 5.8.0 and MySQL 4.1 in order to pull that off...
> Anyone have some ideas for sure what we'd need to do for this? I'd like to
> kind of figure out what I'm getting myself into. :-)
More information about the developers