> On Jun 30, 2015, at 12:43 AM, Radu Coravu <
radu_coravu@sync.ro> wrote:
>
> 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).
I see that emerge on gentoo wants me to upgrade:
[ebuild NS ] dev-java/fop-2.0 [1.1] USE="jai -doc -examples -hyphenation -source {-test}"
Given the concerns expressed here, that might be a little rash.
>
> 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