Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Errors-To: <wrowe@rowe-clan.net>
Message-Id: <5.2.0.9.2.20030311133211.01e80138@pop3.rowe-clan.net>
Date: Tue, 11 Mar 2003 13:38:24 -0600
To: dev@httpd.apache.org
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Subject: Re: Apache UTF-8
In-Reply-To: <69EB8DF424C8FE409AF8FFAF1B19787A16A5FE@ftlpexch502>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Win32 and some UTF-8 unicies effectively are, as their file names are 
all in utf-8.  About the only non-ASCII stuff in your .conf file are usually
comments and file names and paths, and uri's.  There is no translation
(and will probably never be) so your httpd.conf should just follow your
site and platform conventions.

In any case, there is alot more work to be done around the arguments
to and from the clients - there is no defined way for a request to indicate
the character set the request is coming in with.  One group advocates
that all URI's should be sent in UTF-8.  Existing browsers are a real
obstacle to 'enforcing' that.

In any case, I don't see why you can't use UTF-8 right now, 99.5% of
most configuration files are ASCII subsets, common to UTF-8.  *If* your
filenames and paths are in UTF-8 use that.  If they are in another
encoding, you must use that specific encoding in your httpd.conf file.

There really is no magic to it.  Apache directives are all ASCII-subset.

Bill


(Don't post HTML messages to mailing lists please.)

At 11:44 AM 3/11/2003, Juan Rivera wrote:

>I'm starting to look into what would it takes to support UTF-8 in configuration files. This means modules must have to handle parameters in UTF-8 format.