Go to file
2022-08-21 23:47:02 +00:00
_constraints Accepting request 575526 from home:coolo:branches:openSUSE:Factory 2018-02-12 10:00:45 +00:00
.gitattributes osc copypac from project:M17N:fonts package:google-cousine-fonts revision:1 2013-10-25 11:48:09 +00:00
.gitignore osc copypac from project:M17N:fonts package:google-cousine-fonts revision:1 2013-10-25 11:48:09 +00:00
generate-fonts-and-specfile.sh fix: summary and descriptions not mentioning font being Serif 2022-08-21 23:47:02 +00:00
google-noto-fonts.changes fix: summary and descriptions not mentioning font being Serif 2022-08-21 23:47:02 +00:00
google-noto-fonts.spec fix: summary and descriptions not mentioning font being Serif 2022-08-21 23:47:02 +00:00
google-noto-fonts.spec.in fix: summary and descriptions not mentioning font being Serif 2022-08-21 23:47:02 +00:00
LICENSE Accepting request 978146 from home:Pi-Cla:branches:M17N:fonts 2022-05-20 08:12:35 +00:00
README.FAQ fix: summary and descriptions not mentioning font being Serif 2022-08-21 23:47:02 +00:00
ttf.tar.gz fix: summary and descriptions not mentioning font being Serif 2022-08-21 23:47:02 +00:00

FAQ by Gordon Leung <pirateclip@protonmail.com>
Last reviewed: 2022-08-22

Q: Why are there so many Noto packages?
A: Each Noto Font family is individually packaged to allow the user to pick and
choose which font(s) they need. If we instead shoved them all into a single
package, then we would get situations such as KDE Plasma pulling in many MBs
worth of font files as KDE Plasma uses Noto Sans as their default font.

Q: Why do the packages take up so much space?
A: We currently package the most space inefficient font format provided by
Google which are Hinted TTFs. We have tried switching to more space efficient
formats such as Unhinted OTFs, but that made the fonts ugly on low dpi
monitors. If you or someone you know can help with transitioning us to a more
space efficient format please let me know.