Re: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source.

[alírio eyng]

On 4/2/16, Eric Bavier <address@hidden> wrote:
> It often appears that in trivial scripts it is simply the 'print'
> syntax that causes breakage between python2 and 3.
and you trivially fix it with 2to3 command

> while packaging the fantasque-sans font, I found that it requires
> fontforge with python2 (because of print syntax, ugh).
[1] uses obsolete print statement, i think it isn't needed to build
[2] uses print function

> do we really want
> python3 for fontforge if their documentation is introducing users to
> python2 syntax and many font packages need python2?
making people downgrade to python2 isn't nice[3]
"many font packages need python2" is questionable, freefont should
support python3 in next release, i think you can _build_
fantasque-sans with python3

> Perhaps we leave python3 in the user-installable fontforge, but have a
> private python2 variant for building fonts when necessary?  What do
> others think?
ok

the ideal would be to make a font-build-system so we could use the
isMonoMono.py from freefont to validate all mono fonts; and the build
system would have the right python, not individual fonts

the problem with fantasque-sans is they have python code embedded in
bash, so i think 2to3 won't work
freefont had nontrivial code 2to3 can't convert

[1]https://github.com/belluzj/fantasque-sans/blob/master/fontdiff
[2]https://github.com/belluzj/fantasque-sans/blob/master/validate-generate
[3]https://github.com/ncraun/smoothscan/issues/3#issuecomment-24867766