Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4DA76CF4.8070000@rowe-clan.net>
Date: Thu, 14 Apr 2011 16:53:56 -0500
From: "William A. Rowe Jr." <wrowe@rowe-clan.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Wes Garland <wes@page.ca>
CC: APR Developer List <dev@apr.apache.org>
Subject: Re: Q to unix filesystem developers
References: <4DA7536B.6070808@rowe-clan.net>
 <BANLkTinttbYObgCnkdm3qf+NxJ997it4hQ@mail.gmail.com>
In-Reply-To: <BANLkTinttbYObgCnkdm3qf+NxJ997it4hQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 4/14/2011 3:34 PM, Wes Garland wrote:
> On Thu, Apr 14, 2011 at 4:04 PM, William A. Rowe Jr. <wrowe@rowe-clan.net
> <mailto:wrowe@rowe-clan.net>> wrote:
> 
>     With some multibyte character sets, it may be possible that '/' is one
>     byte of a multibyte sequence.  From a Unix perspective, I presume that
>     it is always treated a path separator and never treated as a multibyte
>     combination filename character.
> 
> 
> FWIW -- I know the whole world isn't Unicode, but that will not happen with any valid
> Unicode encoding.

Correct, utf7/8 are otherwise escaped.  I'm thinking of shift-jis and similar,
where ascii code points are recycled.