For me, on Windows, that text renders as missing character squares. It probably uses an uncommon range that either the WebKitGTK widget is handling differently (different font?) from the standard widget. I've found that GNOME tends to use a very excellent coverage font by default for its UI elements. However, WebKitGTK might be defaulting to a different font for display that doesn't include those characters (whatever font WebKit in Chrome is using on Windows is not presenting those characters, so it's also possible the selected font it chooses on your machine does not include that coverage).
Just some speculation. --Greg On Fri, Jul 27, 2012 at 4:26 PM, Karl Kleinpaste <[email protected]> wrote: > I was just doing some updates to Xiphos' languages file, from this... > http://crosswire.org/wiki/Localized_Language_Names > ...which was referenced from the "choosing an app" page. > > When I add this entry to the file... > cop Ⲙⲉⲧⲣⲉⲙ̀ⲛⲭⲏⲙⲓ > ...it works in principle, and Xiphos displays it in the module tree just > fine. But it also kicks the GNOME font discovery tool to life, the > first time that the Biblical Texts section of the module tree is opened. > > What is so interesting about this entry, that it causes this extra font > discovery behavior, when demonstrably the content of the name is already > correctly displayed? > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
