* Pete Resnick wrote:
>On 2/3/15 9:12 PM, Bjoern Hoehrmann wrote:
>> You did not say which document this is for...
>
>-framework.
>
>> ...but if it actually gives the advice above...
>>    
>
>Might I suggest that before commenting on what you think the text might 
>mean, you actually read over the document and see if it says something 
>that is in fact problematic. Since the documents cited in the text I 
>provided are *not* about confusability, and the present document's 
>section 12.5 discusses the issue and what can, and more importantly 
>can't, be done about it, I'd suggest that the rest of what you write is 
>not applicable to either the document or the text to be added.

I think the text to be added is very clear that implementations should
disallow all characters whose implications are not actually understood.
If you cannot produce a complete list of all characters implementations
should disallow with the current version of the Unicode standard, then
my comment seems very applicable to me. Note that I have reviewed the
document before and did not come across the advice the proposed text
claims to be there, and I've checked section 12.5 right now and do not
see it there either.

Regardless, as an example, if, instead of saying

    Even so, implementations that are sensitive to the advice given in 
    this specification (to be careful to only allow characters whose 
    implications they actually understand and, especially for the 
    LetterDigit case, characters that actually are used to write 
    relevant human languages) are unlikely to run into significant 
    problems as a consequence of these issues or potential changes.

the specification were to say something like

    Implementations that heavily restrict which characters they allow,
    like limiting the set of permissable characters to a single script,
    are unlikely to run into significant problems as a consequence of 
    these issues or potential changes.

I would find that much less objectionable.
-- 
Björn Höhrmann · mailto:[email protected] · http://bjoern.hoehrmann.de
D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 · http://www.bjoernsworld.de
 Available for hire in Berlin (early 2015)  · http://www.websitedev.de/ 

_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis

Reply via email to