XEP and oXygen?
Are you missing a feature? Request its implementation here.
XEP and oXygen?
I don't know enough about Java to know whether it's possible to use RenderX's (http://http://xep.xattic.com/) Java XSL-FO processor XEP (sorry about the density of jargon!) with oXygen... so... has anyone gotten it to work, and if so, what do I need to do (i.e., among other things, what do I enter in the Configure Transformation > FOP tab > External FO Processors > Command Line box)? Thanks!!!
We tried to run XEP as a post processor, but it has the drawback of generating the output pdf in the same directory as the input FO, with the same name and appending the ".pdf" extension.
The command line in the external FO processor shold point to the batch file that starts XEP. For example, if the you have installed XEP in:
C:\XEP, you have to put in the command line:
C:\XEP\run.bat $2
The $2 macro is replaced by the editor with the FO file.
For more info, read the XEP user guide, section"Command line interface to XEP"
The command line in the external FO processor shold point to the batch file that starts XEP. For example, if the you have installed XEP in:
C:\XEP, you have to put in the command line:
C:\XEP\run.bat $2
The $2 macro is replaced by the editor with the FO file.
For more info, read the XEP user guide, section"Command line interface to XEP"
XEP how-to for OS X
Thanks for the help! Incidentally, I'm using Mac OS X 10.2.4 with JDK 1.4.1. After reading through more documentation, and some experimentation, I was able to get it to work without the limitation you identified.
Assuming that XEP is in /Applications/XEP
Step 1: copy/move the files (xt.jar, saxon.jar, cryptix32.jar, cryptix32-pgp.jar, xep323_trial.jar) which are in /Applications/XEP/lib to ~/Library/Java/Extensions
Step 2: To make the run.sh script executable, type the following at a terminal prompt:
%chmod +x /Applications/XEP/run.sh
Step 3: in oXygen, set the command line for an External FO processor to /Applications/XEP/run.sh $2, and make sure you've got the appropriate FOP "Input" and Output "Save As" values.
Alternatively, using syntax such as the following in the terminal works:
%java com.renderx.xep.XSLDriver -fo ~/Desktop/source.fo -pdf ~/Desktop/output.pdf
If there are any mistakes in what I've posted, please point them out...
Assuming that XEP is in /Applications/XEP
Step 1: copy/move the files (xt.jar, saxon.jar, cryptix32.jar, cryptix32-pgp.jar, xep323_trial.jar) which are in /Applications/XEP/lib to ~/Library/Java/Extensions
Step 2: To make the run.sh script executable, type the following at a terminal prompt:
%chmod +x /Applications/XEP/run.sh
Step 3: in oXygen, set the command line for an External FO processor to /Applications/XEP/run.sh $2, and make sure you've got the appropriate FOP "Input" and Output "Save As" values.
Alternatively, using syntax such as the following in the terminal works:
%java com.renderx.xep.XSLDriver -fo ~/Desktop/source.fo -pdf ~/Desktop/output.pdf
If there are any mistakes in what I've posted, please point them out...
com.renderx.xep.Driver (wrapped into run.sh/run.bat) is kept for compatibility. Use com.renderx.xep.XSLDriver and xep.bat/xep.sh instead. The command line options it
provides is more than enough for command-line applications.
java com.renderx.xep.XSLDriver
-help
| {option} {-quiet|-version|-valid}
(
[-xml] <infile> [-xsl <stylesheet>] {-param <name=value>}
| -fo <infile>
| -xep <infile>
)
[[-<output format>] <outfile>]
[-format <output format>]
Available output formats: ps (Postscript), pdf (PDF), xep (XEP), at (XEP).
provides is more than enough for command-line applications.
java com.renderx.xep.XSLDriver
-help
| {option} {-quiet|-version|-valid}
(
[-xml] <infile> [-xsl <stylesheet>] {-param <name=value>}
| -fo <infile>
| -xep <infile>
)
[[-<output format>] <outfile>]
[-format <output format>]
Available output formats: ps (Postscript), pdf (PDF), xep (XEP), at (XEP).
-
- Posts: 2
- Joined: Wed Oct 24, 2007 5:49 pm
Java RenderX
Post by steveo06360 »
There is an article at http://www.integrityintegrators.net/art ... lining.htm. In there they show a java class called FOPThread.
I modified this class and renamed it RenderXThread and only had to change about 4 lines of code to make it work with RenderX
I modified this class and renamed it RenderXThread and only had to change about 4 lines of code to make it work with RenderX
-
- Posts: 2
- Joined: Wed Oct 24, 2007 5:49 pm
Bad URL
Post by steveo06360 »
Try this url instead:
http://www.integrityintegrators.net/art ... lining.htm
Those little periods are nasty little buggers.
http://www.integrityintegrators.net/art ... lining.htm
Those little periods are nasty little buggers.
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service