On 04/22/2016 12:54 PM, Alexandre Julliard wrote:
Jens Reyer <jre.winesim(a)gmail.com> writes:
Wine and Debian are both using the quite old
fontforge version
20120731-b, the patches apply cleanly in Debian.
But upstream is actively developing and in Debian someone is working on
packaging a recent version (not sure with what outcome, e.g. afaik there
is at least one upstream regression blocking an update).
Are there any plans in Wine to update to a newer version?
No plans currently, but I can certainly look into it if it helps.
Thanks. First off, I successfully tested the current fontforge
20160404. I built Wine and the .ttf files with it, and verified in one
app that relies on them that they are working. So no immediate need to
update, but it might be a good idea generally.
After looking into your patches and explanation my understanding is
that we may regenerate the .ttf files in Debian without having to
worry about the results. However for contributing to Wine the current
Debian fontforge is not suitable. So I started trying to get your
changes applied upstream:
> 1. Various hacks to avoid putting timestamps
in generated files (AJ).
Created issue
https://github.com/fontforge/fontforge/issues/2711
The timestamps are also a hindrance for reproducible builds, and need
to be tackled somehow in fontforge anyway.