[Qt-interest] Font issue with Windows 7

[Wm. G. Urquhart]

On 04/06/2010 08:50, Oliver.Knoll at comit.ch wrote:
> Wm. G. Urquhart wrote on Friday, June 04, 2010 9:20 AM:
>
>>> ... eyes. Are you sure you haven't accidentally requested a
>>> Symbols or WinDings font-family?
>>
>> Hi Colin,
>>
>> Positive, I've just double checked and I've attached the
>> properties window displaying my selection. As I said in the
>> original message even if you build on Windows 7 with a font of
>> choice from those available the result is still the same.
>
> Okay, I admit the following is a totally weird guess - but so is the
> problem ;)
>
> According to
> http://msdn.microsoft.com/en-us/library/dd374112%28VS.85%29.aspx the
> fonts 'MS Shell Dlg' and 'MS Shell Dlg 2' are merely "logical" font
> names which are mapped onto a concrete font, such as Tahoma for 'MS
> Shell Dlg 2' (depending on the Windows version). But the mapping is
> also influenced by the regional settings, e.g.: "MS Shell Dlg uses
> Microsoft Sans Serif (distinct from MS Sans Serif) if the install
> language is not Japanese. MS Shell Dlg maps to MS UI Gothic if the
> install language is Japanese."
>
> Now my totally weird conclusion would be that some
> freak-regional-setting influences Windows for the choice of the
> actual font (maybe also with the "help" of Qt), and that the chosen
> font is not properly installed or available - okay, very shaky (since
> when a font is not available it is replaced by a font which IS
> available etc.) but worth a thought.
>
> Maybe studying the above article more carefully also reveals more
> useful insights. Somehow a bell rings in the back of my head that MS
> did change the default "Shell Dlg" font on Windows 7 - which would
> explain the different behaviour between Win 7 and XP (Vista) that you
> are seeing.
>
>
> Try choosing an "existing" font such as "Tahoma" and see whether that
> makes a difference?
>
> Cheers, Oliver

Well it gets weirder by the minute. Using designer to view the UI 
displays as expected, using either a 'real' or 'virtual' font name. 
However as soon as the application is run it fails.

Now to add another twist it is only relevant to x64 builds! We have 
another application that was originally x86 and this compiles and 
displays correctly on Windows 7, so we added an x64 version to the build 
configuration. But when this is ran it displays the same 'font' issue.

Any ideas?

-- 
William