Well, Pango *did* drop Type1 support...
Regarding the 1.44 issue: There have been reports that a lilypond binary
compiled against Pango 1.43 doesn't work with 1.44 `.so` libraries (using
OpenType fonts). If this can be confirmed (can you do that?) we have a serious
bug in Pango itself since they broke ABI backward compatibility; this should be
reported as such, and the Pango guys have to increase the `.so` major number
correctly – or fix the ABI.
Of course, we should make LilyPond compile with newer Pango versions, too.
---
** [issues:#5545] Compatibility with pango 1.44**
**Status:** Accepted
**Created:** Wed Jul 31, 2019 07:59 AM UTC by Simon Albrecht
**Last Updated:** Tue Aug 06, 2019 06:59 AM UTC
**Owner:** nobody
[Reported by T.
Sefzick:](https://lists.gnu.org/archive/html/bug-lilypond/2019-07/msg00035.html)
With the new pango version 1.44 compilation of
`src/lilypond/lily/pango-font.cc`
gives warnings about
`'void* pango_fc_font_lock_face(PangoFcFont*)'`
to be deprecated and
`'pango_font_get_hb_font'`
should be used instead.
followed by
`error: invalid conversion from 'gpointer' {aka 'void*'} to 'FT_Face' {aka
'FT_FaceRec_*'}`
Seems that pango doesn't work with freetype fonts anymore.
A side note: lilypond executables compiled with pango <=1.43
produce an empty 1st page when run with pango 1.44 installed.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list._______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
