-
Notifications
You must be signed in to change notification settings - Fork 43
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
Old kern writer: register lookups under DFLT, too #844
Conversation
5d9ec42
to
b072905
Compare
54bbd2b
to
5f17e66
Compare
b072905
to
0d15b13
Compare
5f17e66
to
e36d9c1
Compare
@@ -694,6 +694,7 @@ def test_kern_LTR_and_RTL(self, FontClass): | |||
|
|||
feature kern { | |||
lookup kern_dflt; | |||
lookup kern_ltr; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm this looks suspicious..
the global languagesystems contain both LTR and RTL scripts in this particular test font (I see both latn and arab), if you register kern_ltr
in the top part of the feature block before any explicit script/language declarations then it will be registered for all the globally defined languagesystems, but do we actually want to register the kern_ltr
under arab
?! Probably not. I don't know if it is benign or just plain wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If kern_ltr
includes kerning between common characters (e.g. punctuation or digits) it would be wrong to register it for arab
, otherwise it should be redundant and tiny bit slow but otherwise harmless.
e36d9c1
to
27af8ea
Compare
This ports #787 to the old kern writer.
Contrary to the new writer, here we don't try to register languages for DFLT.