back to anchors

[NinnaD]

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.

[NinnaD]

The anchor must be the same for it to work in mark attachment lookups.

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.)

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.

[Erwin Denissen]

Something seems to fail. I will get back to you soon.

[NinnaD]

Another manifestation of weirdness: I tried adding anchor-based composites one by one, just in case:
1. agrave, aacute went OK:

ccaa_1.png (9.03 KiB) Viewed 2036 times

2. acircumflex went OK, but...

ccaa_2.png (9.29 KiB) Viewed 2036 times

3. adding atilde modified acircumflex:

ccaa_3.png (8.44 KiB) Viewed 2036 times

And so it continues with each new addition, then aring results in:

ccaa_4.png (9.49 KiB) Viewed 2036 times

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.

[Erwin Denissen]

Here is a new release which should solve the problem.

FontCreator 14.0.0.2839 (64-bit)

Let me know your results.

[NinnaD]

Yes, seems to work like a charm! Thanks a bunch!

[NinnaD]

Well, there appears to be a further issue. When I use a formula:

Code: Select all

a+ogonekabovecomb

(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?

[Erwin Denissen]

Can you send the font project file to us?

[Erwin Denissen]

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".

[NinnaD]

And I've just tested it - and it's the paren_T anchor that's used. Compare:

1. default settings for base and mark

default_anchor_base.png (21.25 KiB) Viewed 1976 times

default_anchor_mark.png (11.3 KiB) Viewed 1976 times

2. modified settings for base and mark (paren_t anchor)

paren_T_anchor_base.png (21.29 KiB) Viewed 1976 times

paren_T_anchor_mark.png (11.33 KiB) Viewed 1976 times

3. modified settings for base and mark (ogonek_t anchor)

ogonek_T_anchor_base.png (21.23 KiB) Viewed 1976 times

ogonek_T_anchor_mark.png (11.28 KiB) Viewed 1976 times

So, what now?

[Erwin Denissen]

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".

I was looking at aogonek while your issue is related to acurlhook...

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?

[NinnaD]

Auto Attach is not taking into account OpenType layout features

It's the same with Auto Attach disabled.

How do you think we could find a solution to this, having two anchors for both base and mark?

I really couldn't say - without looking at the code behind it.

[NinnaD]

How do you think we could find a solution to this, having two anchors for both base and mark?

Though it must be possible, cf. FontForge:

fontforge.png (49.69 KiB) Viewed 1962 times

[Erwin Denissen]

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.

[NinnaD]

OK.

Auto Attach is not taking into account OpenType layout features

Would it be possible to have an option for anchor-based composites to use OT features?