-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should it be called "case-sensitive"? #5067
Comments
I'd be okay with minting "equals" for this (or perhaps "is", since I suspect that's generally what we use these days), in https://infra.spec.whatwg.org/#strings. But someone would have to do the work of identifying all specifications and getting them all changed. |
"visually equivalent"? Though I suppose that would have other issues. |
"case dependent" Might be a good way to go too? |
I reviewed the current use of
Does this sound like the right approach? |
Generally sounds good to me.
Probably you'd also want to include a note that by default, specs using Infra compare strings in this manner. I don't want people to think that if a spec compares strings without linking to "is" or "identical to", then it's undefined. (This would basically be a port of HTML's "Except where otherwise stated, string comparisons must be performed in a case-sensitive manner.")
Since HTML doesn't have automatic cross-linking anyway, we'd have to add a bullet point for the relevant "is" to the Infra section of https://html.spec.whatwg.org/#dependencies. At that point maybe you should just add the appropriate anchor there (probably as an empty At that point https://html.spec.whatwg.org/#case-sensitivity-and-string-comparison will be almost deleted; the remainder would just be the uses of "prefix match" which are in AppCache and which @annevk preferred to leave alone until we remove AppCache. |
Adds definitions for string equality comparisons "is" and "identical to". Includes a blanket statement making these the default for string equality. Also includes a note spelling out the relationship to HTML's former "case-sensitive" comparison and appropriate health warning about visual and encoding sequence identity. Helps with whatwg/html#5067.
https://html.spec.whatwg.org/multipage/infrastructure.html#case-sensitivity-and-string-comparison
When discussing issue #5066 members of the I18N WG expressed concern that the use of the term "case-sensitive" was misleading, since what is actually happening is codepoint-by-codepoint comparison. Should "case-sensitive" be called something else, such as "identical" or "codepoint"?
Note: I'm aware that the term "case sensitive" is already used and linked widely, not only in HTML but also in many attendant specs that refer to the definition provided by HTML.
The text was updated successfully, but these errors were encountered: