Bug 25196

Created attachment 11221 [details]
gvim with pango after the upgrade - bad looking.

Created attachment 11222 [details]
with pango 1.43.

Don't know if related or not but NEWS log says:


- Stop using freetype for font loading; this
    drops support for type1 and bitmap fonts



Overview of changes in 1.44.1
=============================
- Fix a crash with allow_break attributes
- Fix Emoji spacing
- Fix up includes and pkg-config requires
- Correct some cases for hyphen insertion

Overview of changes in 1.44.0
=============================
- Use harfbuzz for shaping on all platforms
- Stop using freetype for font loading; this
    drops support for type1 and bitmap fonts
- Add a getter for hb_font_t
- Make PangoCoverage a GObject
- Add a pango_tailor_break api
- font metrics: Add line height
- layout: Support line spacing
- layout: Draw hyphens for line breaks
- Add an attribute to suppress line breaking
- cairo: Don't render hex boxes for space
- Add an attribute to show invisible characters
- Stop quantizing glyph positions
- Add tests for itemization and line breaking
- Remove language and shape engine remnants
- Rename meson options: gtk_doc, introspection
- Require GLib 2.59.2
- Require Harfbuzz 2.0

CC: (none) => geiger.david68210

@Shlomi
Thank you for providing the two examples (although the updated one is not so bad, just less good).

(In reply to David GEIGER from comment #3)
> Don't know if related or not but NEWS log says:
> - Stop using freetype for font loading; this
>     drops support for type1 and bitmap fonts
This had me baffled! Is the NEWS log referred to a Pango thing?
Who should stop, or has stopped, using Freetype to load fonts? Pango?
What exactly "drops support..." ? Pango again?
---
Pango has no registered maintainer, but assigning this to Olav because you apparently have worked a fair bit with it in the past.
Re-assign it globally if you want.

Assignee: bugsquad => olav

(In reply to Lewis Smith from comment #4)
> @Shlomi
> Thank you for providing the two examples (although the updated one is not so
> bad, just less good).
> 
> (In reply to David GEIGER from comment #3)
> > Don't know if related or not but NEWS log says:
> > - Stop using freetype for font loading; this
> >     drops support for type1 and bitmap fonts
> This had me baffled! Is the NEWS log referred to a Pango thing?
> Who should stop, or has stopped, using Freetype to load fonts? Pango?
> What exactly "drops support..." ? Pango again?


Yes, its Pango that dropped support fro type1 and bitmap fonts  because of: "We want to stop using freetype because FC_Face locking is broken and causes unsolvable issues between cairo's and pango's use of it"


This issue is also being discussed on xorg-devel where they are thinking of shipping the fonts as OpenType bitmap fonts that HarfBuzz supports... 
so we'll see where we'll (and all other distros) end up ...

See Also: (none) => https://gitlab.gnome.org/GNOME/pango/issues/386
CC: (none) => tmb

Also new pango seems to have broke some pkgs build, e.g: remmina, kde-gtk-config and surely some others!

I have to add a workaround for now to make it build, like:

export CPATH="${CPATH}:%{_includedir}/harfbuzz"