[Pkg-fonts-devel] Bug#797627: ITP: fonts-hack -- Typeface designed for source code

Paride Legovini pl at ninthfloor.org
Thu Sep 10 19:55:48 UTC 2015


On 2015-09-07 08:15, Paul Wise wrote:
> On Mon, Sep 7, 2015 at 7:02 AM, Fabian Greffrath wrote:
>> Am Freitag, den 04.09.2015, 23:40 +0200 schrieb Paride Legovini:
>>> What do you think? What are more precisely the Debian requirements
>>> for the build process of its packages?
>>
>> I think we should approach this with pragmatism.
> 
> I think we should talk to upstreams and find out how they produce
> their fonts, then work with them to ensure they are using best
> practices; distributing their source materials in a VCS repository and
> offering automatic methods for creating binary font files from their
> source materials.

Dear Paul,

here is the developer's point on the build process:

https://github.com/chrissimpkins/Hack/issues/85#issuecomment-139083942

The builds are performed with FontLab Studio (OS X), but it should be
possible to build at least the ttf fonts with FontForge in an automated way.

I propose to start distributing just the official font files at first
(after all, I decided to package a font to make practice on a simple
package!). After this I'll be happy to help upstream with the build
scripts, and improve the Debian package when it's time.

My idea is that it shouldn't be more difficult to distribute a font
where the source code is available (even if not provided with an
automated build process) rather than a font where only the final product
is made available.

Paride


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20150910/114e0698/attachment.sig>


More information about the Pkg-fonts-devel mailing list