-
Notifications
You must be signed in to change notification settings - Fork 37
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
Sync with 3.0.0. #92
Sync with 3.0.0. #92
Conversation
So as far as I can tell arabic tables and ucd tables are all covered by EDIT: Nevermind, seems like the corresponding Python file in harfbuzz is |
And it seems like we have |
Wow, you have put a lot of effort into it. Much appreciated!
Yes, we don't have such API.
Yes, unrelated.
Yes, we don't have those.
Yes, we use master branch already.
Afair, As for
|
Gotcha! |
We also have |
Ah, I guess we need to update the dependencies too, then. |
Should I submit PR to those (unicode-cc and unicode-bidi)? Or is it faster if you just do it when you have time? |
#[derive(Clone, Copy, PartialEq, Debug)]
pub enum JoiningType {
U = 0,
L = 1,
R = 2,
D = 3,
// We don't have C, like harfbuzz, because Rust doesn't allow duplicated enum variants.
GroupAlaph = 4,
GroupDalathRish = 5,
T = 7,
X = 8, // means: use general-category to choose between U or T.
} Why would adding C here make it duplicated? |
I will update my unicode crates soon.
Because Rust doesn't allow enums to have duplicate values. The C++ code is: enum hb_arabic_joining_type_t {
JOINING_TYPE_D = 3,
JOINING_TYPE_C = JOINING_TYPE_D,
} |
Right, so I always need to use D instead of C. |
Yep. |
Updated my |
Okay, just the emoji commit is missing now: harfbuzz/harfbuzz@35ac0de42 I'm unsure what to do with it though. They basically add this file: https://www.unicode.org/Public/emoji/latest/emoji-test.txt But it seems that this file doesn't contain any information on extended pictographics. But it seems we only use the file to generate that one method. Does this mean we can ignore this file? |
Yes, I think we can ignore that emoji change. It doesn't seems to affect us. The rule of thumb: if tests are passing - we're fine. |
I guess porting itself is not as hard as I thought, just time-consuming. But I will probably change my mind once I encounter my first not-passing test and spend hours with the debugger. 😄 |
Pretty much. |
This file is used to generate emoji test data (IIRC, to test that all emoji sequences are shaped as one cluster) |
My first attempt. let's see how it goes.
Legend:
🟢: Port of commit succeeded
⚪️: Commit is not relevant
🟡: I have uncertainties about that commit
🔴: Port of commit is failing
⚫️: Commit has not been ported yet.
Table: