|
Radu,
That says a lot! It seems like a simple fix to me. I wonder why they let it
out of the gate that way? That's a major bug.
I will probably wait as well since I have no interest in maintaining a
patch in our system and the time between FOP updates is usually quite a long
time.
Thanks for your input!
Dean Nelson
In a message dated 6/29/2015 10:44:18 P.M. Pacific Daylight Time,
radu_coravu@sync.ro writes:
Hi
Dean,
If it's worth anything, I stumbled upon the same problem when
converting
DITA to PDF using Apache FOP 2.0 (the bug I posted was marked
as a
duplicate as yours):
>
https://issues.apache.org/jira/browse/FOP-2479
After I made a patch to
guard the NPE I successfully translated our
user's manual's 1000+ pages to
PDF.
But that left me with a bitter test of the initial Apache FOP 2.0
encounter.
I will probably wait for 2.1 before I integrate it into our
product
(Oxygen XML Editor).
Regards,
Radu
Radu
Coravu
<oXygen/> XML Editor, Schema Editor and XSLT
Editor/Debugger
http://www.oxygenxml.com
On 6/30/2015 2:19 AM,
DeanNelson@aol.com wrote:
> Hello
> I have tried to update our
production documentation system to FOP 2.0
> but in doing so I
discovered a little problem that prevented the use of
> FOP 2.0. I get
an exception and cannot get around it without recompiling
> with a fix.
(See https://issues.apache.org/jira/browse/FOP-2461 )
> I am interested
in other people's experience in using FOP 2.0. In your
> experience, is
it really ready for prime time? Are you using it
> successfully?
>
I'm using the 1.78.1 stylesheets with Docbook 4.5.
> Regards,
>
Dean
Nelson
-
---------------------------------------------------------------------
To
unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For
additional commands, e-mail:
docbook-apps-help@lists.oasis-open.org
|