John Ehresman wrote:
Robert Roessler wrote:
In particular, aren't the specific implementations of the GTK/Pango
libraries free to use whatever they want to actually stuff the bits
into a bitmap? All these functions do is [presumably] reap whatever
optimizations are possible in being specialized for specific font
representations... right? Or is this where my model needs work? :)
The backends are mostly responsible for enumerating available fonts,
reporting the space used be specific glyphs for a specific font size &
other attributes and drawing the glyphs at specific positions. That's
glossing over a fair bit, but that's about it. I think that
functionality is available without writing backend dependent code though.
As an aside, in these contexts, "win32" means TrueType fonts, while
"ft2" means FreeType fonts, right? Are either of these expected to be
replaced anytime soon?
I don't know exactly where you are looking, but I think the cairo
backend is used in the gtk 2.8 stack and that the win32 bits have been
rolled into this backend.
What prompted this exchange was my noticing the tree:
http://www.gtk.org/api/2.6/pango/
and more specifically
http://www.gtk.org/api/2.6/pango/pango-Win32-Fonts-and-Rendering.html
http://www.gtk.org/api/2.6/pango/pango-FreeType-Fonts-and-Rendering.html
THIS is what the "pango_{ft2,win32}_{font,render}..." reference I made
earlier was all about... ;)
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
