Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ttx_diff] Add basic support for mark2lig rules #792

Merged
merged 1 commit into from
May 9, 2024
Merged

Conversation

cmyr
Copy link
Member

@cmyr cmyr commented May 9, 2024

We weren't handling this at all. This implementation does not do some of the fancier stuff that we do for other mark attachment rules, since these lookups are less common and it seems much less likely that there will be overlapping lookups that apply rules to the same glyphs.

We weren't handling this at all. This implementation does not do some of
the fancier stuff that we do for other mark attachment rules, since
these lookups are less common and it seems much less likely that there
will be overlapping lookups that apply rules to the same glyphs.
Comment on lines +48 to +58
write!(f, "{base_name} (lig) [")?;
for (i, anchor) in self.base_anchors.iter().enumerate() {
if i != 0 {
write!(f, ", ")?;
}
match anchor {
Some(a) => write!(f, "{a}"),
None => write!(f, "<NULL>"),
}?
}
writeln!(f, "]")?;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks suspiciously likely to be a repetitive pattern, if it is perhaps we could share a fn?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we end up repeating it we can always refactor, but this is the last mark attachment rule so I don't anticipate that happening.

@cmyr cmyr added this pull request to the merge queue May 9, 2024
Merged via the queue into main with commit 3dd835e May 9, 2024
10 checks passed
@cmyr cmyr deleted the layout-norm-mark2liga branch May 9, 2024 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants