Re: Bug#755382: ITP: fonts-adobe-sourcehansans-cn -- “Source Han Sans CN” A sans-serif Pan-CJK font family (CN subset) that is offered in seven weights
On Wed, Jul 23, 2014 at 6:09 AM, James Cloos <firstname.lastname@example.org> wrote:
>>>>>> "PW" == Paul Wise <email@example.com> writes:
>>> * Package name : fonts-adobe-sourcehansans-cn
> PW> Due to the need for Adobe's ADFKO, this will have to go to contrib.
> PW> IIRC ADFKO will become open source at some point and the font could
> PW> move to main then.
> AFAICT, fontforge has enough capability to convert the format of the
> files in the git repo into OTF files, at least. Pehaps also combining
> those into the OTC files.
> The outlines are in the repo as type0 (collection of type1) format, but
> again fontforge can edit and save that format just as well as its own
> sfd format, so onecan argue that it is close enough to preferred src
> So it seems they are already dfsg-free, even without a dfsg-free release
> of adfko, yes?
> Or did I miss something which fontforge and/or fonttools cannot yet
I would be happy to be proven wrong on this; feel free to package it
for main if fontforge can take the place of all the commands mentioned
in the upstream build system. The way to prove that would be to only
ship the non-OTF files in the source package and build the OTF files
at build time using fontforge. Adobe might be unhappy at us for
finding out we are using a non-standard build though, so it might be a
good idea to ping them about AFDKO becoming FLOSS and let them know we
will use fontforge until that happens. Might be a good idea to send
them a Makefile that uses fontforge too.
Ken Lunde <firstname.lastname@example.org>