On 2016/05/07 11:40, John C Klensin wrote:
--On Friday, May 06, 2016 15:54 +0900 "Martin J. Dürst"
<[email protected]> wrote:
On 2016/05/05 07:43, Peter Saint-Andre wrote:
Suggestions for improvement are welcome, especially from
John. (E.g., we might want to more explicitly call out
comparison vs. other contexts in the normative text elsewhere
in §5.2.3).
I think 'compare' should be changed to 'search'. That's the
prototypical use case for CaseFold.
Hmm. If we have to choose, I think I prefer "compare". I just
looked at the subsections on "Default Case Folding" and "Default
Caseless Matching" in Section 3.13 of TUS 8.0 and it says a lot
about comparison and nothing about search. Recommended
compromise: Make the relevant sentence fragment read "most
appropriate when an application needs to compare two strings
such as in search operations."
Fine by me.
I'd still prefer to denounce toCaseFold completely, especially
where identifiers are concerned.
I didn't know which direction we are leaning, but if that's where we are
moving, that would be very fine by me, too.
It just has far too much
potential for being destructive and creating false results
(either positive or negative) when the language context is
unknown. People/designers/implementers who are not prepared to
understand those issues and their implications should really not
be using the thing.
Agreed.
Also, the language in the "Therefore" sentence is somewhat
convoluted. It's unclear which alternative this text prefers.
I suggest that if we want to put the two alternatives on an
equal footing (i.e. make sure the application designer thinks
carefully), then a more parallel sentence structure, avoiding
words such as "carefully", "truly", and "would", would be more
appropriate. What about:
Therefore, application
developers
are advised to carefully consider whether toCaseFold() or
toLower() is more appropriate.
For the reasons above, I'm not sure that an even footing is
appropriate. I'd rather have the guidance be closer to "use
toLowerCase, which your users are likely to understand, unless
you need CaseFolding for some particular reason and understand
its implications"
I'm fine with that. I just had difficulties understanding which way the
bias in the "Therefore" sentence was going, if any. And my guess is that
others may have the same difficulties.
Regards, Martin.
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis