-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Bugfix Panose on "Nerd Font" variants #1099
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
Conversation
[why] query_monospace is newer. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why] Some fonts have invalid (or unset) Panose flags. When we create a "Nerd Font Mono" font the Panose proportion is set to 'monospace'. This make the font selectable in certain applications that need monospaced fonts. After #764 the "Nerd Font" variant shall (again) be detected as monospaced font, but the glyphs have a big right side bearing (hang into the next 'cell'). So we need to set the Panose bits there also. [how] We already have a check if the font is propably monospaced, independent from Panose. This is used to prevent --mono patching on originally proportional fonts. If we find out with that check that the font is (most probably) monospaced we also set the appropriate bits in Panose; unless Panose has valid values that contradict that change. Fixes: #1098 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
All Panose related messagesRunning on all fonts in HermitBold and light not monospaced? iA WriterPanose only partially filled OpenDyslexicPanose only partially filled MononokiPanose empty ProggyCleanPanose only partially filled RobotoMonoPanose empty ProFontPanose only partially filled DaddyTimeMonoPanose only partially filled LektonPanose proportion unset / strange MonofurOnly Italic has unset proportion?! FiraCodePanose empty CascadiaCodePanose empty (issue raised at their repo) GohuOne style has different proportion in Panose InconsolataPanose empty LilexPanose empty VictorMonoPanose only partially set OverpassPanose only partially set |
[why] Forgot to push these changes to the PR #1099. They are just 'more output'. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why] Forgot to push these changes to the PR ryanoasis#1099. They are just 'more output'. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
…ndard-variant Bugfix Panose on "Nerd Font" variants
[why] Forgot to push these changes to the PR ryanoasis#1099. They are just 'more output'. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Description
[why]
Some fonts have invalid (or unset) Panose flags. When we create a
Nerd Font Monofont the Panose proportion is set tomonospace. Thismake the font selectable in certain applications that need monospaced
fonts.
After #764 the
Nerd Fontvariant (withoutMono) shall (again) be detected asmonospaced font, but the glyphs have a big right side bearing (hang into
the next 'cell'). So we need to set the Panose bits there also.
[how]
We already have a check if the font is probably monospaced, independent
from Panose. This is used to prevent
--monopatching on originallyproportional fonts.
If we find out with that check that the font is (most probably)
monospaced we also set the appropriate bits in Panose; unless Panose has
valid values that contradict that change.
Fixes: #1098
Requirements / Checklist
What does this Pull Request (PR) do?
How should this be manually tested?
Install
CaskaydiaCove Nerd Font Complete.ttfon Windows and try to select it inWindows Terminal(without 'all fonts').Any background context you can provide?
What are the relevant tickets (if any)?
Screenshots (if appropriate or helpful)