[Pkg-fonts-devel] fontforge pending issues and uploading to experimental

Philippe Cochy acquadoria at gmail.com
Mon Jul 18 15:54:39 UTC 2016

Le dimanche 17 juillet 2016 à 21:07 +0200, Fabian Greffrath a écrit :
> Hi Vasudev,
> Am Sonntag, den 17.07.2016, 20:01 +0530 schrieb Vasudev Kamath:
> > How should we deal with this?. There seems to be some work around for
> > building pecita with new fontforge as discussed by pecita author in
> > above issue. Can we patch the fonts-pecita when we upload new
> > fontforge?.
> I'd say this is similar to a new GCC upload. If a package fails to
> build with a new version of GCC, we usually file bugs against the
> failing package instead of GCC.
>   - Fabian

The font Pecita is completely dependent on the FontForge function
ExpandStroke. The nearly 5000 drawings glyphs are made without thickness
are then applied:
It's a fantastic productivity tools that disappears today in FontForge.
Of course the same action performed manually fall in the same bug and it
concerns a lot of FontForge users!


More information about the Pkg-fonts-devel mailing list