Well errors in general are reported as they occur, that said a strange one
like a "java crash" -- i.e. the bug you hit, one could not guarantee
anything.
It is very rare if at all that you would get an error in the final stage (to
PDF). The reason is that normally it is RenderX generating the output tree
to feed into the backend. Some errors that could occur in that step could be
inclusion of an image as a PDF and that PDF is broken. It is possible that
the PDF itself would not be parsed for inclusion into the document until
that time. Also, many customers have implemented custom post-processing of
the serialized tree output (XEP format) and then feed that back into the
software to do special things.
With such techniques, you can feather pages, apply barcodes that are based
on unknown values like page counts, or perform bookfolding, inject
backgrounds, apply OMR marks, ... Of course, it is possible that the code
builds incorrect XEP format and hence causes the backend process to fail.
Kevin Brown
RenderX
-----Original Message-----
From: xep-support-bounces@renderx.com
[mailto:xep-support-bounces@renderx.com] On Behalf Of dvint@dvint.com
Sent: Tuesday, August 20, 2013 3:02 PM
To: RenderX Community Support List
Subject: [xep-support] [SPAM] Re: Re: Troubleshooting DITA environment and
output
That did the trick thanks. Went back to the original FO that was generated
by the DITA OT and XEP produced the file without any modifications.
Kevin, do you have any insights on how close the errors are reported to
their actual location based upon the last page number displayed?
> Thanks, I'll give it a try. I just deleted all the WARNed about links
> and was able to produce the PDF file.
>
>
>> Dan:
>>
>> There was a version of software in the shop briefly that had a few
>> errors in processing of page numbers. I see you downloaded around
>> that time (it was released August 8).
>>
>> Please upload the key and download the version that is in the shop now:
>>
>> http://www.renderx.com/download/updates.html
>>
>> Test again and see if this is not the issue.
>>
>>
>> Kevin Brown
>> Executive Vice President, Sales & Marketing RenderX, Inc.
>> (650) 327-1000 Direct
>> (650) 328-8008 Fax
>> (925) 395-1772 Mobile
>> skype:kbrown01
>> kevin@renderx.com
>> sales@renderx.com
>> http://www.renderx.com
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: xep-support-bounces@renderx.com
>> [mailto:xep-support-bounces@renderx.com] On Behalf Of dvint@dvint.com
>> Sent: Tuesday, August 20, 2013 1:40 PM
>> To: xep-support@renderx.com
>> Subject: [xep-support] Troubleshooting DITA environment and output
>>
>> I've been trying to troubleshoot some problems within our content and
>> the resulting FO that is generated by the DITA OT and the various
>> formatting engines that I have been testing.
>>
>> Here are the results/issues I've found, question to follow:
>>
>> - Using the default FOP I have several tables that report problems.
>> What I have seen are mostly related to a mismatch in the number of
>> columns in the table and the number of colspecs defined. FOP reports
>> this and indicates that the auto layout is not supported.
>>
>> - We switched to a trial of Antenna House and it seems to power
>> through the table issues and just issues warnings about 40 links that
>> are to non-DITA types and wants the format attribute specified. These
>> manifest as
>> warning:
>> [warning] unresolved internal destination: 'unique_2518_Connect_42_how'
>> [warning] unresolved internal destination:
>> 'unique_2518_Connect_42_examples'
>> AH does produce a PDF file that looks complete.
>>
>> - When I try the same FO file with XEP we seem to get past the table
>> issues and get the same warnings as AH, but we get near the end and
>> receive a formatting failure:
>> (generate [output-format
>> pdf][1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][1
>> 9][20][
>> 21][22][23][24]
>> [error] formatting failed
>> [error] java.lang.NullPointerException
>>
>> Any idea what would be causing this to fail completely? It has been
>> some time since I have worked with XEP, but it seems like I'm at the
>> stage where we are writing out the actual PDF pages. How accurate is
>> the counter vs where the actual problem might be? I'm looking at the
>> AH output around pages
>> 25-30 and I'm only finding xrefs that are producing page numbers, so
>> I don't think I have any of my link warnings in this area (I'll be
>> checking further on this), so what else should I be searching for?
>> Any ideas on how to debug this problem?
>>
>> I'm using the x4u utility at the moment, quoted error text is from
>> the output window. I don't see any errors in the command window that
>> made the java call.
>>
>> This is a 3,177 page document when produced. I had to bump the stack
>> heap space to 4096m to get it to this point in the process.
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> (*) To unsubscribe, please visit
>> http://lists.renderx.com/mailman/options/xep-support
>> (*) By using the Service, you expressly agree to these Terms of
>> Service http://w ww.renderx.com/terms-of-service.html
>>
>> _______________________________________________
>> (*) To unsubscribe, please visit
>> http://lists.renderx.com/mailman/options/xep-support
>> (*) By using the Service, you expressly agree to these Terms of
>> Service http://w ww.renderx.com/terms-of-service.html
>>
>
>
>
>
>
>
> _______________________________________________
> (*) To unsubscribe, please visit
> http://lists.renderx.com/mailman/options/xep-support
> (*) By using the Service, you expressly agree to these Terms of Service
> http://w
> ww.renderx.com/terms-of-service.html
>
***SPAM***
!DSPAM:87,5213e7769851931932425!
_______________________________________________
(*) To unsubscribe, please visit
http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service
http://w
ww.renderx.com/terms-of-service.html
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
Received on Tue Aug 20 15:14:44 2013
This archive was generated by hypermail 2.1.8 : Tue Aug 20 2013 - 15:14:44 PDT