Re: [precis] local case mapping

Peter Saint-Andre <stpeter@stpeter.im> Tue, 08 October 2013 22:38 UTC

Return-Path: <stpeter@stpeter.im>
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 A580711E8102 for <precis@ietfa.amsl.com>; Tue, 8 Oct 2013 15:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.894
X-Spam-Level:
X-Spam-Status: No, score=-101.894 tagged_above=-999 required=5 tests=[AWL=0.705, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HXDnTiOY6yum for <precis@ietfa.amsl.com>; Tue, 8 Oct 2013 15:38:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1814D11E8109 for <precis@ietf.org>; Tue, 8 Oct 2013 15:38:23 -0700 (PDT)
Received: from [192.168.1.3] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id CB661414D9; Tue, 8 Oct 2013 16:44:18 -0600 (MDT)
Message-ID: <52548959.1040306@stpeter.im>
Date: Tue, 08 Oct 2013 16:38:17 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
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> <20131008211611.GA45541@mx1.yitter.info>
In-Reply-To: <20131008211611.GA45541@mx1.yitter.info>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 22:38:29 -0000

On 10/08/2013 03:16 PM, Andrew Sullivan wrote:
> 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.
Agreed.
>   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
>
Well it's a bit mealy-mouthed for us to say we don't prefer simple case 
mapping. Better, I think, to say "apply full case mapping".

Peter