Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#58235 - [libgdiplus] Cannot handle font fallbacks unless compiled with pango support

Attached to Project: Arch Linux
Opened by Mingye Wang (arthur2e5) - Sunday, 15 April 2018, 05:55 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:24 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


libgdiplus by default calls cairo directly. It retrives the first font match from fontconfig, and goes on to only use that match for all of the rendering. This of course breaks UI rendering in WinForms using e.g. "Sans", as a lack of fallbacks means a lot less font coverage and blank rectangles appear where they shouldn't happen.

The good news about this issue is that libgdiplus has a "--with-pango“ build option right in its official source. The option uses pango, which does fallbacks correctly. Yes, it's "UNSUPPORTED", but what on earth from Xamarin is meaningfully supported anymore?

This is a longstanding bug, reported as early as 2 years ago as

Additional info:
* package version(s) (EVERY/ALL)

Steps to reproduce:
Compile the source at, and run it in a locale where "fc-match Sans" does not give a Chinese font but is capable of displaying of Chinese text via fallback.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:24 GMT
Reason for closing:  Moved
Additional comments about closing: ackaging/packages/libgdiplus/issues/1
Comment by Mingye Wang (arthur2e5) - Sunday, 15 April 2018, 06:02 GMT
(And no, it is likely that this will never be fixed unless pango is used. Because Cairo alone is simply not for rendering multilingual text and doing stuff like fallbacks. cf.

Also, they appear to be working on supporting the pango stuff. That's a good thing -- maybe if you come back in a few months it will become the default.
Comment by Jan de Groot (JGC) - Wednesday, 18 April 2018, 10:26 GMT
Looking at post-release commits, it seems there has been some serious work on the pango support in libgdiplus.

We have some options here:
- implement this with next release, which can take quite some time
- backport the pango improvements
- push to snapshot
Comment by Marcell Meszaros (MarsSeed) - Monday, 25 April 2022, 12:14 GMT
Pango is now officially supported as a build option,
since v6.0, released on 2 Aug 2019.


Latest release (v6.1 as of now):
Comment by Marcell Meszaros (MarsSeed) - Sunday, 18 June 2023, 12:35 GMT
Any chance of libgdiplus getting updated and configured to use pango to fix this issue?

You know this package has the oldest flag-out-of-date in all of the Arch repis? (2019-08-08)
Comment by Marcell Meszaros (MarsSeed) - Sunday, 18 June 2023, 12:50 GMT
There are also a few as-yet unaccepted PR's improving font handling and rendering with Pango:
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.