lookupFlags IgnoreMarksbut it didn't match at all. Using a MarkFilteringSet did match, but it didn't match the "a MARK b MARK c" case.
sub a MARK' lookup lu b c;
sub a MARK' lookup lu b c;But my real situation has a longer context and a lot more combinations, and although I have Python and I can make class-based lookups, it's just ugly so I'd rather not enumerate them all if there's a better way to do it.
sub a MARK' lookup lu b MARK c;
Comments
this is possible using microsoft VOLT.
You can choose the process marks filtering by Class
There is a diference between Class and Group in VOLT.
Sami
Would you mind making an example font for me?
http://www.sbl-site.org/Fonts/SBL_Hbrw.ttf
Yes, but no luck:
Now if we have a sequence with@below_dots
between the init and the medi, it does not match. (This makes sense, because we've told it to skip over anything that it's not a @below_dot, and so the dot after the init needs to match.) Enumerating the possibilities does work: If we put something other than@below_dots
in the mark filtering set, then the rule does not match at all because the@below_dots
have been skipped over.I consider Mark Attachment Class to be essentially obsolete for mark filtering purposes. Mark Attachment Classes have to be exclusive, i.e. the same mark cannot be included in more than one Mark Attachment Class, which makes them useless for lots of purposes. In recent projects, I have simply used Mark Filtering Sets for all ignore marks filtering groups, regardless of whether they are exclusive or not.
That's the sort of situation that can lead to adding duplicate glyphs under different names, so you can use GSUB to contextually set up distinct sets.