Hi again,
> I'm sorry to learn that you find overkill the way we implemented
> conversion to PDF.
Oh, my love to DocBook never ends, so I want to gladden it everyday :)
> In fact, we didn't find any other way to do it which also solves the
> 2 following problems:
> [1] Be able to convert XML documents stored on a remote server (FTP,
> WebDAV, etc).
> [2] Conversion to PDF should work even when XXE is deployed using
> Java Web Start (everything is contained in .jar files cached by Java
> Web Start).
That's OK for me, but that doesn't make sense in 95% situations where
document is just file:/something/, and doesn't make sense at all for
callouts and admon that can be linked using "admon.graphics.path" set
to "'xxe-config:docbook/xsl/images/'" without copying. (Also you don't
detect whether I use SVG admon, do you ?)
I have plenty of documents that have various illustrations, etc., and
copying them together with their dependencies takes more than the
conversion itself though XXE :)
Also I miss very much option to open automatically output PDF! (This
would be very usefull)
So I believe you can handle this 2 ways:
1) Use /tmp just for intermediate .fo file (single file), and
automatically set "base-dir" of FOP to base path of the document no
matter it is file:/... ftp:/... or anything, then all the relative
urls will be relative to document placement, AFAIK FOP handles quite
well xml-config: ftp: and so on, so it should work with remote
documents as well
2) Use the same method as 1) but instead of setting "base-dir" set
current working directory ("base-dir" is by default CWD)
3) Use point 1) method only for documents whose URLs are file:/ (local)
4) Use point 1) method triggered in the XXE configuration like [X]
Copy files to local temporary folder before FO processing
>> 3) Files & paths specified in .xxe/addon/customize.xxe should be
>> relative to .xxe/addon/customize.xxe but they're not in all cases,
>> <cfg:parameter name="configuration"> is relative to /Applications
>> on my Mac and C:\Program Files\XXE\bin on Windows (I think this is
>> a bug)
Can you confirm this?
Regards,
--
Adam Strzelecki |: nanoant.com :|
