google-noto-fonts
No description set
- Developed at M17N:fonts
- Sources inherited from project openSUSE:Factory
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/google-noto-fonts && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
README.FAQ | 0000000812 812 Bytes | |
README.maintain | 0000001175 1.15 KB | |
_constraints | 0000000109 109 Bytes | |
generate-specfile.sh | 0000008965 8.75 KB | |
google-noto-fonts.changes | 0000012086 11.8 KB | |
google-noto-fonts.spec | 0000171190 167 KB | |
google-noto-fonts.spec.in | 0000002165 2.11 KB | |
notofonts.github.io-noto-monthly-release-24.5.1.ta |
1067574188 1020 MB |
Revision 30 (latest revision is 34)
Ana Guerrero (anag+factory)
accepted
request 1171083
from
Gordon Leung (Pi-Cla)
(revision 30)
- Update to 20240501 * Noto Rashi Hebrew - Corrects the width and position of marks under double-yud and double-vov - Improves the anchoring of yod - Adds the U+053F yod triangle character - Improves the spacing of tsadi * Noto Egyptian Hieroglyphs - Add codepoints from Unicode 14
Comments 4
Should this package be named as "noto-fonts"? Because all its sub-packages are prefiexed with noto- rather than google-noto-
Most font packages are prefixed with the name of the vendor/group/foundry. https://en.opensuse.org/openSUSE:Packaging_Fonts#Naming_and_Central_Font_Repository
If it should be prefixed with google-noto-, then all sub-packages should have the same prefix. It is a problem of inconsistent naming.
I would agree.