On Fri, 2004-06-11 at 03:17, bulia byak wrote:
argh. some error checking is needed. tho it's strange that the symbol font doesn't have a charmap. how is the unicode<->glyph conversion done?
PfaEdit (a highly recommended font editor btw) reports that symbol.ttf (from a Windows installation) uses "Symbol" encoding, and it correctly shows all its characters. So perhaps it's just a special encoding that we need to support.
Assuming I'm guessing correctly what problem fred was describing (I wasn't privy to the original email) we may also need to tweak the mapping between the symbol encoding's codepoints and unicode ourselves.
Symbol might be getting mapped directly into the first Unicode private use area, but I think user expectations are that it will also map into the bottom 256 unicode codepoints also.
pango layout should do the trick, with one caveat: since you can only specify one font for the layout, for the dominant direction, all the text in the opposite direction gets a default font from pango. if you have idea on how to tell pango to choose one specific font...
Well, in this case one can put the opposite-direction fragments to be in <tspan>s in SVG, and set a font for them.
Alternatively, maybe we could inject pango markup to control the font when doing the layout.
Anyway, this is much better than not having RTL before.
Yes, I think it is not necessarily something we need to worry about fixing for this release. Best to save our strength for fixing things that used to work and now don't. ^_-
(... yeah, like the statusbar... I'll get back to that soon, I promise ^^;;...)
-mental