On 10/9/13 6:45 AM, Peter Saint-Andre wrote: > On 10/8/13 10:23 PM, Andrew Sullivan wrote: >> On Tue, Oct 08, 2013 at 08:36:31PM -0600, Peter Saint-Andre wrote: >>> I take it you're suggesting that we add a bit explaining that PRECIS >>> does *not* include a way to specify the locale for purposes of >>> restricting the range of codepoints that are allowed in a given >>> profile? >> >> Because I'm not as clever as you, it hadn't occurred to me to suggest >> that exactly. But that might well be another way to cope with the >> topic: "Yeah, we know you want this. If you really want it, you need >> a special-purpose internationalization framework, and not a >> general-purpose one." The more I think about it, the more I think >> that's true. The user's linguistic environment has so many >> tightly-bound implications for an application that if you really need >> to know about it, your application needs to get dirty. (Come to think >> of it, this is another nice way of explaining the IDN problem around >> this sort of request too. Thanks!) > > Something along those lines sounds good.
Here is proposed text (for the end of section 9.5): The challenges inherent in supporting the full range of Unicode code points has in the past led some to hope for a way to programmatically negotiate more restrictive ranges based on locale, script, or other relevant factors. As a general-purpose internationalization technology, the PRECIS framework does not include such a negotiation mechanism. Applications requiring a tighter binding to the user's linguistic environment might need to develop extensions to the PRECIS framework, or special-purpose internationalization technologies. Peter -- Peter Saint-Andre https://stpeter.im/ _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
