Hi Yuri, Yuri Dario wrote: > I'm checking how OOo does identify symbol fonts: in the OS/2 port, it > happens that bullet symbols are properly displayed if OpenSymbol ttf > font is installed, otherwise we get empty rectangles. In such case, it > could be related to a missing fallback for OpenSymbol or missing glyphs > into others symbol fonts. > > I see vcl code handles different fields, one is the meCharSet, another > is the mbSymbolFlag.
Here is the historic perspective: Before SO/OOo adapted unicode the meCharSet member was very important for internationalization. Since the unicode migration it is only needed for backwards compatibility. Today what is left of all the endlessly confusing and bug infested charset-specific text handling is just the one mbSymbolFlag. It indicates that a code point does not have a semantic which is independent of the font. So it usually doesn't make sense to spellcheck symbol strings. And glyph fallback often doesn't make sense too, except for some very specific fonts. In vcl/source/gdi/fontcvt.cxx there is logic to convert some important symbol fonts from to StarSymbol/OpenSymbol. Extending this machinery to translate every platform specific important symbol font is doable, but is it really worth the trouble? Installing OpenSymbol is no black magic. OOo does identify that a font is a symbol font is platform dependent: on WIN ports the LOGFONT member lfCharSet is checked for SYMBOL_CHARSET. On UNX ports the psprint module analyzes the font and/or metrics files directly. I hope this helps, -- Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
