-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/21/13 2:19 PM, Florian Zeitz wrote: > Am 12.11.2013 03:15, schrieb Yoshiro YONEYA: >> Dear all, >> >> As we discussed at WG meeting in Vancouver, the latest framework >> document seemed fine but updated a lot since previous WG LC, so >> chairs decided to perform WG LC again to the document. >> >> This message starts two weeks Working Group Last Call (WGLC) on >> draft-ietf-precis-framework-11.txt (PRECIS Framework: Preparation >> and Comparison of Internationalized Strings in Application >> Protocols). >> <http://tools.ietf.org/id/draft-ietf-precis-framework-11.txt> >> >> Please review the document and send comments to the list >> ([email protected]), the co-chairs ([email protected]), >> or the authors ([email protected]) by >> the end of WGLC. >> >> The WGLC will end on Monday, Nov 25th. >> > > I've reread the draft in its entirety now that some time has > passed. I have a few minor comments (some of them nits, which IMHO > is a good sign), but overall I'm very pleased with it and think all > feedback has been addressed.
Thanks for the review! > Generally I think we need to update the draft to Unicode 6.3. If > we don't, at least the claims that Unicode 6.2 is the latest > version at the time of writing should be removed ;). Yes, I noticed that while completing my own review earlier this week. > Section 4.1.1 claims width mapping is an aspect of NFKC. While this > is true it is more generally an aspect of compatibility > decomposition, and therefore happens when NFKD is employed. I think > the text should reflect this. How about this? OLD Because one aspect of Unicode normalization form KC (NFKC) is width mapping, a profile that uses NFKC does not need to specify width mapping. NEW Because Unicode normalization form KC (NFKC) performs width mapping via compatibility decomposition and subsequent recomposition, a profile that uses NFKC does not need to specify width mapping. > Section 4.1.3 right now says: «Use of the Unicode Default Case > Folding algorithm is RECOMMENDED.» That statement is broader than > we want it to be. Use of that algorithm is certainly recommended, > but if and only if case-preservation is not desired. Correct. A minor note: the Unicode specification does not use the term "Unicode Default Case Folding algorithm", so it seems better to refer to it as the "Unicode case folding algorithm" (and also to reference Chapter 5 of the Unicode Standard). Thus: If case preservation is not desired, it is RECOMMENDED to use the Unicode case folding algorithm (see Chapter 5 of the Unicode Standard). > Section 7.11 says the category exempts printable 7-bit ASCII from > other rules. This is untrue. The algorithm does this, utilizing the > category. Good point. How about: By applying this PRECIS-specific category, the algorithm specified under Section 8 exempts most characters in the (printable) ASCII-7 range from other rules that might be applied during PRECIS processing, on the assumption that these code points are in such wide use that disallowing them would be counter-productive. > In Section 8 the paragraph preceding the actual algorithm should > say "Exception*s*" instead of "Exception" in two places. Noted. I too have found some other nits during my review (which I'll try to complete tonight), so I might make a few more comments on the list. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSjqgeAAoJEOoGpJErxa2pcf0QAKU0DmNsH+pNXpH9HfVrq1Sv khkKsssU4wJiooohvpSSUjpuOW8Yl6MXKoPtWws61Ak1qKveda2LT8P9DuA13Pig po7W6ogW4OSIEvvMrw/0JeCkFTmF77AkUUZiQvuYEAqafNzI+5nNwYf+J9nZcwBC s5PDlIEwbokP7A2OWi3yXF78weGcIkXCs/5dOC9RDkhoKMRC42TbVPzdaJB9mQ/d p13qHCBpNTHyZxW0dppYwbSmLZ+b76l+u6hfqrtFnlDqpvEOeVPJd/UXVUuJe37v 6/XrEE5MVwfH3AVmVJq7t0ij0W9Qhi1FG39OAGj9qW+qb12VXrl+seoylhcB5WlB 9Kf6UOSM8jUWfDpHR7mvtYX660B/LvBMfCwvpxURPi2HWpuyia/7piGcGkvaUXqn rUkI5rlpRFd8HWRep16dVQRyu5q3d21inDoRcKtdzRDHTpnOyTZVSH+o9hKJ44HQ HZ8RR7hiAxHb7+HBLIsrGlrtZ+WT6Wji5N7qGaqV5kDBXPgp6dAzrz74FczNrYcO NMA+7ewapJgFLtEmnI03o/ahGtgVpHnIeLaeE8XK+szH2FIuuLkWfqQfnMBPv2+n fHvUQuk2qu1xhA+I+OlA7b92aydKY/XH80t8msNWRFIjxNcQFk9XKOUagIspsD2E GKYh5abwwNdrHtAHO3eh =4zwE -----END PGP SIGNATURE----- _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
