The PDF is not rendered whole


I've tried to render fo document using FO.NET and the result is rendered not whole. Every page is rendered only to halb. I've used the FOP for same document, and all went OK. I've attached the document and outputs. Can you help me find the problem.
Thanks in advance, Tomas Studva
My log:
 [xslt] Processing D:\**** to ****
 [xslt] Loading stylesheet D:****rotationReport.xslt
 [exec] [INFO] Building formatting object tree
 [exec] [WARN] Will ignore TrueType font 'Symbol' because a base 14 font with the same name already exists.
 [exec] [INFO] [1]
 [exec] [INFO] [2]
 [exec] [INFO] Last page-sequence produced 2 page(s).
 [exec] [INFO] [3]
 [exec] [INFO] [4]
 [exec] [INFO] Last page-sequence produced 2 page(s).
 [exec] [INFO] Parsing of document complete, stopping renderer
 [exec] Took 656 ms.

file attachments


studva wrote Mar 11, 2009 at 12:18 PM

The PDF generated by FO.NET wans't readable only in adobe Acrobat 7.0. profession.

esky wrote Mar 30, 2009 at 10:38 PM

Yes I am finding the same thing, FO.NET doesn't work for Adobe Reader 7.0. I can't open pdf documents generated by FO.NET using adobe reader 7.0, 8.0 and up works fine.

wrote Mar 31, 2009 at 6:15 AM

deeds wrote Apr 8, 2009 at 12:49 AM

Did you manage to resolve this? I am having the same problem.. The complete PDF is not rendered.

wrote Apr 8, 2009 at 12:50 AM

studva wrote Apr 10, 2009 at 8:20 AM

My solution of this problem was to switch to another rendering engine. I've switched to Java Apache FOP renderer, it works without such a problem. You can also try using NFOP, if you got stucked in .NET platform, but I haven't tried this way. Tomas

deeds wrote Apr 11, 2009 at 6:34 AM

Thanks for your reply.
I will try NFOP...Wanted to keep the application completely .NET

Decmac wrote Oct 3, 2009 at 5:20 AM

This is such a pity. The FoNet renderer is much more performant than the nFop implementation and only a single dll dependency top drawer. However not working in Adobe Reader 7.0 and 7.1 is a serious problem for me as I wanted to put this in a corporate roll out of about 10k pcs but guess what they are using Adobe Reader 7 and not a simple matter of telling them to upgrade. Please escalate and fix this

rjseventythree wrote Nov 29, 2009 at 11:40 PM

If this issue is not going to be resolved quickly, can we please put this on the front page or in the FAQ as it is a potential show-stopper for those of us trying to maximise compatibility. Our decision to use this library (over nfop, which does not work on 64-bit servers) would have been affected had we been immediately aware of this issue.

If anyone has a work around for this or a fix please let me know as soon as possible, thank you.

As mentioned above, this is a serious problem for me too and the rest of this package runs circles around other free renderers for .net.

wrote Nov 30, 2009 at 12:33 AM

wrote Jun 21, 2011 at 11:10 AM

griffm wrote Aug 5, 2011 at 8:20 AM

Hello all. Sorry for not spotting this issue when it was reported a couple of years ago, I have now enabled notifications for "Issues". It sounds like this was a problem that affected Acrobat 7 only - I can't download that version to confirm. In any case, there has been a patch submitted that can be used by anybody who still needs to target that version of Acrobat. In the meantime, I will study the patch and might incorporate it into the main codebase.

wrote Feb 21, 2013 at 11:01 PM

happycujo wrote Feb 27, 2013 at 4:39 PM

Will this issue is not reproductible on the latest version of acrobat, it can reproduced fairly easily with other viewer, such as google chrome internal viewer.

HTML sample to open with chrome
<a href="pdf.pdf">PDF</a>

I would like to work on this issue as we are planning to use fo.net. This is for us a major concern. Could someone direct us toward the classes to look in the code for this issue? Any technical help would be appreciated!

happycujo wrote Mar 5, 2013 at 2:56 PM

Google Chrome has fixed its rendering issue that was occuring in the PDF internal viewer. the latest version canbe tested here.


The issue seems not to be related to fo.net, but to their reader implementation.