> 4) KEY POINT - use context.pango_layout to lay out paragraphs. If you > don't do this, you end up doing your own line-breaking routines, font > formatting, etc. Which you *will* get wrong for most languages except > your native one. This is why we have pango in the first place.
This is something I haven't been doing until now -- I'll be more than happy to give up my lousy layout routine and pass it off to pango. However, I'm confused how the pango stuff works. How do you know where context.pango_layout(...) leaves me on the page? I'm used to writing each line with my own routine and keeping track of e.g. margins, wrapping-around pictures, and page-breaks/page numbers/page headers myself. Do you understand how all this works with context.pango_layout...? (I realize this is poorly documented -- but if you or anyone knows the answers, they'd add to the usefulness your post will already provide for many future googlers!). Tom _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
