Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <20150811231222.GK30785@ted.stsp.name>
References: 
 <trinity-1607eaec-70dc-4c40-93e5-ee25b5b141c3-1439225186511@3capp-gmx-bs13>
	<55CA5C74.7080304@wandisco.com>
	<1E5EFC78-2847-429F-8B53-A38F1C9A456E@azeotrope.org>
	<20150811231222.GK30785@ted.stsp.name>
Date: Tue, 11 Aug 2015 21:09:15 -0400
Message-ID: 
 <CAOCN9rxiB0eLbPU8fP1A_n0Nyq9cHvjp8NsvwBuZfe8qeCyG2A@mail.gmail.com>
Subject: Re: question about subversion 1.9 unicode normalization status
From: Nico Kadel-Garcia <nkadel@gmail.com>
To: Dave Huang <khym@azeotrope.org>,
	"users@subversion.apache.org users" <users@subversion.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 11, 2015 at 7:12 PM, Stefan Sperling <stsp@elego.de> wrote:
> On Tue, Aug 11, 2015 at 05:11:10PM -0500, Dave Huang wrote:
>> On Aug 11, 2015, at 15:35, Branko =C4=8Cibej <brane@wandisco.com> wrote:
>> >
>> > On 10.08.2015 18:46, Attila Soki wrote:
>> >> hi,
>> >>
>> >> i saw the entry "reimplement UTF-8 fuzzy conversion using utf8proc (r=
1511676)"
>> >> in the changelog and hoped this would be the fix for
>> >> http://subversion.tigris.org/issues/show_bug.cgi?id=3D2464
>> >>
>> >> but after a quick test it seems to be still broken.
>> >
>> > In my not even a bit humble opinion, what's broken is Apple's HFS, not
>> > Subversion.
>>
>> Exactly what is broken in Apple's HFS? MacOS uses one of the Unicode Nor=
malization Forms. Perhaps it's not the same one that Windows uses, but ther=
e's nothing wrong with that. While it's unfortunate that SVN didn't handle =
this correctly from the start, it doesn't make it Apple's fault. Unicode 2.=
0 talked about normalization/canonicalization in 1996, and TR 15 has been a=
round since about the same time--both predating SVN's development by years.=
 Of course, most people weren't thinking about Unicode back then, and a fil=
ename was considered to be some opaque string of bytes, so I don't particul=
arly blame SVN either. If anything, Unicode should've just declared one can=
onical form instead of giving options. But while HFS(+) is old and is due f=
or an overhaul, its use of Unicode NFD isn't broken.

One can also avoid Unicode like the plague of stable programming that
it is. It's awkward enough to stabilize *any* filesystem operations
without trying to "normalize" the translations of anything that is not
internal binary compnents of a file, itself.