[Pkg-fonts-devel] Bug#703456: Bug#703456: Bug#703456: Bug#703456: Bug#703456: Please add Nafees Nastaleeq
pabs at debian.org
Mon Jun 9 23:42:59 UTC 2014
On Mon, Jun 9, 2014 at 10:43 PM, Nicolas Spalinger wrote:
> On 09/06/14 09:07, Paul Wise wrote:
>> I'm not sure what all this
>> means in terms of the DFSG but it is probably OK.
> May I suggest helping upstream to come up with reproducible buildpath
> instead of creating a Debian-specific one ? A much better long-term strategy
> for everyone.
That would be great but since upstream are using Microsoft Windows I'm
not sure they would appreciate us telling them to completely switch
around their workflows and or platform without clear arguments about
the benefits from their PoV. Personally I don't know enough about the
upstream side of font production to be able to provide those
> You can look into libfont-ttf-scripts-perl (and newer repository version)
> which contain the volt2ttf and related utilities and can work with
> text-based representations of the smart features. (vtp files).
> Type designers are increasingly moving towards using the .fea features files
Thanks for the info, I wasn't aware these existed. It would be great
to add some info about the various upstream font technologies,
non-standard sfnt tables and how to work with them in Debian to the
wiki page or a sub-page of the wiki page.
> BTW, if you haven't noticed yet, there are significant issues with the
> licensing of this font that still need fixing (it's sadly a non-standard
> mishmash of licenses with little coherence, legal validity or practical use
> cases: http://www.cle.org.pk/software/license/Nafees_Nastaleeq_License.html
> So I would expect our ftpmasters to seriously frown on this and reject it!).
> TTBOMK various people (including Mozilla) are in touch with upstream to get
> them to re-release under a community-approved license.
I did notice the custom license but didn't analyse it for DFSG issues.
More information about the Pkg-fonts-devel