Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (herse.apache.org: domain of ehuels@gmail.com designates
 64.233.162.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=CT7Rocm7yThhLY5CoxxWtEJVVE7cS10HAVwD8YE/WnGUy2e8RLg6SC7AF0UpTvq+xLLGesGMAYyX1TMe3pYMoJsfVIO4YD9+GELZ6ZIlkFIf6+0t7bdpETYqQrOyp/s9w8K3+xaDUB1N+aSELVJtXWTdtvNcNd4z6o61Uo+2XYE=
Message-ID: <aea328ab0707170557j3526dad1q12cb47d26f080815@mail.gmail.com>
Date: Tue, 17 Jul 2007 14:57:15 +0200
From: "Erik Huelsmann" <ehuels@gmail.com>
To: "APR Developer List" <dev@apr.apache.org>
Subject: Re: apr_filepath_encoding on Darwin
In-Reply-To: <20070717124041.GD2587@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <aea328ab0707170514i322c6209me61cb7aed4204e09@mail.gmail.com>
	 <20070717122529.GB2587@redhat.com>
	 <aea328ab0707170531u261c1ae7m2f2150d59ceab5@mail.gmail.com>
	 <20070717124041.GD2587@redhat.com>

On 7/17/07, Joe Orton <jorton@redhat.com> wrote:
> On Tue, Jul 17, 2007 at 02:31:27PM +0200, Erik Huelsmann wrote:
> > On 7/17/07, Joe Orton <jorton@redhat.com> wrote:
> > >This is deliberate; on Unix the character set used for filenames is
> > >dictated by the locale settings (e.g. LC_CTYPE), by convention.  There
> > >is certainly no Unix standard which dictates that all filenames must be
> > >UTF-8-encoded Unicode, so APR cannot enforce that.
> >
> > I didn't mean to imply this should apply to any unix, but the Darwin
> > docs do seem to say that this is the standard on Darwin.
>
> Presuming that Darwin still has a configurable locale like any other
> Unix, is the "standard" really anything other than a "default"?

Well, as I quoted in my post to Lucian from the url I posted before:
"All BSD system functions expect their string parameters to be in
UTF-8 encoding and nothing else."

That doesn't seem like a default to me, more like a requirement, but
if I were certain, I would have posted a patch instead of an inquiry.

bye,


Erik.