Package Details: ttf-raleway 20160215-3

Git Clone URL: (read-only, click to copy)
Package Base: ttf-raleway
Description: An elegant sans-serif font, designed in a single thin weight.
Upstream URL:
Keywords: font league moveable type
Licenses: custom:OFL
Groups: lmt-fonts
Conflicts: otf-raleway
Submitter: eeva
Maintainer: lightdot
Last Packager: lightdot
Votes: 14
Popularity: 0.000237
First Submitted: 2016-02-15 00:23
Last Updated: 2018-08-07 21:10

Latest Comments

caleb commented on 2020-03-12 16:36

@lightdot A long time ago you added me as a co-maintainer on a lot of the league font packages. I'm working on some more font package cleanup across the AUR and would like to address this one too (obsolete dependencies, split OTF vs TTF packages, etc.). Would you mind adding me?

lightdot commented on 2018-03-06 04:32

The Arch font packaging guidelines seem to be few and far between.

Most of the lmt-fonts packages have had both OTF and TTF variants included by the original packager, although the package name suggest only the latter. Perhaps they should have been named lmt-fonts-raleway, etc. in the first place... or broken up into two packages? I'm open to suggestions on how to handle this, I'd just prefer to have all League of Moveable Type font packages behave the same.

The 18 variant version of the Raleway available on the FontSquirrel seems to come from the fork made by Pablo Impallari. His version has already been packaged as otf-impallari-raleway-family and ttf-impallari-raleway-family in AUR. In any case, I'd prefer not to stray from the original upstream source, as I can't judge what are their reasons for not updating the font in their repo...

caleb commented on 2018-02-24 11:00

The Github project is 8 years out of date, there have been 18 variants in this family for ages. Until The League gets their act together on Github this should package some other release, for example the download from FontSquirrel.

caleb commented on 2018-02-24 08:13

Do you know where any Arch font packgaging guidelines talk about including both OTF & TTF forms in the same packgae or not? And also package naming guidelines. I'm wondering if either OTF should be dropped from this package or whether I should drop the OTF package entirely.