Bahman Eslami

That would be very useful. As I mentioned in a fontParts [issue](https://github.com/robotools/fontParts/issues/245#issue-312272374), having an anchor lib also would be nice to add other information like context of mark positioning. This...

> As explained in the issue you reference, adding lib to anchor is problematic, so please focus on solutions that don't require that. I will probably use this type property...

> Likewise for the type of a glyph? Only from this set: - base - ligature - mark - components https://docs.microsoft.com/en-us/typography/opentype/spec/gdef#glyph-class-definition-table-overview

(Just to be clear for anchor type) Anchor type can only be: - base - mark - entry - exit Base anchor can get an index attribute for the logical...

Actually in adobe fea file a ligature mark and base mark are defined differently. - Base: `pos base [behDotless-ar] mark @mark_bottom mark @mark_top;` - Ligature: `pos ligature [lam_alefWasla-ar.fina] mark @mark_bottom...

Current solution to prevent adding any property to anchor is having name conventions for anchors. The advantage of naming convention is that the intention of the anchor is visible. The...

> Suggestion: > Describe/document the Glyphs/fontmake behavior into more detail. It may then become easier to reason about the following: I will do that, thank you for pointing them out....

Could you give an example where there is a need for multiple lookups for cursive anchor?

> I have a font that has cursive anchors with RTL flag and without it, based on whether it wants the rightmost of the leftmost glyph to be the one...

This also adds the question, do we need a `RTL` property for anchors?