From: Martin Sevior (msevior@physics.unimelb.edu.au)
Date: Fri Feb 28 2003 - 18:29:14 EST
On Fri, 28 Feb 2003, Seth Delackner wrote:
> Was( Re: ut_contextGlyph: display code or document code? )
>
> On Fri, Feb 28, 2003 at 09:08:43AM -0000, Tomas Frydrych wrote:
> >
> > I am not sure I really understand your question, but anything that
> > lives in the text/fmt directory is concerned solely with display, that
> > includes all the run classes; the glyph shaper in UT_ContextGlyph
> > too is concerned with display only. The structure of the document is
> > represented by the classes in text/ptb.
>
> This seperation cannot be perfect just yet because during export to RTF some of
> the fmt/* classes are used. I just noticed this while trying to figure out why
> a specific file crashes on conversion.
>
> gdb stack trace showing the exporter attempting to create a layout object:
> http://home.jtan.com/~seratonin/email/stack.txt
>
> The file I can't export to RTF (Bus Error in the previous stack trace):
> http://home.jtan.com/~seratonin/email/Virtualization.doc
You're right. The problem with the /text/fmt/xp classes in the export to
RTF classes is objeying the RTF rules for fields. Many fields in the RTF
export require calculating some some text which is not in the piecetable.
In order to correctly export to RTF we have to calculate those values and
place them inside the exprted RTF. I really did not like doing this but
the alternative is to duplicate a large amount of code in the impexp/xp
classes.
Cheers
Martin
>
This archive was generated by hypermail 2.1.4 : Fri Feb 28 2003 - 18:36:41 EST