Sebastian Rahtz wrote: > I entertained myself running a large TEI document (the TEI Guidelines > themselves) > through my stylesheets. That threw up some errors, which I have now fixed. > The resulting FO file is valid according to RenderX's checkers, and > is processable using XEP. It's at > http://users.ox.ac.uk/~rahtz/Guidelines.fo
Valid just means: conforming to the (unofficial) XSL-FO DTD written by RenderX. > I tried the XMLMind XSL FO converters; the RTF created was readable > in OpenOffice; "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. XMLmind XSL-FO converter creates RTF, WML and OOXML which should look good when opened in Microsoft Word, and no other application. To be more precise: - 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. > the OpenOffice-specific format was not readable (OO 2.3 > rejected it). > I'd be interested to know if thats something wrong in my FO, or a bug > in the converter. 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. > 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.
