Re: Thinking of Using XMLMind - Eval in progress.
Hussein Shafie <[email protected]> Wed, 18 May 2016 12:15:44 +0200
| Newsgroups | gmane.text.xml.xfc.general |
|---|---|
| Message-ID | <[email protected]> |
On 05/18/2016 10:23 AM, Steve Parry wrote: > Hi we have an application that currently uses FOP to generate PDF and > now have a requirement to generate RTF (Word editable files etc…) and > are looking at XMLMind. > > This will be integrated into our application, I’ve put together a POC > and generated simple documents successful (provided that the evaluation > code is intended to make some changes to the text showing as spelling > errors). The *only* difference between Evaluation Edition and Professional Edition is: --- Note that Evaluation Edition is useless for any purpose other than evaluating XMLmind XSL-FO Converter. This edition generates output containing random duplicate letters. (Of course, this does not happen with Professional Edition!) --- ( Excerpts from "About Evaluation Edition" in http://www.xmlmind.com/foconverter/downloadeval.shtml ) Hence the very large number of spelling errors. > > The questions I have are; > > 1)Does it support UTF8 I tried changing the encoding from cp1252 but it > wouldn’t take UTF8 (is that just the eval version?) No, RTF output just supports: ASCII, Cp1250 (Windows Eastern European), Cp1251 (Windows Cyrillic) and Cp1252 (Windows Latin-1). This is documented here: http://www.xmlmind.com/foconverter/_distrib/doc/user/command_line_java.html Please note that we don't plan to improve our RTF support as nowadays, the vast majority of our customers are interested only in the DOCX output. > > 2)We have embedded image in external-graphics tags where the source is > represented as file://[path to file] these are not resolving and causes > the conversion to fail (again is this just a limitation of the eval or > is it a limitation of XMLMind XSL-FO to RTF Integrated Converter) There is no known bug related to external-graphics. Moreover in principle, a problem with external-graphics can cause the conversion to report warnings, not to fail. Please refer to this FAQ: http://www.xmlmind.com/foconverter/faq.html#image_not_showing --- My .fo file contains a fo:external-graphic element which points to an existing JPEG file, but this image is not showing in the document generated by XFC. Are there known bugs related to image support in XFC? --- If you cannot solve the issue after reading the FAQ, please do not hesitate to send us a sample ".fo" file + sample graphic files causing the conversion to fail. -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support