Does the Apache rpm shipped with CentOS 4.x have UTF-8 enabled as the default document encoding for all virtual servers? If so, then why?
Regards, Jim
-- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3
On Tue, 10 Jan 2006, James B. Byrne wrote:
Does the Apache rpm shipped with CentOS 4.x have UTF-8 enabled as the default document encoding for all virtual servers? If so, then why?
Yes. See line 730 of /etc/httpd/conf/httpd.conf.
Why? I can't speak for Red Hat, but I for one support the move away from the various, and rather limited, ISO-* character sets to the much broader UTF-8 standard. For one thing, it's now the default shell environment on RHEL/CentOS boxes. For another, it's (for me, at least) a better output format for XML -> HTML transformations, especially those that contain non-Latin characters like those in the Greek alphabet.
On Tue, 2006-01-10 at 08:22 -0800, Paul Heinlein wrote:
On Tue, 10 Jan 2006, James B. Byrne wrote:
Does the Apache rpm shipped with CentOS 4.x have UTF-8 enabled as the default document encoding for all virtual servers? If so, then why?
Yes. See line 730 of /etc/httpd/conf/httpd.conf.
The why (for CentOS) is because that is the default from upstream.
Why it is the default from upstream, I have no idea.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Jan 10, 2006 at 10:40:34AM -0600, Johnny Hughes wrote:
On Tue, 2006-01-10 at 08:22 -0800, Paul Heinlein wrote:
On Tue, 10 Jan 2006, James B. Byrne wrote:
Does the Apache rpm shipped with CentOS 4.x have UTF-8 enabled as the default document encoding for all virtual servers? If so, then why?
Yes. See line 730 of /etc/httpd/conf/httpd.conf.
The why (for CentOS) is because that is the default from upstream.
Why it is the default from upstream, I have no idea.
All major distributions are moving toward UTF-8 in the past couple years. The main reason is to stop the PITA of charset conversion. If you ever tried migrating a Samba2 server to Samba3 in a multi-charset environment, you will feel the pain.
I have a client whose network is composed of computers running with several different charsets (CP850, ISO8859-1, UTF-8 and SHIFT-JIS are the more common ones). Once installing a CentOS 4 server, I have to get rid of the standard samba package and replace it with Samba 2, exactly because of charset issues, since Samba 2 used charset conversion bypass, and Samba 3 doesn't support it (and yes, I tried "raw").
I only wish we had UTF-8 from the start.
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-
James B. Byrne -
Johnny Hughes -
Paul Heinlein -
Rodrigo Barbosa