Re: [precis] local case mapping
Peter Saint-Andre <stpeter@stpeter.im> Fri, 18 October 2013 17:00 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 CB05C11E8318 for <precis@ietfa.amsl.com>; Fri, 18 Oct 2013 10:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.342
X-Spam-Level:
X-Spam-Status: No, score=-102.342 tagged_above=-999 required=5 tests=[AWL=0.257, 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 BXDZcFZohKcu for <precis@ietfa.amsl.com>; Fri, 18 Oct 2013 10:00:07 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A63C711E8311 for <precis@ietf.org>; Fri, 18 Oct 2013 09:58:21 -0700 (PDT)
Received: from sjc-vpn3-1120.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 983114100F; Fri, 18 Oct 2013 11:04:45 -0600 (MDT)
Message-ID: <526168A8.8050401@stpeter.im>
Date: Fri, 18 Oct 2013 10:58:16 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Takahiro Nemoto <t.nemo10@kmd.keio.ac.jp>
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> <52548959.1040306@stpeter.im> <20131008224453.GG46045@mx1.yitter.info> <6E7B1D8D-AB23-4FD7-99B6-D1A333772A37@kmd.keio.ac.jp>
In-Reply-To: <6E7B1D8D-AB23-4FD7-99B6-D1A333772A37@kmd.keio.ac.jp>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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: Fri, 18 Oct 2013 17:00:13 -0000
On 10/18/13 1:41 AM, Takahiro Nemoto wrote: > I would like to address some of the comments that I have received > from Peter, Alexey, and Andrew in this email. > > First, I would like to do some revision to the document according to > Peter's suggestions. Also, I am planning to split the "References" > section into "Normative References" and "Informative References". That's all good. > One > other thing, as Andrew has pointed out, I am thinking of local case > mapping as followings: > > Purpose: The purpose of local case mapping is to increase the > probability of matching-result from the comparison between uppercase > and lowercase characters, targeting language-dependent characters. Works for me. The text in the I-D is now: The purpose of local case mapping is to increase the probability of matching-result from the comparison between uppercase and lowercase characters, targeting locale and locale and context-dependent characters. I stumbled over the last clause. I think it would be a bit clearer as follows: targeting characters whose mapping depends on locale or on locale and context. > Regarding the final sigma, > > Currently, the handling order of PRECIS Framework is local case > mapping to case mapping. Because of this, when Σ=U+03A3 is handled by > local case mapping that apply the context-sensitive (i.e., > "language-insensitive") mappings from SpecialCasing.txt, it becomes > ς=03C2, in the end, when ς=03C2 is case mapped, it will still result > in σ=03C3. > > For this reason, final sigma is not one of the targets for local case > mapping. OK, I understand that logic. However, it implies that if a protocol or PRECIS profile uses local case mapping then it will benefit from the nice language-sensitive mappings in SpecialCasing.txt but it can't handle Greek final sigma in a context-sensitive way. I *think* that's probably fine for comparison purposes. To use my previous example, a nickname of "ΦΙΛΟΣ ΜΟΙ" would be case folded to "φιλοσ μοι" (not "φιλος μοι"). That comparison would be applied consistently, without attention to context (i.e., we wouldn't get "φιλοσμοι" if there's no space but "φιλος μοι" if there is a space). This seems to be an acceptable approach, I just wanted us to be clear that this is what we're doing. :-) > Also, in the next I-D, I would like to add "local case mapping can be > selected only when case mapping is selected using the PRECIS > Framework profile" and "casefolding in this document means full > casefolding described in the Casefolding.txt file". That's sensible. Peter -- Peter Saint-Andre https://stpeter.im/
- [precis] local case mapping Peter Saint-Andre
- Re: [precis] local case mapping Takahiro Nemoto
- Re: [precis] local case mapping Takahiro Nemoto
- Re: [precis] local case mapping Andrew Sullivan
- Re: [precis] local case mapping Peter Saint-Andre
- Re: [precis] local case mapping Andrew Sullivan
- Re: [precis] local case mapping Peter Saint-Andre
- Re: [precis] local case mapping Andrew Sullivan
- Re: [precis] local case mapping Takahiro Nemoto
- Re: [precis] local case mapping Takahiro Nemoto
- Re: [precis] local case mapping Peter Saint-Andre