Hi Herbert,
>The name of the device font that matches
>most closely on is in the ImplFontSelectData.mpFontData->maName. On your
>system there is probably just OpenSymbol, so when an application requests
>StarSymbol, which isn't available, this one gets chosen.
ah, here is the problem: the OS/2 logical font API does a best match
unless a unique system id is passed; this id is enumerated in the
Os2SalGraphics::GetDevFontList.
But in latest code, I removed use of this id, thus leaving the OS/2
graphic engine to select a best match based on name, style, size and so
on.
So without a StarSymbol font, OS/2 selected a different font that
matches most required fields, but this was not a symbol font. And the
call did not fail obviously.
Maybe this could explain another bug: truetype bold fonts are exported
to pdf using emulated bold, then they looks ugly compared to normal
output.
Bye,
Yuri Dario
/*
* member of TeamOS/2 - Italy
* http://www.os2power.com/yuri
* http://www.teamos2.it
*/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
