FS#77425 - Inconsistent font package naming?

Attached to Project: Community Packages
Opened by - (xiota) - Tuesday, 07 February 2023, 14:59 GMT
Last edited by Toolybird (Toolybird) - Thursday, 09 February 2023, 03:31 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Most fonts are named {ttf,otf}-fontname. However, there are several packages that are named fontname-fonts. Perhaps they should be renamed {ttf,otf,font}-fontname?

adobe-source-code-pro-fonts
adobe-source-sans-fonts
adobe-source-serif-fonts
cantarell-fonts
gnu-free-fonts
noto-fonts
tex-gyre-fonts
adobe-source-han-sans-cn-fonts
adobe-source-han-sans-hk-fonts
adobe-source-han-sans-jp-fonts
adobe-source-han-sans-kr-fonts
adobe-source-han-sans-otc-fonts
adobe-source-han-sans-tw-fonts
adobe-source-han-serif-cn-fonts
adobe-source-han-serif-hk-fonts
adobe-source-han-serif-jp-fonts
adobe-source-han-serif-kr-fonts
adobe-source-han-serif-otc-fonts
adobe-source-han-serif-tw-fonts
awesome-terminal-fonts
opendesktop-fonts
powerline-fonts
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 09 February 2023, 03:31 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See comments.
Comment by Toolybird (Toolybird) - Thursday, 09 February 2023, 03:31 GMT
Perhaps in an ideal world. But no, we don't have a documented font naming policy. Renaming that whole list would be a fair bit of work for very little gain, so not worth it IMHO.

PS. filing a bug against a list of pkgs usually doesn't go down well. Policy stuff happens on the Arch GitLab instance.

Loading...