You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that Neovide does not enable aalt, and the font does not have it enabled by default either. Still Swash thinks it's enabled, until we explicitly disable it with -aalt
One of my theories is that the support for font features with TrueType fonts is a bit broken, since we have not seen any similar reports for any other fonts. But that's just a guess. and I decided not to debug it further for the moment, since the font is not free.
Do you have any ideas what could cause it?
The text was updated successfully, but these errors were encountered:
Per @fredizzimo 's request, I attach the testing code I did some time ago using swash_demo:
I added the following near the end of main.rs, right before db.build()
db.enter_span(&[S::family_list("PragmataPro Mono Liga"),S::Weight(Weight::BOLD)]);
db.add_text("\n\nDoes this BOLDING work?");
db.leave_span();
db.enter_span(&[S::family_list("PragmataPro Mono Liga"),S::Style(Style::Italic)]);
db.add_text("\n\nDoes this Italic work?");
db.leave_span();
The result is this:
Oddly enough, when I use the non-Liga version (using the font family "PragmataPro Mono" instead), the fonts renders fine. Same results for non-Mono versions: Liga = problem, non-Liga = good.
It doesn't completely match the behavior in neovide though. In neovide, every combination of (non-)Mono/(non-)Liga seems to be rendered wrong.
I use the latest release of PragmataPro (0.830 I think).
For the full context check this Neovide issue
But in short, the font PragmataPro Mono enables these features when
aalt
is enabled, and that combination looks exactly like the screenshot provided.The issue is that Neovide does not enable
aalt
, and the font does not have it enabled by default either. Still Swash thinks it's enabled, until we explicitly disable it with-aalt
One of my theories is that the support for font features with TrueType fonts is a bit broken, since we have not seen any similar reports for any other fonts. But that's just a guess. and I decided not to debug it further for the moment, since the font is not free.
Do you have any ideas what could cause it?
The text was updated successfully, but these errors were encountered: