-
Notifications
You must be signed in to change notification settings - Fork 19
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
New entries in the operator dictionary for U+1EEF0 and U+1EEF1 #6
Comments
@fred-wang how can we figure out if it was fixed? To be completely honest, I do not understand how a change in the MathML standard would affect this matter. |
@physikerwelt it looks like at the time
although there is some discussion in the email thread about whether it should also have spacing added, That entry in unicode.xml should mean the entry appears in appendix C but it appears not, I'll check the build this evening. If we want the core to be a self standing spec I guess the operator dictionary should be in the core spec as well. |
The build of the mathml4 spec was using an older copy of unicode.xml that was fixed with commit These character now appear in the table as the first entries in https://mathml-refresh.github.io/mathml/appendixc.html#oper-dict.entries-table |
Yes, we need to move this and several other things (like embellished op, mathml length...) into the core and remove quotations of MathML 3. This is another TODO. |
I think this is essentially fixed now. Thanks David! |
Agreement that this is dealt with |
Fixed in WebKit: https://bugs.webkit.org/show_bug.cgi?id=153984 |
Resolution: Specification: Implementation: Polyfill: Tests: |
Reopening since we need tests |
I started to add tests for Operator Dictionary entries in web-platform-tests/wpt#19123 I realize that it lacks explicit values for priority (which does not matter for layout), lspace and rspace. For the first character, I guess we want something similar to other n-ary sum? As said on the mailing list, the spacing is the default i.e. 0.2777777777777778em (aka "thickmathspace" in full) which is probably too big. I don't really have strong preference about the values, but I'd like at least to have explicit lspace and rspace values unless 0.2777777777777778em is intentional. @davidcarlisle Can you please take care of that and make a proposal for the next MathML CG meeting? |
yes I will look, Also @khaledhosny may be able to have a more informed opinion on the spacing requirements for these two characters, Khaled any suggestions welcome:-) |
@davidcarlisle After writing tests for the operator dictionary, I notice all browsers fail the accent test for the following operators:
I can't find these entries in Gecko/WebKit. Do you know if that's something that was added recently? |
@fred-wang " (U+00222) U+00AA U+201b all have entries in the MathML3 spec operator dictionary with an |
@davidcarlisle Thanks I can see them in https://www.w3.org/TR/2014/PER-MathML3-20140211/appendixc.html but not in https://www.w3.org/TR/2010/REC-MathML3-20101021/appendixc.html So I guess browsers need to be updated |
@fred-wang but on the other hand are the ordinal signs and quote marks really used as accents, seems a bit odd. I guess it was me that edited this info into unicode.xml but there must have been a bug report or something I'll see if I can find any record. The old CVS log entry says that the opertaor dictionary entries were added for all the primes etc listed in https://www.w3.org/TR/MathML3/chapter7.html#chars.pseudo-scripts but I'm not sure that this really means that the characters should have the accent property set to true? |
@davidcarlisle IIRC, one idea is that all operators used as scripts would have "postscript" form. I'm not sure the accent property is needed, it's only supposed to be for overscript. (BTW regarding pseudo-script, this is a property that is supposed to be controlled at the font-level, not dictionary one. See w3c/mathml-core#135 ) |
Hmm, Unicode says for 201B: "has same semantic as [2018 -- char didn't render] but differs in appearance". Given that, it is strange that the operator dictionary entries aren't the same. Seems like a bug. |
Neil, are you talking about these two? These are different in appearance, also we have no entry for 2018 here (but have one for 201B): |
Nm, you probably were talking about the MathML 3 appendix C. |
Yes, that's correct about appendix C. In https://mathml-refresh.github.io/mathml-core/, both are mentioned:
|
I have no idea either. I guess they should be spaced like similar operators. |
I wrote:
Some integrals use 0 and 1, however, n-ary sum/product and other large operators use: lspace=1, rspace=2 ; so I'm proposing to do that instead. The operators are also in https://mathml-refresh.github.io/mathml-core/#stretchy-operator-axis. Then I would keep the remaining property as it, until someone complains. |
I opened #151 for this separate issue. |
I'm closing this. These operators are handled. It seems nobody has an idea of a correct spacing, so using existing category is fine. |
I don't know if that was fixed but just to move issue here:
https://lists.w3.org/Archives/Public/www-math/2016Aug/0014.html
The text was updated successfully, but these errors were encountered: