-
Notifications
You must be signed in to change notification settings - Fork 313
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
Compressed kerning with trailing backtick #3
Comments
I also have the same issue. |
The dead marks feature in the feature code should be removed. This is a bad practice and makes the font unusable for programming languages, markup languages and language orthographies that use those ASCII marks. |
I found a workaround. In short, you have to disable the Compare this to how it looks by default (incorrect): This also works fine in other software that lets you customize which OpenType features are active. One such example is kitty, a terminal emulator: Notice how the comment renders correctly. I stumbled across this by using the TTX tool from <Lookup index="18">
<LookupType value="1"/>
<LookupFlag value="0"/>
<!-- SubTableCount=1 -->
<SingleSubst index="0">
<Substitution in="acute" out="uni0301"/>
<Substitution in="breve" out="uni0306"/>
<Substitution in="caron" out="uni030C"/>
<Substitution in="cedilla" out="uni0327"/>
<Substitution in="circumflex" out="uni0302"/>
<Substitution in="dieresis" out="uni0308"/>
<Substitution in="dotaccent" out="uni0307"/>
<Substitution in="grave" out="uni0300"/>
<Substitution in="hungarumlaut" out="uni030B"/>
<Substitution in="macron" out="uni0304"/>
<Substitution in="ogonek" out="uni0328"/>
<Substitution in="ring" out="uni030A"/>
<Substitution in="tilde" out="uni0303"/>
<Substitution in="uni02CD" out="uni0331"/>
<Substitution in="uniA788" out="uni032D"/>
</SingleSubst>
</Lookup> As evident in the sample above, this behavior occurs not only for grave (`), but also for others such as dieresis (¨); it gets substituted with its combining form, merging it with the previous character (in certain scenarios). Is this supposed to simplify the insertion of accented characters in languages such as Catalan? I'm not sure. I'm also unsure as to what the intended fix is; I don't know much about professional font authoring and what the correct semantics are here, so I'll leave the proper fix to the designers. |
Addendum: the README says this (with added formatting, because the linebreaks don't render correctly on GitHub):
So this appears to be an intentional feature of the font, albeit misfiring. Surrounding a word with grave characters is fairly prevalent in Markdown, code, and technical prose in general, and it's incorrect to substitute the glyph with a combining one in these cases. Probably a bug. |
+1. The trailing backtick doesn't show up at all for me in neovim v0.9 |
Adding this line to
|
Should be fixed with the latest release (1.2.0) |
Verifying this is fixed in 1.2.0, thanks for the update! |
It would seem that text wrapped in backticks will have compressed kerning when the character is an alphabetic symbol. For example, this is how the following text is rendered:
The text was updated successfully, but these errors were encountered: