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". 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. 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. 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". Regards, Nemo On 2013/10/09, at 7:44, Andrew Sullivan <[email protected]> wrote: > On Tue, Oct 08, 2013 at 04:38:17PM -0600, Peter Saint-Andre wrote: >> case mapping. Better, I think, to say "apply full case mapping". > > Sure, yes. > > A > > -- > Andrew Sullivan > [email protected] > _______________________________________________ > precis mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/precis
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
