Re: [I18ndir] NFS i18n

John C Klensin <> Fri, 22 May 2020 03:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 40DE63A0E3B for <>; Thu, 21 May 2020 20:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ChhIAe0sZpcE for <>; Thu, 21 May 2020 20:13:32 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 455123A0E36 for <>; Thu, 21 May 2020 20:13:32 -0700 (PDT)
Received: from [] (helo=PSB) by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1jby7h-000MW9-2u; Thu, 21 May 2020 23:13:25 -0400
Date: Thu, 21 May 2020 23:13:18 -0400
From: John C Klensin <>
To: John R Levine <>, Nico Williams <>
Message-ID: <B9C29FA210931FEC78FAF9F8@PSB>
In-Reply-To: <alpine.OSX.2.22.407.2005212130371.6217@ary.qy>
References: <> <> <ra6rmd$1nah$> <20200521224857.GL18021@localhost> <alpine.OSX.2.22.407.2005212130371.6217@ary.qy>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Subject: Re: [I18ndir] NFS i18n
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 22 May 2020 03:13:41 -0000

--On Thursday, May 21, 2020 21:34 -0400 John R Levine
<> wrote:

>> NFSv4 servers can't realistically support varying locales by
>> client, ...
> I agree, but a NFS server in Turkey will want to use Turkish
> case mapping, not some generic UTS46 one-size-fits-badly
> mapping.  That's the point, they don't prescribe a single
> mapping.

Of course, an NFS server in Turkey (or anywhere else) serving
out a file system where names or case-sensitive (such as Unix)
won't want to do case mapping at all.  And that is a fairly good
example of why this is sensitive... and why these folks would be
better off recommending appropriate profiles of PRECIS -- if
necessary, somewhat localized ones-- rather than rolling their
own.  It is also the reason why they need to much more careful
approach to normalization than the handwaving I think I noticed
as I went quickly through the draft.