-
Notifications
You must be signed in to change notification settings - Fork 15
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
Non-ascii alternative operator symbols #204
Comments
I’m also referencing #126, in which some suggestions and concerns on the extensions were discussed. @michaelhkay I share your concerns. It’s still a challenge on most keyboards to type in arbitrary Unicode characters, and we should avoid getting people to copy and paste single characters all the time. In addition, most operators are compact enough, so we don’t save much space by switching to single characters. Finally, @davidcarlisle indicated in |
Some concerns have been raised (in #126, among others) about offering Unicode symbols for mathematical operators in the specification. If no one is fond of keeping the symbols, we could…
|
Now that #460 was created, do we want to keep this open? |
#460 was closed, I’m closing this one as well. |
Appendix B.3 of the draft specification proposes that we provide non-ASCII synonyms for many of the operator symbols:
This issue is raised to enable discussion of this proposal.
I have to confess I'm going rather cool on the idea. Some of the proposed symbols are rather obscure, and they aren't always rendered very clearly on display; some can easily be confused with other symbols. It's going to take a lot of WG time to agree the details, and it will probably cause more usability problems than it solves.
I've always felt that it was high time for programming to break loose from ASCII, but there are probably good reasons it hasn't done so.
The fact that we have two sets of comparison operators (and that some of the symbols clash with XML reserved characters) doesn't help. Providing alternative ways of writing them can only add to the confusion.
I'm going to propose dropping this unless someone else wants to champion it.
The text was updated successfully, but these errors were encountered: