Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75062 - [ttf-nerd-fonts-symbols] Using Cascadia Code PL makes symbols smaller

Attached to Project: Community Packages
Opened by Gabriel Sirilan (siri) - Tuesday, 14 June 2022, 09:19 GMT
Last edited by Daniel M. Capella (polyzen) - Friday, 14 July 2023, 22:19 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Daniel M. Capella (polyzen)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:Using Cascadia Code PL makes symbols smaller

Additional info:
* Package version: 2.1.0+36+gd0bf73a1-
* 10-nerd-font-symbols.conf symlinked from /etc/fontconfig/conf.d/
* Cascadia {Code, Mono} PL NOT set as `monospace` font

The original variant of Cascadia Code/Mono do not contain Powerline symbols. Hence, it may be advisable to use the Cascadia {Code, Mono} PL variants. However, using the variants in conjunction with this package with ttf-iosevka-nerd installed results in the symbols being smaller than usual.

The ttf-iosevka-nerd package only contains the fonts and no fontconfig configuration files. However, removing ttf-iosevka-nerd results in the problem being fixed. This strongly suggests that font substitution quirks are responsible for this rendering error.

As detailed below, adding the Cascadia {Code, Mono} aliases to 10-nerd-font-symbols.conf fixes this problem.

Steps to reproduce:
0. Install ttf-nerd-fonts-symbols, ttf-cascadia-code, and ttf-iosevka-nerd
1. Use the Powerline variant of Cascadia (Cascadia {Code,Mono} PL) in your preferred terminal
2. Nerd font symbols become smaller

(Suggested) fixes:
0. Add Cascadia {Code, Mono} PL alias to 10-nerd-font-symbols.conf.
Tested fix in per-user configuration

1. Notify maintainer of ttf-iosevka-nerd of this problem. However effectiveness is doubted as 10-nerd-font-symbols.conf contains aliases for a large number of fonts, which indicates this affects all fonts that do not have an alias.
This task depends upon

Closed by  Daniel M. Capella (polyzen)
Friday, 14 July 2023, 22:19 GMT
Reason for closing:  No response
Comment by Gabriel Sirilan (siri) - Tuesday, 14 June 2022, 09:25 GMT
Diff file for the suggested fix.
Comment by Daniel M. Capella (polyzen) - Sunday, 19 June 2022, 04:43 GMT
`10-nerd-font-symbols.conf` presumably only covers patched fonts provided by Nerd Fonts. You might be better off rolling your own font configuration file, eg. https://gitlab.com/polyzen/dotfiles/-/blob/master/workstation/.config/fontconfig/fonts.conf.
Comment by Gabriel Sirilan (siri) - Sunday, 19 June 2022, 10:51 GMT
Cascadia Code is patched by Nerd Fonts. However, using Cascadia Code (original variant) yields an undesirable result in that the Powerline symbols do not display properly (independent of having `ttf-iosevka-nerd` installed). Switching to Cascadia Code PL fixes this issue, but the icons tend to be smaller (only with `ttf-iosevka-nerd`). The end result of using this package should be nearly (if not actually) identical to the third screenshot, which is the Nerd Fonts-provided CaskaydiaCove Nerd Font ( https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/CascadiaCode ).

On a high note, I had to contend with having ttf-iosevka-nerd installed because of the `ttf-nerd-font` dependency of one of my packages. With the new update this is not needed, so I can revert back to not having `ttf-iosevka-nerd` installed with this.

I am suggesting this as a workaround, since this should really work out of the box with `Cascadia Code` and with any other package installed. It may help though that the PL variant is officially provided by Microsoft ( https://github.com/microsoft/cascadia-code#font-variants ).
Comment by Daniel M. Capella (polyzen) - Thursday, 11 May 2023, 20:18 GMT
Is this still an issue?

Loading...