back to anchors
Re: back to anchors
Please forget about this for now.
The underlying issue is getting curioser and curioser. I've now tried to replicate the problem I experienced in my font in the file you provided, and it seems I've succeeded, and then some. I'm trying to make sense of it and failing, so here are 2 font files with glyphs tagged "Review". This time I've been unable to delete anchors from agrave-abrevehookabove, even after making them simple and empty. Also, every time I do that and then select Complete Composites > Anchor Based and AutoAttach > Enable, the marks migrate higher and higher and shift more to the right.
Maybe you can diagnose what's going on.
The underlying issue is getting curioser and curioser. I've now tried to replicate the problem I experienced in my font in the file you provided, and it seems I've succeeded, and then some. I'm trying to make sense of it and failing, so here are 2 font files with glyphs tagged "Review". This time I've been unable to delete anchors from agrave-abrevehookabove, even after making them simple and empty. Also, every time I do that and then select Complete Composites > Anchor Based and AutoAttach > Enable, the marks migrate higher and higher and shift more to the right.
Maybe you can diagnose what's going on.
- Attachments
-
- Verajja Var v1.04.fcp
- (640.29 KiB) Downloaded 108 times
-
- Verajja Var v1.03.fcp
- (640.28 KiB) Downloaded 112 times
Re: back to anchors
Yes, and that makes perfect sense. What didn't make sense was that in order for the lookup using "top" anchor to position breve on a, I had to add "top_stacked" to a. Yes, breve had both "top" and "top_stacked" anchors, but that lookup used "top". ("top_stacked" was used by a different lookup for stacking diacritics, not for placing breve on a.)The anchor must be the same for it to work in mark attachment lookups.
But if you look at my two most recent posts, there seems to be something else going on there and maybe with the help of files I attached you'll be able to figure it out.
i appreciate the solution you suggested and I wanted to avoid, but hopefully it won't be necessary.
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: back to anchors
Something seems to fail. I will get back to you soon.
Re: back to anchors
Another manifestation of weirdness: I tried adding anchor-based composites one by one, just in case:
1. agrave, aacute went OK: 2. acircumflex went OK, but... 3. adding atilde modified acircumflex: And so it continues with each new addition, then aring results in: which impacts the placement of all previous marks (grave & acute minutely, so it's hardly noticeable in the image)
I understand you're working on the problem, so this is just by way of maybe providing you with additional data.
1. agrave, aacute went OK: 2. acircumflex went OK, but... 3. adding atilde modified acircumflex: And so it continues with each new addition, then aring results in: which impacts the placement of all previous marks (grave & acute minutely, so it's hardly noticeable in the image)
I understand you're working on the problem, so this is just by way of maybe providing you with additional data.
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: back to anchors
Here is a new release which should solve the problem.
FontCreator 14.0.0.2839 (64-bit)
Let me know your results.
FontCreator 14.0.0.2839 (64-bit)
Let me know your results.
Re: back to anchors
Yes, seems to work like a charm! Thanks a bunch!
Re: back to anchors
Well, there appears to be a further issue. When I use a formula:
(which is supposed to attach ogonekabovecomb using "ogonek_T" anchor) the mark, judging by its position, is attached by a different anchor ("paren_T"). Yes, both anchors are present (on a as base, on ogonekabovecomb as mark) and MarkPositioning instructions are to use "ogonek_T" for ogonekabovecomb attachment to a. No, "paren_T" is never defined in connection with a - it's used for mkmk attachment.
Any ideas?
Code: Select all
a+ogonekabovecomb
Any ideas?
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: back to anchors
Can you send the font project file to us?
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: back to anchors
Thank you for sending the file. I have taken a look at aogonek and it uses the ogonek anchor. You will see it when you move the base anchor on the "a".
Re: back to anchors
And I've just tested it - and it's the paren_T anchor that's used. Compare:
1. default settings for base and mark 2. modified settings for base and mark (paren_t anchor) 3. modified settings for base and mark (ogonek_t anchor) So, what now?
1. default settings for base and mark 2. modified settings for base and mark (paren_t anchor) 3. modified settings for base and mark (ogonek_t anchor) So, what now?
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: back to anchors
I was looking at aogonek while your issue is related to acurlhook...Erwin Denissen wrote: ↑Thu May 26, 2022 10:54 pm Thank you for sending the file. I have taken a look at aogonek and it uses the ogonek anchor. You will see it when you move the base anchor on the "a".
Auto Attach is not taking into account OpenType layout features, so in this case it looks for the first match. How do you think we could find a solution to this, having two anchors for both base and mark?
Re: back to anchors
It's the same with Auto Attach disabled.Auto Attach is not taking into account OpenType layout features
I really couldn't say - without looking at the code behind it.How do you think we could find a solution to this, having two anchors for both base and mark?
Re: back to anchors
Though it must be possible, cf. FontForge:How do you think we could find a solution to this, having two anchors for both base and mark?
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: back to anchors
We will make some changes, so the next update of FontCreator will prefer common anchor names, thus ones that contain top, bottom, ogonek, etc over unknown names.
Re: back to anchors
OK.
Would it be possible to have an option for anchor-based composites to use OT features?Auto Attach is not taking into account OpenType layout features