Pullreq Reproducible: Always
There's at least one blocker bug: https://gitlab.gnome.org/Archive/pangox-compat/issues/1
+1 please. The pangox-library is very obsolete and not even in portage.
edit: it is, didn't look correctly fwiw the only 5 packages that use pangox-compat as a dependency are app-i18n/atokx23 net-misc/anydesk x11-libs/gtkmathview x11-libs/gtkglext x11-wm/sawfish
There are more issues with the 1.44.x release: dev-python/pygtk - There was [1] which has been closed meanwhile but there are still build issues. I had two more packages failing when doing a rebuild but I have lost the log files meanwhile. [1]: https://gitlab.gnome.org/GNOME/pango/issues/417
We also need to provide instructions on how to create fonts that work with pango-1.44 out of bitmap fonts, as that support was dropped, and some people use bitmap fonts as their monospace terminal/editor font, which would completely stop working with this new pango series.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66d950c109ef07428aaf8a1d1d234ee7ba42df55 commit 66d950c109ef07428aaf8a1d1d234ee7ba42df55 Author: David Heidelberg <david@ixit.cz> AuthorDate: 2019-10-30 13:03:19 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2020-02-03 02:36:22 +0000 x11-libs/pango: Version bump to 1.44.7 From Polynomial-C's overlay. Closes: https://bugs.gentoo.org/698922 Closes: https://github.com/gentoo/gentoo/pull/13498 Signed-off-by: David Heidelberg <david@ixit.cz> Signed-off-by: Matt Turner <mattst88@gentoo.org> x11-libs/pango/Manifest | 1 + ...break.c-Only-test-Thai-breaks-with-libtha.patch | 35 ++++++++++ x11-libs/pango/pango-1.44.7.ebuild | 81 ++++++++++++++++++++++ 3 files changed, 117 insertions(+)
Where is the news item with instructions on the bitmap font lack of support and how to convert bitmap fonts to things that pango-1.44 will still be working with?
Reopening then.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8a8d7b4345fb3b3bad67d9ac5ef3c3d6b9eb707 commit e8a8d7b4345fb3b3bad67d9ac5ef3c3d6b9eb707 Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2020-02-03 11:15:29 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2020-02-03 11:15:29 +0000 package.mask: Mask issue causing x11-libs/pango-1.44 It shouldn't have been pushed in the first place with all the known issues already marked blocking the bump bug... Bug: https://bugs.gentoo.org/698922 Signed-off-by: Mart Raudsepp <leio@gentoo.org> profiles/package.mask | 4 ++++ 1 file changed, 4 insertions(+)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e0e67f09b439f470dd5ac8836b8f0e90da4efa7e commit e0e67f09b439f470dd5ac8836b8f0e90da4efa7e Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-05-03 17:51:17 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-05-03 17:52:14 +0000 profiles: Add x11-libs/pangox-compat to package.deprecated Bug: https://bugs.gentoo.org/698922 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> profiles/package.deprecated | 5 +++++ 1 file changed, 5 insertions(+)
(In reply to Mart Raudsepp from comment #7) > Where is the news item with instructions on the bitmap font lack of support > and how to convert bitmap fonts to things that pango-1.44 will still be > working with? Isn't that backwards? I thought bitmap fonts are just vector fonts that have already been rasterized. For what its worth, I have been using pango-1.44 for a while now, and it has not given me any trouble.
(In reply to cyrillic from comment #11) > (In reply to Mart Raudsepp from comment #7) > > Where is the news item with instructions on the bitmap font lack of support > > and how to convert bitmap fonts to things that pango-1.44 will still be > > working with? > > Isn't that backwards? I thought bitmap fonts are just vector fonts that have > already been rasterized. pango-1.44 does not support the format those are often in anymore. People use them in terminals and such, they need a news item to know how to convert to a supported format (OTF/TTF/etc). > For what its worth, I have been using pango-1.44 for a while now, and it has > not given me any trouble. Yes, as long as you didn't rely on such a font (or pangox-compat), you were probably good by the time of 1.44.7.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4a1c51b9c9f6b14c0970b753d0fa21601aa5dd3c commit 4a1c51b9c9f6b14c0970b753d0fa21601aa5dd3c Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-08-22 15:23:54 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-09-27 17:51:39 +0000 profiles: Mask x11-libs/pangox-compat for removal Move x11-libs/pangox-compat from p.deprecated to p.mask. Bug: https://bugs.gentoo.org/698922 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> profiles/package.deprecated | 5 ----- profiles/package.mask | 5 +++++ 2 files changed, 5 insertions(+), 5 deletions(-)
(In reply to cyrillic from comment #11) > Isn't that backwards? I thought bitmap fonts are just vector fonts that have > already been rasterized. What I meant by that is the rasterizing process throws away too much information, and it is not practical to convert a bitmap font back into a vector font. The easiest solution is to uninstall your bitmap fonts, and replace them with the vector fonts that they originally came from.
The pango 1.45.5, 1.46.2, 1.47.0 also were released in last 5 months.
>Isn't that backwards? I thought bitmap fonts are just vector fonts that have already been rasterized. Pretty sure some of them are hand crafted, which is why they look lovely when displayed on a screen with compatible DPI value.
Just noting that GTK 4 was released today, and this bug blocks it. https://gitlab.gnome.org/GNOME/gtk/-/blob/master/meson.build#L14 bug #754402
In addition PFB fonts (Type1) also became unsupported, that did quite hurt. Especially because nothing will notify why half of the applications won't work anymore with a font that is in the font-cache. There have been improvements in pango which are worth mentioning: soft-hyphen support.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c8aad1653dd8424c391774868915ad75ff2f5873 commit c8aad1653dd8424c391774868915ad75ff2f5873 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2021-05-01 03:28:38 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2021-05-01 03:35:44 +0000 profiles: Unmask >=x11-libs/pango-1.43 Closes: https://bugs.gentoo.org/698922 Signed-off-by: Matt Turner <mattst88@gentoo.org> profiles/package.mask | 5 ----- 1 file changed, 5 deletions(-)
I'm going to repeat Mart Raudsepp from comment #7 about the missing news item. I've upgraded my system today, then after a reboot I realized that terminus font was replaced with some random proportional font and it took me a long time to figure out that a random pango upgrade was the culprit.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=392596a57baeee39ec2de1071942a98a91f21fcf commit 392596a57baeee39ec2de1071942a98a91f21fcf Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-15 02:40:32 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-20 01:09:12 +0000 media-fonts/font-misc-misc: add FONT_OPENTYPE_COMPAT support Bug: https://bugs.gentoo.org/698922 Signed-off-by: Sam James <sam@gentoo.org> media-fonts/font-misc-misc/font-misc-misc-1.1.2-r3.ebuild | 12 ++++++++++++ 1 file changed, 12 insertions(+) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=deeea06356aff42bcb6ceebb8bebca7f5dcc0c4e commit deeea06356aff42bcb6ceebb8bebca7f5dcc0c4e Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-15 02:41:30 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-20 01:06:04 +0000 profiles: add USE=opentype-compat Bug: https://bugs.gentoo.org/698922 Signed-off-by: Sam James <sam@gentoo.org> profiles/use.desc | 1 + 1 file changed, 1 insertion(+) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aafcb52277aa883f12e2e752e0f2d1e795b3ba18 commit aafcb52277aa883f12e2e752e0f2d1e795b3ba18 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-15 02:39:48 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-20 01:05:13 +0000 xorg-3.eclass: add FONT_OPENTYPE_COMPAT support Bug: https://bugs.gentoo.org/698922 Signed-off-by: Sam James <sam@gentoo.org> eclass/xorg-3.eclass | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9eb1de2e795d8a8b2e99d64a3c9567744bb0f41 commit a9eb1de2e795d8a8b2e99d64a3c9567744bb0f41 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-15 02:36:04 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-20 01:02:38 +0000 font.eclass: introduce FONT_OPENTYPE_COMPAT for converting old bitmap fonts >=x11-libs/pango-1.44 dropped support for old bitmap fonts. We can convert (or really, wrap/embed) fonts from the legacy .bdf and .pcf formats into the OTB wrapper format using x11-apps/fonttosfnt. This commit adds FONT_OPENTYPE_COMPAT to font.eclass which packages installing bitmap fonts can set to opt-in to conversion/wrapping. Note that the font conversion isn't perfect -- it's good enough in many cases, but in some cases they may require tweaking via fontconfig to get pixel size right, antialiasing settings, ... Adds IUSE=+opentype-compat to any ebuilds which set FONT_OPENTYPE_COMPAT; enabled by default given discoverability of this issue may be difficult and presumably any font package enabling FONT_OPENTYPE_COMPAT will be useless without it anyway. See also https://fedoraproject.org/wiki/BitmapFontConversion. Bug: https://bugs.gentoo.org/698922 Thanks-to: Kerin Millar <kfm@plushkava.net> Signed-off-by: Sam James <sam@gentoo.org> eclass/font.eclass | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)
