Closed Tarobish closed 8 years ago
What should happen where? I think I've seen this fail somewhere in http://tarobish.github.io/Katibeh/html/generated-pages.html as well. May need some investigation.
I think there is something wrong with the anchors. In the first image, if you don't like it like that it may be the anchor position. Or does it use the wrong anchor, then I have to decompose it differently.
In the second image it is similar: either the anchor is missing (you must solve that) or the decomposition uses a wrong mark for a non-existing anchor.
Can you please explain what you expect to see here and provide a live testing document.
It has to be something wrong with the decomposing. these two ligatures are using the same base and anchors, in the right one, dots position its wrong but the left one it works perfectly. same problem with the characters without ligatures. "jeem-ar.medi" its broken but "tcheh-ar.medi" its not and "jeem-ar.fina" it works but "tcheh-ar.fina" doesn't.
They have to be like these
Ok, I think the solution here is pretty straight forward:
We need xxx.center
marks for all marks that go to the center in the fina
glyphs of the HAH-as-Base family of glyphs.
And for the init and medi versions of uni062D (one dot in the center) I made the wrong decomposition to dotcenterar
where just the dot below should have been used.
I'll post a list of missing xxx.center
in a few minutes.
Thanks :)
All needed marks were already in the font. But some ligatures are missing center
anchors. You must do this:
A bit offtopic but for uni0696.fina
some other ligatures also need a center
anchor:
Just perfect
@Tarobish will you repair the ligatures?
I'm on it
For uni066E062D, the center anchor its right there but seems its not functioning as well as uniFC40,
uni066E0631, uni066E0631.fina, uniFD0E, uniFD0F and uniFD2B are looks good to me. didn't find anything, if we move ranchers a bit then it would be colliding in the small point sizes.
uni066E0631, uni066E0631.fina, uniFD0E, uniFD0F and uniFD2B are looks good to me. didn't find anything, if we move ranchers a bit then it would be colliding in the small point sizes.
In all tables it's just one column, where the second glyph is uni0696.fina:
See how the dot is at the top left? It's supposed to be more in the center, just as in uni0696.fina
That kind of displacement happens when there is no anchor to attach to.
Oh, and it needs a center anchor there.
Done :) both mirza and katibeh
For uni066E062D, the center anchor its right there but seems its not functioning as well as uniFC40,
Ok, I have a theory, please read carefully and pay attention:
For ligatures, we do mark2ligature attachment. There the computer must decide to which anchor of the ligature a mark belongs. I don't know how glyphs decides this. However, in the ufo I can see this:
Note that there are two anchors for top: top_1
and top_2
and two for the bottom: bottom_1
and bottom_2
Then there is just one center
anchor.
Also there is carret_1
which is the position where the cursor will be located within the ligature. 1 carret means the ligature is made of 2 parts, 2 carrets means the ligature is made out of 3 parts, and so on.
Within Glyphs, what are the names of the top
and bottom
anchors?
top
top
bottom
bottom
?top_1
top_2
bottom_1
bottom_2
? If it is like the first option, we need either two center
anchors. Maybe left and right of the carret.
If it is like the second option, what we need is center_2
and Maybe also center_1
I think the best implementation would be if just center_2
is enough. So please rename these anchors to center_2
Also it been added to uniFD2A, uniFD0E, uniFD2B and uniFD0F
probably, for all the ligatures where you just added it, we need to solve the anchor issue as well. Let's try to find the solution for uniFC40 first, so we can iterate faster.
its all top_1 top_2 bottom_1 bottom_2 and center_1
:+1:
So we want center_2
plz check it
I filed a bug report in the Glyphs Forum https://forum.glyphsapp.com/t/problems-getting-custom-ligature-anchors-to-work/3846
Ok, Looks allright now!
Dot's position its broken in "jeem-ar.medi" either in ligature or character positioning