> The issue is whether we want to draw all of UTF, and it's far too big > to be memorized glyph per glyph, or only latin characters, and the > single glyph texture approach becomes possible and preferable.
Ah - but no text is really all that likely to use all the glyphs, so a mechanism to render glyphs that are used "on demand" and then cache them for re-use later (on the basis that a given bit of text is very likely to re-use the same glyphs...) I guess we'd need some sort of low-cost hash scheme for "searching" for the cached glyphs quickly, then... With that mechansim, we can probably cache just a few thousand glyphs and get pretty much everything we'd need, for any given text. Or, we can (as you have done) render complete strings and cache them. I guess that will make the rendering more consistent between the GL and FL views, as we will get kerning and so forth the same in both cases. (I assume that glyph-by-glyph rendering will not cope with kerning and so forth.) > I reasoned that FLTK-1.3 aimed at full UTF support. It does. > To draw UTF to textures, one needs to be able to draw them > to a bitmap in the first place, and that is still not possible > in 1.3+X11+xft. I don't understand what you are saying here. I often render utf8 text, with non-LGC glyhs, into bitmaps and so forth. I don't understand what you are telling me here. > So, the way I see this issue is that extending > xft support to full UTF needs be solved before deciding how to > transform xft output into GL textures. Sorry - you have lost me - what part of XFT rendering do we need to fix? -- Ian SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
