http://bugs.winehq.org/show_bug.cgi?id=16514
--- Comment #17 from Jörg Höhle hoehle@users.sourceforge.net 2010-04-23 07:06:31 --- What need be done is IMHO 1. See what encoding the database(s) use. There's no need mucking with encodings on the web side of things if the DB contains junk (that is a mixture of ISO-8859-1 and UTF-8). Who can tell what it is? 2. See & control what encodings are used between applets and DB (connection level). 3. Control what the web applets spit out to the browsers.
Nowadays the answer is obviously UTF-8. It's equally obvious that the Wine databases did not start that way.
Last but not least, it's not the web server's choice to impose an encoding on the browser. It ought to listen to the client's advertised capabilities (Accept-*) and *should* convert on the fly if e.g. the browser indicates that it only accepts ISO-8859-1. Few servers actually do this.
4. Tell the SMTP component about the correct encoding so it can send out proper MIME formatted e-mails (quoted printable when needed etc.)
Or, to respond to your question directly:
Would it be a problem if the Content-Type of the AppDB page is changed to be the same as the one for the Bugzilla page?
First you need to make sure that the AppDB applets actually receives the "micro" character from the DB. Only afterwards can you convert its encoding to what the rest of the AppDB page uses.