Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 39418 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
In src/font.c:812, GdipCreateFont, fontconfig is used to match the 'best' family from config.
> 812 r = FcPatternGetString (family->pattern, FC_FAMILY, 0, &str);
However, this doesn't seem to be friendly to fallbacks, especially with system-generic names like "Sans". This makes using `new Font ("Sans, size);` in mono give tofus for CJK chars, while directly supplying the CJK font name gives some normal result (well, now the first font).
The output of `fc-match -s "Sans"` is available at https://cfp.vim-cn.com/ccw6. In this case, DejaVuSans was matched first, and then wqy-zenhei, the CJK font.
Cairo seems to provide something like cairo_ft_font_face_create_for_pattern(). Perhaps you can delay the fc interpretation and just store the pattern in `result`...
This also breaks SystemFonts.DefaultFont in Mono.
I think I got the point of that cairo thing wrong, and it seems that you need to do that yourselves. Hmm… Should I try the experimental Pango target…
Woah, it seems that building with pango does solve the problem: https://github.com/AOSC-Dev/aosc-os-abbs/issues/224.
So now preferring basic usability over official support...