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 608929 - No font fallbacks on OS X
No font fallbacks on OS X
Status: RESOLVED OBSOLETE
Product: pango
Classification: Platform
Component: atsui
1.26.x
Other Mac OS
: Normal normal
: ---
Assigned To: gtk-quartz maintainers
pango-maint
Depends on:
Blocks:
 
 
Reported: 2010-02-03 22:11 UTC by Mikayla Hutchinson
Modified: 2012-08-25 20:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mikayla Hutchinson 2010-02-03 22:11:27 UTC 
There doesn't seems to be any handling of fallbacks for fonts on OS X.

E.g. editing code using the Monospace Menlo font, Japanese or Arabic comments cannot be read, but instead display as strange patterns of boxes, and cursor movement across these characters is extremely strange.

Using the same font in Xcode, the Japanese and Arabic characters display fine.
Comment 1 Kristian Rietveld 2010-02-28 21:40:02 UTC 
I can confirm this problem.

At the moment it is not fully clear to me how this should be fixed in the ATSUI backend.  I think that implementing proper support for fetching coverage from the fonts (which seems possible, contrary to what is said in the source code currently) and support for fetching font sets from the Mac API matching a given language should help.  I have not quite figured out yet how the acquisition of a font with glyphs for a given language works on OS X.


It is also important to observe that the ATSUI backend is a dead end, since most of that API has been deprecated by Apple.  I think I will focus my resources first on creating a CoreText backend.  Within CoreText there is support for font coverage and language matching, so it must be possible to implement a full-fletched Pango backend.
Comment 2 Kristian Rietveld 2010-03-05 21:25:52 UTC 
Bug 611943 will cover development and review of the CoreText backend, that will hopefully be replacing the ATSUI backend for Macs running Mac OS 10.5 and later.  I will be looking into implementing proper calculation of fontsets (which is the crucial part next to support for fetching coverage from fonts) into this CoreText backend first.

Once I have figured that out, I can try seeing if it is possible to implement this in the ATSUI backend as well.  But since ATSUI has been deprecated, it will not be top-priority for me.
Comment 3 ally 2011-09-20 21:51:42 UTC 
Hi I am having this same problem.  Attached is a screen shot of the home screen.  All the links, tabs, buttons, etc. work but the text is still wrong.  I have uploaded multiple times and it continues to be a problem.

Please help, I am a MFA Design student at California College of the Arts in San Francisco and we are using your product for thesis work.

Thanks
Comment 4 ally 2011-09-20 21:57:08 UTC 
Hi I am having this same problem.  Attached is a screen shot of the home screen.  All the links, tabs, buttons, etc. work but the text is still wrong.  I have uploaded multiple times and it continues to be a problem.

Please help, I am a MFA Design student at California College of the Arts in San Francisco and we are using your product for thesis work.

Thanks
Comment 5 Kristian Rietveld 2011-09-23 12:58:26 UTC 
Font fallback support for CoreText is being tracked in bug 647969.  As I've mentioned in comment 2, the ATSUI backend has no priority for me anymore.
Comment 6 Behdad Esfahbod 2012-08-25 20:19:13 UTC 
ATSUI backend has been removed.