Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On Sun, Jan 22, 2017 at 09:02:09PM +0800, Paul Wise wrote: > Ultimately we need something to change in the upstream fonts community > though; either one of the existing font tools needs to add Glyphs > support or Glyphsapp folks need to release some sort of free toolkit > for it. Otherwise this is

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On Tue, Jan 17, 2017 at 10:29 PM, Fabian Greffrath wrote: > But the OTF format itself is just as suitable a source format for fonts as > any other format. Why is it so important what upstream has chosen? It is > not that font composition is a human-readable-to-binary-one-way-road like >

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On January 17, 2017 3:49:46 PM EST, Fabian Greffrath wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > >Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney: >> Debian recipients should have equal access to make modifications to >> the work, build the work

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney: > Debian recipients should have equal access to make modifications to > the work, build the work from modified source, and install the > result. All these modifications could be made to