[Qt-interest] "Glyph neither outline nor bitmap format"

[william.crocker at analog.com]

I had this (load glyph failed) happen to me when I tried
to upgrade to 4.6.3 (and I pay for support.) The fix I have
chosen was to NOT upgrade to 4.6.3, but to stick with good
old reliable 4.5.3 and pray for 4.6.4

Bill

Atlant Schmidt wrote:
> Folks:
> 
>  
> 
>   So we have this application that’s been running pretty well under Qt
>   4.5.2 and now 4.6.2. But now we’ve tried to migrate it to our Qt 4.6.3
>   runtime environment and suddenly we’re getting font failures.
> 
>  
> 
>   They are heralded by two symptoms:
> 
>  
> 
>     o One of our screens suddenly displays all of its lower-case
>        “u” characters displayed as subscripts.
> 
>  
> 
> It’s q_u ite a c_u te phenomenon, but _u seless for our app.
> 
>  
> 
>     o STDERR repeats, over and over again:
> 
>  
> 
> load glyph failed err=6 face=0x10737d50, glyph=832
> 
> QFontEngine: Glyph neither outline nor bitmap format=0
> 
>  
> 
>  
> 
>   This apparently is a fairly famous message with quite a few Google
>   hits over the last several years but I don’t see an actual explanation
>   of how it (spontaneously) arises or how to resolve it. It is (currently)
>   displayed by the module:
> 
>  
> 
> …/gui/text/qfontengine_ft.cpp
> 
>  
> 
>   and a value of 0 corresponds to QT_FT_GLYPH_FORMAT_NONE,
> 
>   defined in:
> 
>  
> 
> …/gui/painting/qrasterdefs_p.h
> 
>  
> 
>  
> 
>   It appears in Qt Bug 12196 but that’s unanswered.
> 
>  
> 
>     http://bugreports.qt.nokia.com/browse/QTBUG-12196
> 
>  
> 
>  
> 
>   Our font environment is unchanged from 4.6.2 to 4.6.3 and a simple test
>   app (using one of our own added fonts) has no trouble displaying the 
> letter
>   “u” nor any of the glyphs at Unicode code points 831 (“combining double
>   overline”), 832 (“combining grave tone mark”), and 833 (combining acute
>   tone mark”).
> 
>  
> 
>   Has anyone seen this problem? Did you come up with a solution?
> 
>  
> 
>                                    Atlant
> 
>  
> 
>  
> 
> P.S.: Are there any other 4.6.2.->4.6.3 migration issues I should
>         be aware of? (At the moment, our app is still being built against
>         Qt 4.5.2 and being run in a 4.5.2, 4.6.2, and (hopefully) 4.6.3
>         environment, but apps are supposed to be forwards binary
>         compatible within Qt 4.x, right?)
> 
>  
> 
>  
> 
> 
> ------------------------------------------------------------------------
> This e-mail and the information, including any attachments, it contains 
> are intended to be a confidential communication only to the person or 
> entity to whom it is addressed and may contain information that is 
> privileged. If the reader of this message is not the intended recipient, 
> you are hereby notified that any dissemination, distribution or copying 
> of this communication is strictly prohibited. If you have received this 
> communication in error, please immediately notify the sender and destroy 
> the original message.
> 
> Thank you.
> 
> Please consider the environment before printing this email.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest