[Pkg-fonts-devel] Font packaging information

Paul Wise pabs at debian.org
Sat Oct 15 02:29:19 UTC 2016

On Fri, 2016-10-14 at 10:07 +0000, Mohammed Isam wrote:

> I am editing SFD files, from which I generate TTFs.
> This has been so far a manual process.

Sounds like Fabian has helped you sort that out.

> If you are the packager and I am the upstream, and (a) I gave you the
> SFDs, and (b) I provided you with a script to autogenerate TTFs from
> SFDs (or you devised such a script yourself, either way), is there
> still a problem in this scenario?.

Yes, due to the reserved font names and the OFL license we aren't
allowed to do any format shifting without renaming the font. The fixes
are to either remove the reserved font name or change the license.

If you could remove the reserved font names and release a new source
package containing only the SFD, the script to build, the OFL license,
README and any other documentation, then it can be packaged for Debian:


The TTF version of the font can continue to be released separately as
you are currently doing, for people who just want to download it.

Also, are you using a version control system like git to manage the
SFD? If not I'd encourage you to do so. If you are or start doing that,
it would be great if you could make that public so that people can send
patches. Something like savannah, gitlab, sourceforge or github would
work if you don't want to have to host it yourself.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20161015/fe2db6c2/attachment-0001.sig>

More information about the Pkg-fonts-devel mailing list