|
As I said on the call, there is a HUMAN expectation that case
doesn't matter - so lots of compute time is spent case mapping.
For machine interactions, I'm less convinced that there's a
problem with case sensitive strings.
bill
--
On 9/7/18 7:19 AM, Rob Godfrey wrote:
For the case
insensitive comparison rules, Iâm looking towards
adopting the recommendation from W3C Character Model
for Web draft for case-insensitive Unicode
comparisons. The doc seems to be in a permanent WD
state, though.
Â
https://w3c.github.io/charmod-norm/#sec_unicode_cs
Â
Itâs quite the
rabbit hole, but I think the implementation burden
is already handled by many/most Unicode aware string
handling libraries.
Yes - without more context such as the language being
used it does not seem like the problem can actually be
solved :)
ÂÂ
Before I head
down that direction, any objections?
Â
No objections. My only concerns are clarity in definition
and the wide availability of existing implementations of
whatever algorithm is adopted. This approach would seem to
satisfy those criteria.
--
_____________________________________________________________________________
Red
Hat GmbH,Âwww.de.redhat.com,
Registered
seat: Grasbrunn, Commercial register: Amtsgericht
Muenchen, HRB 153243,
Managing
Directors: Paul Argiry, Charles Cachera, Michael
Cunningham, Michael O'Neill
|