[Pkg-fonts-devel] Cantarel font

Nicolas Spalinger nicolas_spalinger at sil.org
Mon Mar 14 12:55:40 UTC 2011

On 07/03/11 17:01, Fabian Greffrath wrote:
> Am 07.03.2011 16:20, schrieb Nicolas Spalinger:
>> My point was to recommend pinging them and asking to make their build
>> system usable by packagers instead of us forking it or grafting
>> something else on top (even from a different project) they may not use
>> themselves, which really boils down to maintaining the delta which is
>> non-trivial.
> I have asked upstream to provide a rule to rebuild the font files, see:
> <https://bugzilla.gnome.org/show_bug.cgi?id=644126>

Great, thanks for reporting this (and other bugs) upstream.

>> Well, apart from gently and respectfully nudging the authors and
>> maintainers, maybe sending patches so that the font source tree comes
>> closer to the general community recommendation of our
>> foo-open-font-sources VCS template?
> Sorry, I am really unable to follow you on this... :/

Sorry for being unclear, I was trying to point out that git master of
Cantarell as hosted by GNOME is rather different from our general
foo-open-font-sources VCS template (see the folder in our own
repository, this is the result of discussions and feedback across the
open font community on how to best structure a open font VCS tree. It
can always be adjusted/improved but it provides a good starting point).

I'd recommend that, to make the work of contributors and package
maintainers easier across distros/platforms, upstream should consider
organising font sources along the lines of:

	FONTLOG.txt  (renamed from NEWS)
- developer-documentation/design-guide.txt
- documentation/
- sources/*.sfd  (AFAICT the Oblique, Bold Oblique and Spiro-Regular
fontforge sources which are on the Google webfont repository are not in
the GNOME repository: should they be? Has there been a merge or are we
missing some important source files including the resulting .otf in the
parent folder?)
- tools/*.pl (various build scripts, whose authors should also be
credited in the FONTLOG)
- web/	

I'd say that the fontconfig configuration files can probably go into
sources/ or maybe tools/ (as they are platform-specific and we probably
don't want a top-level folder for every type of config file) but it's up
to upstream and to you as packager to see. I guess the answers to  GNOME
#644187 will help.

Having prominent open font projects follow best practises will be
helpful for many other "smaller" projects.



Nicolas Spalinger,
SIL NRSI volunteer - http://scripts.sil.org
Debian fonts task force -  http://pkg-fonts.alioth.debian.org
Open font community - http://planet.open-fonts.org

More information about the Pkg-fonts-devel mailing list