Skip to content
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

Open
fred-wang opened this issue Feb 14, 2019 · 10 comments
Open

Add rules to map from non-combining to combining accents #137

fred-wang opened this issue Feb 14, 2019 · 10 comments
Labels

Comments

@fred-wang
Copy link
Contributor

fred-wang commented Feb 14, 2019

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.

@davidcarlisle davidcarlisle transferred this issue from w3c/mathml-core Feb 20, 2019
@davidcarlisle davidcarlisle added enhancement New feature or request MathML Core labels Feb 20, 2019
@fred-wang
Copy link
Contributor Author

@fred-wang
Copy link
Contributor Author

However, I think the MathML Core text still has to be adjusted and refer to that table.

@davidcarlisle
Copy link
Collaborator

@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.

@fred-wang
Copy link
Contributor Author

@davidcarlisle where is the latest version of unicode.xml ; http://www.w3.org/2003/entities/2007xml/unicode.xml seems not up-to-date?

@fred-wang
Copy link
Contributor Author

@davidcarlisle
Copy link
Collaborator

davidcarlisle commented Jun 18, 2019 via email

@fred-wang
Copy link
Contributor Author

I think it would be good to have one "official" version to use/edit.

@davidcarlisle
Copy link
Collaborator

davidcarlisle commented Jun 18, 2019

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/

@fred-wang
Copy link
Contributor Author

For MathML Core, I think we only want non-combining => combining mapping.
And actually an ordered list of combining characters so that browsers can try them in a determined order.
I'll try to update the spec for that.

@fred-wang
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants