Unfortunately, proposed solutions do not help. FOP does not read configuration file on startup without explicit call of loading options in the code. It seems that XML Editor does not do such calls. I checked it by placing incorrect config.xml in the fop.jar -- FOP under XML Editor did not even notice it while standalone FOP breaks.
As for parameters, by specifying <parameter></parameter> it is possible to store string values (such as baseDir, baseFontDir), but not fonts. Sources of FOP pdf printer show that it expects value for "fonts" parameter to be a java object (actually, a list of java objects), not a string. It would be very cool if XMLMind would provide an option for configuring FOP fonts either directly in XXE config style or by specifying fop configuration file. Anyway, XXE is a cool tool for docbook typesetting, and this particular problem can be solved by starting FOP as an external application. Best regards, Nikolay Pakulin Institute for System Programming RAS mailto: npak at ispras.ru Phone: +7 (095) 912-5317(ext 4427) Fax : +7 (095) 912-1524 Web : http://unitesk.com/ http://www.ispras.ru/ -----Original Message----- From: Hussein Shafie [mailto:[email protected]] Sent: Tuesday, August 02, 2005 6:05 PM To: Nickolay Pakoulin Cc: xmleditor-support at xmlmind.com Subject: Re: [XXE] How to convert non-latin file using FOP plugin? Nickolay Pakoulin wrote: > I have a docbook file with some Cyrillics characters. When I convert > it to PDF using XMLEditor all cyrillics is presented as '#' in > generated pdf. The intermediate __doc.fo file preserves cyrillics, > but it is lost during fo->pdf transformation. > > I know how to solve the problem in standalone FOP: by specifying > custom fonts in configuration files. I failed to find any ways to > configure FOP plugin for XML Editor, maybe I am missing something? FOP can be configured by passing it parameters. * Edit <XXE_install_dir>/addon/config/docbook/xslMenu.incl. * Go to command docb.toPS. * The invocation of FOP looks like this: --- <processFO processor="FOP" file="__doc.fo" to="__doc.%0"> <parameter name="renderer">%0</parameter> <parameterGroup name="docb.toPS.FOPParameters" /> </processFO> --- * You can either: ** directly add one or more parameters after --- <parameter name="renderer">%0</parameter> --- ** OR, more elegant, define a "docb.toPS.FOPParameters" parameterGroup in your ~/.xxe/addon/customize.xxe --- <parameterGroup name="docb.toPS.FOPParameters"> <parameter name="param1">val1</parameter> <parameter name="param2">val2</parameter> <parameter name="param3">val3</parameter> ... </parameterGroup> --- Which parameter to add? Well, you need to consult FOP documentation for that. A parameter corresponds to the key/value of an entry in the configuration file. But I don't know if this is sufficient to solve your problem. If this is not sufficient, a possible (really dirty) workaround consists in replacing conf/config.xml by your own, modified, conf/config.xml in the fop.jar bundled with our plugin. --- PS: I'm not really sure that what I'm saying can be used to solve your problem. I've never tested this.
