Subject: Re: On rendering (Re: Pango will be a problem)
From: Martin Sevior (msevior@mccubbin.ph.unimelb.edu.au)
Date: Thu Jan 04 2001 - 16:47:29 CST
On Thu, 4 Jan 2001, Leonard Rosenthol wrote:
>
> Think of Pango (and similar things) as a "mini AbiWord" that
> only knows about Paragraphs. It has all the smarts necessary to
> render multilingual (Unicode-based) multi-styled text, including text
> wrap (and word breaking), etc. So you just create a "paragraph"
> (which includes all the text and style runs) and then tell Pango
> (etc.) to render.
>
Ah this finally makes sense. Have you actually lookd through the Pango
API? I mean to but find myself dissecting RTF instead.
BTW reading the RTF spec gives an excellent insight as to how MS Word
works. In the case of lists they did not discover our "parentID" tag. I
can see why they do not allow direct cutting of list structures. Without
the parentID tag they could not undo cutting a multi-level list. We can do
that of course.
People interested in implementing Frames or Tables would do well to read
RTF spec on how MS does them. MicroSoft helpfully provides some very
useful documentation on RTF at:
http://support.microsoft.com/support/kb/articles/Q269/5/75.ASP
Lots of other info on RTF can be found at google.com with the keyword
search
"Rich Text Format"
I love google...
Its really hard to find the time to work on importing/exporting lists to
RTF right now but I have made some progress.
Cheers
Martin
This archive was generated by hypermail 2b25 : Thu Jan 04 2001 - 16:47:47 CST