After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 655297 - Font fallback not working on OS X CoreText
Font fallback not working on OS X CoreText
Status: RESOLVED DUPLICATE of bug 647969
Product: pango
Classification: Platform
Component: coretext
unspecified
Other Mac OS
: Normal normal
: ---
Assigned To: gtk-quartz maintainers
pango-maint
Depends on:
Blocks:
 
 
Reported: 2011-07-25 23:48 UTC by Bill Kelly
Modified: 2011-07-26 09:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bill Kelly 2011-07-25 23:48:40 UTC 
Pango font fallback seems to be broken on OS X with CoreText.

For example, the following UTF-8 string contains two Japanese characters at the end:

"_MG_9781.jpg:\xE5\xA4\xA7\xE9\x98\xAA"

(I.e. "_MG_9781.jpg:\u5927\u962A")

However, when using a font like Helvetica or Arial, which do not themselves contain the necessary glyphs, Pango is not falling back to a font which does contain the glyphs.


I'm using the latest Pango sources from git, on OS X 10.6.7, and have built Pango as:

CXXFLAGS="-arch i386 -g -O0 -fno-rtti -fno-exceptions" CFLAGS="-arch i386 -g -O0"  \
 ./autogen.sh --prefix=/usr/local/clutter-i386 --enable-shared --enable-introspection=no --without-x


Thanks,

Bill
Comment 1 Bill Kelly 2011-07-25 23:54:56 UTC 
Oops, I see this is already a known issue with Pango / CoreText:

https://bugzilla.gnome.org/show_bug.cgi?id=647969


Sorry for the duplication.
Comment 2 Kristian Rietveld 2011-07-26 09:11:49 UTC 

*** This bug has been marked as a duplicate of bug 647969 ***