Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: question about subversion 1.9 unicode normalization status
From: Dave Huang <khym@azeotrope.org>
In-Reply-To: <55CB0B46.3050500@wandisco.com>
Date: Thu, 13 Aug 2015 11:59:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D36BBF5-EC57-4A99-9E9E-AACBDA7CD139@azeotrope.org>
References: 
 <trinity-1607eaec-70dc-4c40-93e5-ee25b5b141c3-1439225186511@3capp-gmx-bs13>
 <55CA5C74.7080304@wandisco.com>
 <1E5EFC78-2847-429F-8B53-A38F1C9A456E@azeotrope.org>
 <55CB0B46.3050500@wandisco.com>
To: "users@subversion.apache.org users" <users@subversion.apache.org>

On Aug 12, 2015, at 4:00, Branko =C4=8Cibej <brane@wandisco.com> wrote:
>=20
> Yay for misunderstandings. :)
>=20
> The problem with HFS is that it normalizes paths: regardless of how =
your
> file names are (de)normalised when you create them, they're stored in
> HFS in NFD form.

I don't think I misunderstood anything; I said in my message that =
filenames are stored in NFD, and that I don't think that's broken: "But =
while HFS(+) is old and is due for an overhaul, its use of Unicode NFD =
isn't broken."

That's great that you're working on the issue though. While I only work =
in English these days and am not affected by this problem, I used to =
work at a place were a lot of l10n stuff was going on, and saw all sorts =
of languages and accented letters :)
--=20
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 39 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ =
PL++