Hi
I use contextual anchor in behDotless-ar.init
contextual anchor used when the letter reh-ar placed before beh-ar.init
It works properly.
But I want to ignore space or a comma between these two.
Is it possible?
Can I add a group for ignore in anchor context box?
and also Ignore marks
when I type [reh-ar kasra-ar beh-ar.init] contextual anchor not work.
How can I use IgnoreMarks;
@GeorgSeifert @mekkablue
You first question requires two different contexts. That is not supported, yet.
It would need:
[@Re @Ve]
[space, comma] [@Re @Ve]
for your second question. You can add lookup flags before the context, delimiting it with a ;.
lookupflag IgnoreMarks; [@Re @Ve]
Hi @GeorgSeifert
Thank you for responding
I think this part is very needed
I hope it will be updated soon
I tried, it doesn’t work
What version of Glyphs do you have (the four digit number)? The lookup flag support was added in 3.2.
I have 3.2
Does the anchor work if there are no marks in the string?
When I add
lookupflag IgnoreMarks; [@Re @Ve]
Nothing work
If I add class (one or more), anchor works
Hi @GeorgSeifert
Still, Ignore marks not working, Did you work on it?
Also contextual anchor like *bottom_1 are not working
I think Ignore marks and contextual anchor like *bottom_1 are very important
Both not working
What do you have written in the context and what do you intend?
Hi
First
not working
Also, creating a list of glyphs to ignore would be great.
Second
In ligature (Arabic script) *bottom_1 or like this not working
How can I use contextual anchor in ligature?
Ligature anchors do not support context, yet. It is much more complicated ;(.
I have 2 contextual anchors in 2 masters
*bottom
*bottom.re
If in one master, these 2 contextual anchors have the same position, then *bottom.re will ignored
Any Update?
This is a bug, don’t forget it.
That will not be fixed as the current system can’t handle it. Please move one of the anchors by one unit.