IETF Logo Mail Archive

Re: [I18ndir] I-D on filesystem I18N

John R Levine <johnl@taugh.com> Wed, 08 July 2020 16:23 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 68ACB3A0F04 for <i18ndir@ietfa.amsl.com>; Wed, 8 Jul 2020 09:23:56 -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=F8uAF59d; dkim=pass (1536-bit key) header.d=taugh.com header.b=kTKzo+PK
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 H-buR1gtZ9LR for <i18ndir@ietfa.amsl.com>; Wed, 8 Jul 2020 09:23:54 -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 0522A3A0F03 for <i18ndir@ietf.org>; Wed, 8 Jul 2020 09:23:53 -0700 (PDT)
Received: (qmail 79644 invoked from network); 8 Jul 2020 16:23:51 -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=13717.5f05f317.k2007; i=johnl-iecc.com@submit.iecc.com; bh=MrdocDTm/wZr9Dc6xlZXDhRcww02fQuxq8VkVlOA2gw=; b=F8uAF59dgsDAhpL6ReHdK0kstx0LUp62vMDKw5GmGqHhGtUJDAJpThUmpWp6P3Jp+mOvoX5C7RZRtlFCu67YjXI0dChUp3d7VcLrdz7kwsKiDHQfEhv4hZrQ2zDaam1v/X7mu13NSKsmxV1NcdcIhen4xyePcC2C25ZPzlfyDQr8BK7IS6Ex2+720scV9n2P8lU3OQn7iyPDmUtYcyRGdLwlRY1jDzWwxeWHegspgL4tx5daTBRiOUKkuUhv5qzA
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=13717.5f05f317.k2007; olt=johnl-iecc.com@submit.iecc.com; bh=MrdocDTm/wZr9Dc6xlZXDhRcww02fQuxq8VkVlOA2gw=; b=kTKzo+PKoNQS1KsE0j8Kf6oY6W2iJ3Z1kGKYD/pv7DmVwzPlQK0KBTr4OVISO9x3qmOPh1BKqUhTUO25HgzFzzwkzEfkdbTgWUTuPO6FFpAhtleipl7buAj5im3ThAB+rBRlFfbStq9DIgBIt6nFYhzns5z+J1Ho6X41D6jKkMXj6u3qL/jgssq7sbt9Xy9EQFBksUzDWu/P7rJiKqjuPucy+xuDOzs8VKB6dIG35cVfntR07lZWQha5j14IwuC0
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 16:23:51 -0000
Date: Wed, 08 Jul 2020 12:23:53 -0400
Message-ID: <alpine.OSX.2.22.407.2007081222580.24789@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Nico Williams <nico@cryptonector.com>
Cc: i18ndir@ietf.org
In-Reply-To: <20200708161644.GO3100@localhost>
References: <20200706225139.GJ3100@localhost> <20200708004250.01B111C67670@ary.qy> <20200708013311.GZ3100@localhost> <alpine.OSX.2.22.407.2007072143001.22521@ary.qy> <20200708032341.GF3100@localhost> <alpine.OSX.2.22.407.2007081147001.24605@ary.qy> <20200708161644.GO3100@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/dlT-FwmkCQHiCtb8aZ7DVIkx5Cs>
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 16:23:56 -0000

>> 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.
>
> Several filesystems do just that.  No one implements what NFSv4 says to
> do for I18N, so clearly persisting in that approach won't help.
>
> Having a document specifically targeted at filesystem implementors is
> much more likely to help, even if we have no authority over them.  After
> all, we don't have a protocol compliance police either, yet we write
> protocol documents all the time.

So long as we make it clear what kind of advice it is, and we acknowledge 
the issues in migrating from what they do now to UTF-8 nirvana, that could 
be somewhat useful.

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

v2.23.0 | Report a Bug | By Email