Update to 1.44

[Iain Lane]

There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now.

Overview of changes in 1.44.6
=============================
- docs: Fix symbol indices
- Fix Thai line breaking
- Re-add symbols needed by some bindings
- Don't insert hyphens for some languages
- Fix a crash with hyphenation

Overview of changes in 1.44.5
=============================
- Revert a broken change (causing crashes on OS X)

Overview of changes in 1.44.4
=============================
- Add an insert-hyphens attribute
- Reinstate the return type of pango_fc_font_lock_face
- Fix a problem with ellipses getting the wrong font
- fc: Improve filtering by font format
- Re-add PangoFcFont to public headers
- Install PangoFc and PangoOT introspection files
- Fix ink rectangles to have positive height
- Fix mark positioning
- Switch to using harfbuzz for metrics

Overview of changes in 1.44.3
=============================
- Install pango-ot headers
- Make subpixel positioning optional
- fc: Ignore fonts with unsupported formats

Overview of changes in 1.44.2
=============================
- Disable ligatures when letterspacing
- Set design coords on hb_font_t
- Expose more font options in pango-view
- OS X: Make 'system-ui' font work
- Keep deprecated pango-fc apis in headers
- Make hex boxes work, always
- introspection: Various build fixes
- introspection: Add PangoPT, PangoFT2 namespaces
- layout: Make the new line-spacing opt-in

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

Overview of changes in 1.43.0
=============================
- Drop autotools
- Drop Visual Studio build
- Build with meson everywhere
- Update Emoji tables for Unicode 11
- Update test data for Unicode 11
- Fix a crash with Thai breaking
- Fix a crash with font variations
- Deprecate bidi apis in favor of fribidi
- Add a variable font family api
- Improve font fallback handling on win32

And see posts from upstream

https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/
https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/
https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/

for the new features.

We'd like to update to it, if possible.

[Iain Lane (laney)]

I've just built it here: https://launchpad.net/~laney/+archive/ubuntu/ppa/+sourcepub/10458725/+listing-archive-extra

[Łukasz Zemczak (sil2100)]

This looks good in overall. I trust that you are confident that the new pango1.0 will migrate without any bigger issues, especially seeing how many reverse-dependencies it has. I also hope there is no ABI break introduced in the two new versions? The changelogs do not seem to mention anything explicitly. Wouldn't want us to require additional rebuilds so late in the cycle.
Have you tested the packages from the PPA?

[Iain Lane (laney)]

On Fri, Sep 06, 2019 at 11:35:47AM -0000, Łukasz Zemczak wrote:
> This looks good in overall. I trust that you are confident that the new pango1.0 will migrate without any bigger issues, especially seeing how many reverse-dependencies it has. I also hope there is no ABI break introduced in the two new versions? The changelogs do not seem to mention anything explicitly. Wouldn't want us to require additional rebuilds so late in the cycle.
> Have you tested the packages from the PPA?

I'm running with them, it seems fine to me. I think I'd want to check
with others in the desktop team before going ahead, though.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

[Sebastien Bacher (seb128)]

I installed the ppa version on my eoan system, works fine, including french accents ;-)

[Iain Lane (laney)]

It's more like issues with differences in rendering, e.g.:

  - https://github.com/harfbuzz/harfbuzz/issues/1892

  - https://gitlab.com/inkscape/inkscape/issues/364

I'm a bit clueless here, would be happy for someone else to weigh in :-)

[Sebastien Bacher (seb128)]

I'm unsure we have someone in the team/around who knows enough about font rendering to weigh in. I would go forward now with the update because I feel like it's a safer road for the LTS to land changes earlier than later, that time we get one buffer nonLTS cycle to get feedback sort out issues (also based on the fact that even if there are bugs they aren't obvious on a default installation and we can still fix special cases between now and release or in a SRU)

[Iain Lane (laney)]

Feel free then, I'm just really unsure personally about us being able to fix regressions, but if you think that is an OK risk then fine.

[Sebastien Bacher (seb128)]

We failed to have consensus in Paris and I feel like it's getting late now and we have enough other work to do to wrap the cycle so would prefer to delay to next cycle now. Iain, what do you think? (you opened the FFe but so you should be the one deciding if we withdraw the request)

[Iain Lane (laney)]

On Mon, Sep 23, 2019 at 10:12:14AM -0000, Sebastien Bacher wrote:
> We failed to have consensus in Paris and I feel like it's getting late
> now and we have enough other work to do to wrap the cycle so would
> prefer to delay to next cycle now. Iain, what do you think? (you opened
> the FFe but so you should be the one deciding if we withdraw the
> request)

Right, yes, I think so. Sorry about this - maybe I was being overly
conservative here, not sure. Agreed we probably have enough work to do
and don't want to have to deal with any (unknown) fallout from this.

For the record, I saw mclasen saying on IRC somewhere (can't find it
right now) that some commits from cairo git ara cairo snapshot needed to
work properly with this new pango but there is no maintainer to release
it - not sure of the details. We should bear this in mind next cycle.

 status wontfix

Cheers,

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

[Sebastien Bacher (seb128)]

(re-opening and tagging as blocked by ff for our tracking script)

[Christian Ehrhardt  (paelzer)]

This is in Focal, lets close the bug
 pango1.0 | 1.44.7-1 | focal | source