Re: [precis] local case mapping

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 08 October 2013 21:16 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D567121F8E51 for <precis@ietfa.amsl.com>; Tue, 8 Oct 2013 14:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level:
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gr1cyFJiPcju for <precis@ietfa.amsl.com>; Tue, 8 Oct 2013 14:16:14 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6982721F9831 for <precis@ietf.org>; Tue, 8 Oct 2013 14:16:13 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-220-111.meetings.nanog.org [199.187.220.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 0BF7D8A031; Tue, 8 Oct 2013 21:16:11 +0000 (UTC)
Date: Tue, 08 Oct 2013 17:16:12 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <20131008211611.GA45541@mx1.yitter.info>
References: <5227A979.7050403@stpeter.im> <E0DDC70E-DF8C-4163-8ED5-4ADA115DDB72@kmd.keio.ac.jp> <4C8248EF-51BD-4736-A930-E2FEE610EC03@kmd.keio.ac.jp> <20131005031746.GC38902@mx1.yitter.info> <5254632F.6060106@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5254632F.6060106@stpeter.im>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: precis@ietf.org
Subject: Re: [precis] local case mapping
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2013 21:16:27 -0000

On Tue, Oct 08, 2013 at 01:55:27PM -0600, Peter Saint-Andre wrote:
> merely asked the key question, but left it unanswered: what are we
> trying to accomplish here?

Yeah, sorry that I wasn't clear.  I think the issue may actually be
that we can't decide which is needed, and there's a temptation to make
this local policy.  I think that's a bad idea: we should have one
method.  Decisions like this are what "the customers" wanted, I
think.  Therefore,

> 1. Apply the language-sensitive mappings from SpecialCasing.txt
> 2. Apply the context-sensitive (i.e., "language-insensitive") mappings
> from SpecialCasing.txt
> 
> I'm still not sure what to do about about full vs. simple case mapping,
> but I see no strong reason to prefer simple case mapping because I don't
> see a problem with our algorithm resulting in two characters (e.g.,
> "ss") instead of one.

I think all of these are right (so I think we should say that we don't
prefer simple case mapping also).

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com