Bug 112 – Bugzilla should be configured to use UTF-8

Status
RESOLVED
Resolution
FIXED
Severity
normal
Priority
P2
Component
dlang.org
Product
D
Version
D2
Platform
All
OS
All
Creation time
2006-04-21T09:26:00Z
Last change time
2015-06-09T05:14:41Z
Assigned to
braddr
Creator
smjg

Comments

Comment #0 by smjg — 2006-04-21T09:26:32Z
At the moment, pages on this installation of Bugzilla are served in the ISO-8859-1 encoding. Why? As a result, the code snippet in bug 111 isn't quite what the reporter wrote. I'm puzzled, since a quick glance of URL above implies that UTF-8 is supposed to be the default for new Bugzilla installations. After all, D expects strings to be UTF-8. Its Bugzilla ought to match.
Comment #1 by braddr — 2006-04-21T22:48:32Z
The version of bugzilla installed pre-dates the checkin point for any of the changes in that bug. In the version running right now, there's no forcing of the charset at all. I've added a quick change to set the charset to utf8 but that's a subset of what that bug is about and is quite possibly rather insufficient for good utf8 support. Once 2.20 is released, I'll look at upgrading to it, but I don't intend to do so until after it's actually released. Marking this bug as fixed, as it's as fixed as it's going to get until the next bugzilla release.
Comment #2 by braddr — 2006-04-21T22:50:36Z
Oops.. not 2.20, that's what I'm currently running. The changes will be in 2.22 and d.puremagic.com/bugzilla will be upgraded to that once it's released.
Comment #3 by smjg — 2006-05-22T05:51:46Z
What is d-beta.puremagic.com for, and why is it advertised in notification emails? It's running the same version of Bugzilla as d.puremagic.com, with the only apparent difference being that d-beta is back on ISO-8859-1.
Comment #4 by braddr — 2006-05-22T23:30:15Z
Where, other than bug #1, do you see references to d-beta? I looked at a few messages from recent bugs and see no references.
Comment #5 by smjg — 2006-05-23T07:44:33Z
At the top of every bugmail I've received since 17 May. There was also an odd instance on 1 May when bug 111 comment 4 was posted.