Hi Yuri,

>>specific fonts. In vcl/source/gdi/fontcvt.cxx there is logic to convert
>>some important symbol fonts from to StarSymbol/OpenSymbol.
> 
> 
> while rewriting the logical font selection code, I discovered that vcl
> renames OpenSymbol to StarSymbol.
> In the salgraphics::setfont call, the maName field of
> ImplFontSelectData contains StarSymbol instead of OpenSymbol, and this
> caused a lot of problems in font matching because of different name.

In fontcfg.cxx there are a lot of conversion tables between StarSymbol and
other symbol fonts. Since AFAIK StarSymbol is a superset of OpenSymbol
these conversion tables can also be used to translate from/to OpenSymbol.

For other parts of VCL here is the big picture regarding font family names:
ImplFontSelectData.maName is the name that was requested by an application
calling OutputDevice::SetFont(). 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.

--
Herbert

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to