IETF Logo Mail Archive

Re: [I18ndir] I-D on filesystem I18N

John R Levine <johnl@taugh.com> Wed, 08 July 2020 15:50 UTC

Return-Path: <johnl@taugh.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 9D5023A0E94 for <i18ndir@ietfa.amsl.com>; Wed, 8 Jul 2020 08:50:43 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=E3o+Jgvs; dkim=pass (1536-bit key) header.d=taugh.com header.b=u9d2xgQi
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 cKkqk490QH0w for <i18ndir@ietfa.amsl.com>; Wed, 8 Jul 2020 08:50:41 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 0AF033A0EF3 for <i18ndir@ietf.org>; Wed, 8 Jul 2020 08:50:39 -0700 (PDT)
Received: (qmail 67746 invoked from network); 8 Jul 2020 15:50:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=108a0.5f05eb4e.k2007; i=johnl-iecc.com@submit.iecc.com; bh=Vualla3MvQzVL66HvAlMmsCJHu0HCnvcD9CKJhL3wxk=; b=E3o+JgvsyiaG9gHoNmdMUH3TQywhptWE7gWEodK/3n4oa+8dre2NpJ5sfF3/YmDz90yHvqWD9QW+Or0wJGzsr3GcaOXRp2x5fPfJY1QmyIDMT+7QFT97h2seT0EDle1rQduLQ2YBRLTxqgOBS0TyWXToVeA6cgYiskuA7Jwzp6jCwAMrH07ENf+NNNQgp196cKyOYsbRZ0Whmr3HaFu8n1Nyu7fzOmA4iLE6cEDSI2viB4Rsq6PZ2gx++2omh0A+
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=108a0.5f05eb4e.k2007; olt=johnl-iecc.com@submit.iecc.com; bh=Vualla3MvQzVL66HvAlMmsCJHu0HCnvcD9CKJhL3wxk=; b=u9d2xgQins+yEpuSt7C3PGGflG2SkYyDy991lvqGdvlZWUcxGbuGmQGHerWgcb3k+M46+7rebyk7e94o6Fsv7by/NFOB1tRZNt9VLOWChO26k8gg0l1W2rIKtGjjrjZh5YqGqKgjvYhm4Gw+BQjjli8brTQC+nP5JhdR4YnEqdNgzUBDDfV7gCnyyGFwdSGSZXLgH4sJhGqEsNyxexPBChGAGZClz3yP9dBsKA/0Q9FESMH3Br3mPMvoavgJK9g9
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 08 Jul 2020 15:50:37 -0000
Date: 8 Jul 2020 11:50:40 -0400
Message-ID: <alpine.OSX.2.22.407.2007081147001.24605@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Nico Williams" <nico@cryptonector.com>
Cc: i18ndir@ietf.org
In-Reply-To: <20200708032341.GF3100@localhost>
References: <20200706225139.GJ3100@localhost> <20200708004250.01B111C67670@ary.qy> <20200708013311.GZ3100@localhost> <alpine.OSX.2.22.407.2007072143001.22521@ary.qy> <20200708032341.GF3100@localhost>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/jW-TI_zVP1_NV_TQPNz6R1M45Nk>
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 15:50:44 -0000

> We have two choices: leave it as-is, or find a way to make it a better
> match for reality while achieving our I18N goals.  I believe we can do
> the latter, and I believe that the former kinda sucks.

If I wasn't clear enough, my point is that any remote file scheme has to 
deal with situations where two different names refer to the same file.

Case folding and Unicode normalization are just examples of that, and as 
far as I can see, not particularly interesting ones.  There is no problem 
to be solved here.

I suppose we could offer advice saying it would be nice if file systems 
used UTF-8 names and consistent normalization but I don't see why anyone 
would pay attention.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.8.7 | Report a Bug | By Email