9 Dec
2008
9 Dec
'08
8:33 a.m.
Vladimir Volovich wrote:
while this does not look like a right fix (the problem seems to be caused by fooling intl.h by "#undef HAVE_LIBINTL_H" above), it seems to fix the build process.
this was somehow lost during recent upgrade of fontforge in luatex.
is it possible to fix the problem upstream (in fontforge) so it won't re-appear again after another update of fontforge in luatex?
I've reinstated that fix (in trunk). I'll send a message to fontforge-devel once everything seems to work. Best wishes, Taco