Thank you very kindly for your reply. You answered all my questions but I have one follow up point. You mention the XXE has 3 layers of XSL-FO processors, when I look at the add-ons I do see the XMLmind FO converter XSL-FO Processor plug-in which is installed. If I am understanding your reply below correctly, that this plug in DOES NOT render PS or PDF, instead just the formats RTF, WordML, odt, docx? I also see that the version I have is 4.3.1 - while you indicate that the XMLmind FO converter 4.4. Is there an update available?
Another follow up point, since I see that the Apache FOP .095 plug in is currently NOT installed, and based on my previous point (that XXE fo 4.3.1 does NOT produce PS/PDF) how can I be generating PS or PDF without that plug in? Please clarify if you can. I would like to make sure that what I am using is the right component for generating ps/pdf files. Thank you! /Gregorio -----Original Message----- From: Hussein Shafie <[email protected]> To: [email protected] Cc: [email protected] <[email protected]> Sent: Thu, May 20, 2010 3:32 am Subject: Re: [XXE] Convert to PDF? log [email protected] wrote: Im a relatively new user to XML Mind here, and if this topic is covered in the documentation, please point me to that. I scanned through this list archives going back several months and had not seen this issue there either. I suspect that this issue is more with Apache/FOP than XXE, but maybe there is some useful info here for the group. I am having a DocBook XML file fail to create PDF when trying to Convert to PDF (Convert to PS as well for that matter) It seems to be specific to this file. I can successfully create PS/PDF from other DocBook xml files, but this one is failing. I also ran the same file through the Apache 0.95 FOP and it also failed. However when I run it through an eval version of RenderX it renders the PDF just fine. I suspect that the XML Mind FO Converter plug in is the Apache as it states in the doc/docbook/docbook menu documentation. Though it clearly is the XML Mind FO Plug in on the addon menu. XMLmind XML Editor supports 3 XSL-FO processors, each one having its pecific plug-in (a very thin layer integrating the XSL-FO processor ith XMLmind XML Editor): [1] Apache FOP 0.95. Converts XSL-FO to PostScript and PDF. 2] RenderX XEP 4+. Converts XSL-FO to PostScript and PDF. 3] Our own product: XMLmind XSL-FO Converter 4.4. Converts XSL-FO to TF, WordprocessingML, .odt, .docx. You are almost certainly using [1]. > So my questions are: Is the same messages that I see during the 'executing command' window which scroll by really too fast to read when it is running, are these the same messages that then display in the ERROR dialog box that comes up? Yes. > If not - is there a log file written somewhere for further analysis? Even if these are same is there still an error log file? There is no log file per se, but you can very easily review all the essages displayed during 'executing command': Right-click on the status message area found at the bottom/left of the ain window in order to display the ``message logger'' dialog box, then elect "Command Execution" from the combobox of the dialog box. More info. here: ttp://www.xmlmind.com/xmleditor/_distrib/doc/help/statusTool.html > If there is an offending code, entity or sequence of codes, perhaps it is known and I can fix that in the file. What sort of errors would cause failure? I have seen several other files complain, with similar messages but they do not fail... what would be a fatal error? Seems the offending error is java.lang.NullPointerException does anyone know the cause? Finally is this not an XXE issue but rather an issue/bug with Apache? This happens from time to time with FOP. It's clearly an issue/bug in pache FOP. It is indeed triggered by something specific to your document. > If this is known issue or something I am sorry for bringing it up again. Any suggestions would be very welcome. I'm sorry but I don't remember why the same kind of problem happened to e with my own documents. It's generally easy, though tedious, to find a workaround for this kind f problem: comment out your document section by section and each time ou do that, convert the document to PDF. Do that until you find the `offending'' DocBook element. I would bet on a table, a footnote or a raphics file. - MLmind XML Editor Support List [email protected] ttp://www.xmlmind.com/mailman/listinfo/xmleditor-support
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
