Bug#962478: [Pkg-fonts-devel] Bug#962478: Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Am 2020-06-09 14:42, schrieb Fabian Greffrath: Looks like we don't have gftools in Debian, sigh... Apparently this boils down to a single python script importing fonttools which I could just integrate into the Debian package, so chances are good I'll switch to upstream's own TTF build chain with a later package revision: https://github.com/googlefonts/gftools/blob/master/bin/gftools-fix-dsig.py - Fabian
Bug#962478: [Pkg-fonts-devel] Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Am 2020-06-08 22:08, schrieb Fabian Greffrath: sounds reasonable, I'll consider it for the next revision. I hope we have all the pre-requisites for building the TTF variants in Debian, their build chain contains some more steps than the one for the OTF variants. Looks like we don't have gftools in Debian, sigh... - Fabian
Bug#962478: [Pkg-fonts-devel] Bug#962478: Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Am 2020-06-09 04:20, schrieb Paul Wise: Pango/HarfBuzz is dropping support for low-res displays and hinting so I'm not sure how useful this is. fonts-firacode upstream has already dropped the build scripts for the OTF variant (not that we have used them, but whatever), so we should probably follow suit anyway. - Fabian
Bug#962478: [Pkg-fonts-devel] Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
On Tue, 9 Jun 2020 02:20:04 + Paul Wise wrote: > On Mon, Jun 8, 2020 at 3:03 PM Salim B wrote: > > > The FiraCode author explicitly states[1]: > > > > > I think at some point OTF was superior to TTF, but now they are mostly the same. The difference between OTF and TTF is that TTF can embed hinting instructions, which are essential for rendering on low-res displays. > > > > Therefore I think it would *really* make sense to switch to the TTF variant of the font since it's mainly intended for "on-screen" usage anyway (in contrast to print) and thus sharp rendering is very important. > > Pango/HarfBuzz is dropping support for low-res displays and hinting so > I'm not sure how useful this is. > > https://lwn.net/Articles/821016/ > https://www.phoronix.com/scan.php?page=news_item=HarfBuzz-Hinting-Woe > https://gitlab.gnome.org/GNOME/pango/issues/463 > https://github.com/harfbuzz/harfbuzz/issues/2394 > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise > > This issue applies for 1080-1440p screens too.
Bug#962478: [Pkg-fonts-devel] Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
On Mon, Jun 8, 2020 at 3:03 PM Salim B wrote: > The FiraCode author explicitly states[1]: > > > I think at some point OTF was superior to TTF, but now they are mostly the > > same. The difference between OTF and TTF is that TTF can embed hinting > > instructions, which are essential for rendering on low-res displays. > > Therefore I think it would *really* make sense to switch to the TTF variant > of the font since it's mainly intended for "on-screen" usage anyway (in > contrast to print) and thus sharp rendering is very important. Pango/HarfBuzz is dropping support for low-res displays and hinting so I'm not sure how useful this is. https://lwn.net/Articles/821016/ https://www.phoronix.com/scan.php?page=news_item=HarfBuzz-Hinting-Woe https://gitlab.gnome.org/GNOME/pango/issues/463 https://github.com/harfbuzz/harfbuzz/issues/2394 -- bye, pabs https://wiki.debian.org/PaulWise
Bug#962478: [Pkg-fonts-devel] Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Hi Salim, Am Montag, den 08.06.2020, 17:01 +0200 schrieb Salim B: > Therefore I think it would *really* make sense to switch to the TTF > variant of the font since it's mainly intended for "on-screen" usage > anyway (in contrast to print) and thus sharp rendering is very > important. sounds reasonable, I'll consider it for the next revision. I hope we have all the pre-requisites for building the TTF variants in Debian, their build chain contains some more steps than the one for the OTF variants. Cheers, - Fabian signature.asc Description: This is a digitally signed message part
Bug#962478: fonts-firacode: Provide TTF instead of OTF font files. The former embed hinting instructions and thus are rendered sharper on (low-res) screens.
Package: fonts-firacode Version: 2+dfsg1-1 Severity: important Dear Maintainer, More information about this issue can be found in the official FiraCode bug tracker: https://github.com/tonsky/FiraCode/issues/939 The FiraCode author explicitly states[1]: > I think at some point OTF was superior to TTF, but now they are mostly the > same. The difference between OTF and TTF is that TTF can embed hinting > instructions, which are essential for rendering on low-res displays. Therefore I think it would *really* make sense to switch to the TTF variant of the font since it's mainly intended for "on-screen" usage anyway (in contrast to print) and thus sharp rendering is very important. Kind regards, Salim Brüggemann [1]: https://github.com/tonsky/FiraCode/issues/939#issuecomment-640665878 -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-33-generic (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
