-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add rules to map from non-combining to combining accents #137
Comments
However, I think the MathML Core text still has to be adjusted and refer to that table. |
@fred-wang yes in fact I had never really extracted or looked at that data from unicode.xml since adding it during the email discussion, so I just added more or less raw tables into that appendix. To be decided if it needs an appendix or should just be a table in the main body, also I am not sure we need to display the "reverse direction" table. But at least the raw data is now there. |
@davidcarlisle where is the latest version of unicode.xml ; http://www.w3.org/2003/entities/2007xml/unicode.xml seems not up-to-date? |
which is the same as the one in the W3C github at
https://github.com/w3c/xml-entities/
The one in W3C TR space is older
…On Tue, 18 Jun 2019 at 09:36, Frédéric Wang ***@***.***> wrote:
https://github.com/mathml-refresh/xml-entities I guess
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/mathml-refresh/mathml/issues/11?email_source=notifications&email_token=AAJVYATPWMPFWYSW7JADZWLP3CNAXA5CNFSM4GYYLC72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX5UFVY#issuecomment-503005911>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJVYARFMRAE42ARP5S2G3DP3CNAXANCNFSM4GYYLC7Q>
.
|
I think it would be good to have one "official" version to use/edit. |
Sure but it is same as mathml-full spec (and potentially core as well) we are using the mathml-refresh github as that gives full admin control and we can generate new repositories and give write access as required, but if we move to a REC track process (I think) we will need to move to a W3C organisation github, however I am assuming a workflow that doesn't edit on on the w3c repository we just periodically merge in changes from mathml-refresh So historically all edits to unicode.xml for several years have been at https://github.com/w3c/xml-entities/ but I think the current policy should be that edits happen in mathml-refresh (https://github.com/mathml-refresh/xml-entities ) and are then merged across to https://github.com/w3c/xml-entities/ |
For MathML Core, I think we only want non-combining => combining mapping. |
I had set https://mathml-refresh.github.io/mathml-core/#combining-character-equivalences to "non-normative" ; we should defer the details for accents to a next version of core. |
Original thread: https://lists.w3.org/Archives/Public/www-math/2018Mar/0001.html
Also from the MathML in HTML5 note tracker: https://gitlab.com/mathml/MathMLinHTML5/issues/33
I think such a rule should be in MathML Core.
The text was updated successfully, but these errors were encountered: