Closed Tarobish closed 8 years ago
Why would you kern these in the first place? I'm just using the kerning data as provided by you. "Ignore these" is hard, if possible (with a reasonable amount of work) at all after they have been kerned.
Well, there is a " ignore position
Here is the Problem please check the picture, "Adobe Arabic” compare to “Katibeh” Normally “reh-Alef” it has to be kern like the one in the left side but when “Alef” has marks below it would be colliding they solved this problem by moving marks below “Reh” when they are neighbor “Alef” with the marks below has a different spacing when its alone
On Feb 4, 2016, at 11:08 AM, Lasse Fister notifications@github.com wrote:
Well, there is a " ignore position (, )*;" keyword, so it is possible, however, I need to inject this into the kernFeatureGenerator at the right occasion. That kind of sucks, ufo-kerning is not made for this kind of thing :-(
— Reply to this email directly or view it on GitHub https://github.com/Tarobish/Katibeh/issues/80#issuecomment-180005021.
pic is missing
Maybe you can't send the images as attachment of a mail reply.
Maybe its better to do the same :)
Maybe its better to do the same :)
What do you mean? What is "the same"?
Like the Adobe Arabic, moving marks to the bottom Please compare the position of marks "Alef" with marks below, after "Reh" compare to the "Alef" which is alone
Yeah, I like that. I will try it. It's at this point probably better than ignoring the kerning, because I can apply it after the original kerning, so I don't have to mess around with your kerning data. Also, it may look better.
Awesome :)
I made some testing tables to check what we are talking about:
The third one 80.03 is the worst, the others are not so bad actually.
it seems some ligatures and connection did not generated in the table. would please check them out like uniFD0E, uniFD2A it you could that would be great . then ill let you know which characters are usable to fix them and get rid of the rest
Based on the generated test pages we are fine from issues #80.01 and #80.02 lets fix #80.03 but please generate them all :) thanks
seems some ligatures and connection did not generated in the table. would please check them out like uniFD0E, uniFD2A it you could that would be great . then ill let you know which characters are usable to fix them and get rid of the rest
The first two lines in 80.03 are FD0E the third and the fourth line are uniFD2A
You are right but it dint general them all like شر or سر or شز or سژ actually we don’t have these ligature with Persian and Arabic's form here! and they are the most that we want
On Feb 11, 2016, at 11:22 AM, Lasse Fister notifications@github.com wrote:
seems some ligatures and connection did not generated in the table. would please check them out like uniFD0E, uniFD2A it you could that would be great . then ill let you know which characters are usable to fix them and get rid of the rest
The first two lines in 80.03 are FD0E the third and the fourth line are uniFD2A
https://cloud.githubusercontent.com/assets/393132/12987604/16d7fe94-d0fd-11e5-9a86-37f1c504a30a.png — Reply to this email directly or view it on GitHub https://github.com/Tarobish/Katibeh/issues/80#issuecomment-183020063.
I can add these for you and remove the others?
Please! do you want me to write them all?
On Feb 11, 2016, at 11:51 AM, Lasse Fister notifications@github.com wrote:
I can add these for you and remove the others?
— Reply to this email directly or view it on GitHub https://github.com/Tarobish/Katibeh/issues/80#issuecomment-183035198.
how many are there?
in like 20 or 30
On Feb 11, 2016, at 11:55 AM, Lasse Fister notifications@github.com wrote:
how many are there?
— Reply to this email directly or view it on GitHub https://github.com/Tarobish/Katibeh/issues/80#issuecomment-183036263.
actually I think only the variation in the second part matters. Plus if there are any marks below that can be added.
ok, please lets try these i think we will be fine را - زا - ژا سرا - سزا - سژا - شرا - شزا - شژا صرا - صزا - صژا - ضرا - ضزا - ضژا برا - ترا - ثرا - پرا - یرا بزا - تزا - ثزا - پزا - یزا بژا - تژا - ثژا - پژا - یژا also these character when the ligature or characters are in meddle form like ببرا (last three characters) or بصرا (last three) the rest doesn't matter
I'll do
Great!
It's all added at the top of the 80.03 table
Thanks
There you go :)
The red dots are the cases that must work and the rest are "fantasy combinations" or at least very uncommon?
Yes, the res dots are the case the rest "fantasy combinations" and very uncommon in many cases :)))
the point is vowels are really common in the Arabic, but in arabic language we just have these character ر - ز - س - ش - ص - ض also sometimes in Persian which has them all plus ژ
(No, github won't place images into issue comments that come in as mail attachements)
Off-topic, but that “serif” at end of ر is pretty weird, and not so good looking IMHO.
@Tarobish Check it out. All your requested cases work now.
uniFE8E uniFE82 uniFE8E.short + "uni066E0649" if AlefFina has mark's below "uni066E06BA" if AlefFina has mark's below
uni0627 uni0627.short + "uni066E0649" if AlefFina has mark's below "uni066E06BA" if AlefFina has mark's below "uni066E0631" if AlefFina has mark's below
uniFD0E uniFD2A uni066E0631 uni066E0631.fina uniFD0F uniFD2B uniFEAE uni0631 uni0694.fina uni0694 uni0693.fina uni0693 uni0692.fina uni0692 uniFB8D uni0691 uniFEB0 uni0632 uni06EF.fina uni06EF uni0699.fina uni0699 uniFB8B uni0698 uni0697.fina uni0697 uni0696.fina uni0696 uni0695.fina uniFC5C uni0771.fina uni0771 uni076C.fina uni076C uni076B.fina uni076B uni075B.fina uni075B + "uni0627" and "uni0627.short" if AlefIso has mark's below