Re: [I18ndir] I-D on filesystem I18N

Nico Williams <nico@cryptonector.com> Wed, 08 July 2020 01:41 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22AD63A0D40 for <i18ndir@ietfa.amsl.com>; Tue, 7 Jul 2020 18:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25QVAFiDOWwW for <i18ndir@ietfa.amsl.com>; Tue, 7 Jul 2020 18:41:01 -0700 (PDT)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990113A0D1A for <i18ndir@ietf.org>; Tue, 7 Jul 2020 18:41:01 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id BE1E7480A8B; Wed, 8 Jul 2020 01:41:00 +0000 (UTC)
Received: from pdx1-sub0-mail-a38.g.dreamhost.com (100-96-23-13.trex.outbound.svc.cluster.local [100.96.23.13]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id F16E8481079; Wed, 8 Jul 2020 01:40:59 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a38.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Wed, 08 Jul 2020 01:41:00 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Zesty-Battle: 13a573e81d33e0bb_1594172460604_3210989810
X-MC-Loop-Signature: 1594172460604:3072203621
X-MC-Ingress-Time: 1594172460604
Received: from pdx1-sub0-mail-a38.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a38.g.dreamhost.com (Postfix) with ESMTP id A9235B479F; Tue, 7 Jul 2020 18:40:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=0nLqLXuXQM2HD7 ogkSkGMu/KVg4=; b=ExZsgSJfrcYESafZw9yl4QvZzE+LElHNLT4JoOwxkalCD8 yiPlp082eCOF6YGwfbBORpB/GEtn/Si/WQ7dbj6YKYC5NFm08yrpMC/jDP2qs+Do FauCad3PLGzug96mUa5BiP+YKxrjH94s+iSdMrJuJkGMrKEBNxtF7VpHezPgY=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a38.g.dreamhost.com (Postfix) with ESMTPSA id 56B80B479C; Tue, 7 Jul 2020 18:40:57 -0700 (PDT)
Date: Tue, 07 Jul 2020 20:40:55 -0500
X-DH-BACKEND: pdx1-sub0-mail-a38
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Asmus Freytag <asmusf@ix.netcom.com>, i18ndir@ietf.org
Message-ID: <20200708014054.GB3100@localhost>
References: <20200706225139.GJ3100@localhost> <90740541-ab72-ffaf-ff3e-5a27b5805eae@ix.netcom.com> <9044C737C36C0787B9EAE190@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9044C737C36C0787B9EAE190@PSB>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduiedrudeigdehtdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecuggftrfgrthhtvghrnhepffdtkeethfeuteeviefgfeegjeetjedvhfehgfdvtdefueejheelgeeuhffghffgnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/M1v9-SuWSUAV6DGeTxR_5kJeNuo>
Subject: Re: [I18ndir] I-D on filesystem I18N
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2020 01:41:03 -0000

On Tue, Jul 07, 2020 at 09:31:55PM -0400, John C Klensin wrote:
> --On Tuesday, July 7, 2020 16:43 -0700 Asmus Freytag
> <asmusf@ix.netcom.com> wrote:
> > However, early case-insensitive file systems did not preserve
> > case. Not sure how rare this has become.
> 
> Well, Unix, and every Unix-derived system I know of (definitely
> including Linux, FreeBSD, and NetBSD) are case-sensitive and
> getting anywhere near their file names with Case Folding or even
> lower casing will cause rather interesting problems.  One the
> case-insensitive side, I've heard of a system called "Windows"
> that usually preserves case but does not guarantee to do so and
> many operations, in practice, don't.  

At least ZFS supports case-insensitivity as an option.  ZFS is available
on just about every Unix and Unix-like OS today, and is quite popular.

That said, I doubt anyone enables case-insisitivity in ZFS datasets on
Unix unless they intend to share it with Windows clients and users
expect case-insensitivity.  Indeed, that's the reason that ZFS has this
option at all: Windows interoperability.

> In addition, Asmus caught at least one case where your
> terminology is inconsistent with that of Unicode.  Such

Yes yes, I beg your forgiveness.  I wrote "normal form" instead of
"normalization form".  A silly editing error.

> inconsistencies (at least if not specifically identified and
> justified) are an invitation to reader confusion or worse.  As
> one more example, you should not be talking about case folding
> and then lower casing.  They are different and have different
> implications.  And, fwiw, most of my Turkish-speaking and

Did you not read that text?  I only mentioned lower case in the context
of explaining in introductory text what case-folding is.  And I did NOT
say that they are the same thing.

> writing colleagues would disagree that U+0131 "could" or should
> be considered equivalent to U+0069.  In my experience, that

The idea was to describe how an admin might square that circle in a
case-insensitive filesystem, and then I did not endorse it.  The idea
was to describe how custom case-folding tailorings (FYI, that's the term
Unicode uses, 'tailoring') might come about.

There will be time to address all the nits.  The big idea is more
interesting.

Nico
--