Hussein Shafie wrote: > "readable" is the right word. Barely "readable" in fact. > > This illustrates the problem of creating *production-level* output out > of XSL-FOs. I mean: a document you can give to your customers without > feeling ashamed. > > The RTF created by XMLmind XSL-FO converter is *unacceptably* *ugly* > when displayed in OpenOffice. > sure, that file I put up looks truly horrible; but that's because the design specified by the FO I produce is horrible. I didn't claim the design was readable :-}
> - XSL-FOs converted to RTF, WML, OOXML and opened in Microsoft Word > should look like the same XSL-FOs converted to PDF by XEP and opened > in Acrobat Reader. > > - XSL-FOs converted to OpenDocument and opened in OpenOffice.org > should look like the same XSL-FOs converted to PDF by XEP and opened > in Acrobat Reader. understood. you need a TEI to XSL FO stylesheet which produces FO which produces nice-looking results. I will see if I can find time to revisit my FO-making stuff to get it looking better for simple TEI documents; and I do mean "simple" there. A single rendering system for any arbitrary TEI documents is just not possible, I think. > > Probably a bug in...hold your breath...OpenOffice. However, we would > be very grateful if you could send us (mailto:john at xmlmind.com) the > XSL-FO file which causes this problem. its that http://users.ox.ac.uk/~rahtz/Guidelines.fo > >> FOP runs out of Java heap space. > > This kind of problem may happen to all Java applications. The maximum > size of the heap may be adjusted. > > FOP 0.94 is not bad, but our reference XSL-FO processor is still > RenderX XEP. yes, I can't take FOP too seriously. have they even implemented floats yet? -- Sebastian Rahtz Information Manager, Oxford University Computing Services 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
