-
Notifications
You must be signed in to change notification settings - Fork 5
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
F1DAB should be mapped to 200C9 #12
Comments
there are about ten glyphs in PUA that have their exact mapping in unicode standard. i ve calculated this months ago but not made a list, whose appearing would be fine. |
It would be helpful if you can provide a list.
Thanks.
… On Aug 1, 2022, at 8:52 AM, Hulenkius ***@***.***> wrote:
there are about ten glyphs in PUA that have their exact mapping in unicode standard. i ve calculated this months ago but not made a list, whose appearing would be fine.
—
Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN75JYUWMLHYESJNZTUVK4TVW7XDPANCNFSM55HGIDVQ>.
You are receiving this because you are subscribed to this thread.
|
nomfoundation
pushed a commit
that referenced
this issue
Aug 11, 2022
Fixed in 5.02, @guocuozuoduo please verify and close |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The character assigned to private use area F1DAB is identical to the Unicode character 200C9 𠃉,which is currently not included in the font.
![image](https://user-images.githubusercontent.com/32423716/182137463-991cc8bf-52b8-4a2e-8984-180009a839c4.png)
![image](https://user-images.githubusercontent.com/32423716/182137769-4733b37a-3a2d-46e2-b85d-f4b01b7ec7d3.png)
![image](https://user-images.githubusercontent.com/32423716/182137528-211ec53e-c122-407a-8883-0e24ff2f3969.png)
http://nomfoundation.org/common/nom_details.php?codepoint=f1dab
http://yedict.com/zscontent.asp?uni=200C9
(External Unicode character map showing the missing character)
The text was updated successfully, but these errors were encountered: