Earlier quoted context omitted.
I think that you are missing the point. A standard must not dictate which symbols should be used, if it is a straight arrow, curved arrow, or a dotted one. Its purpose is to allow all kinds of symbols, positioning and denoting of relationships so that all symbols, relationships and positioning could be reproduced from the consumer of the data, be it a browser or a screen reader.
I think that you are missing the point. The set of all kinds of symbols is more expressive than you are prepared to codify.
MathJax
41–44 of 44 posts
Re: MathJax
#42Earlier quoted context omitted.
I think that you are missing the point. The set of all kinds of symbols is more expressive than you are prepared to codify.
Well, you don't do it. I'm not asking it from you and we are all good. Not sure that we can go anywhere otherwise.
Re: MathJax
#43Earlier quoted context omitted.
Well, you don't do it. I'm not asking it from you and we are all good. Not sure that we can go anywhere otherwise.
You still don't get it. It is all I do. Detractors amass.
Re: MathJax
#44Earlier quoted context omitted.
You still don't get it. It is all I do. Detractors amass.
What you do might be nice, but it does not scale. People do not include stuff for accessibility's sake. Web is the ultimate proof of that. That's why I prefer if accessibility is included in the workflow itself.