nFop 问题/替代方案
我需要一个免费的 .net XSL-FO 处理器，并初步测试了 nfop 的功能。我发现了一些缺点，这些缺点对我满足项目的要求非常重要。
我遇到的问题是：
- SVG 不渲染
水印功能基本上不可能渲染 - 主体在所有其他面板之前渲染，没有 SVG（上图）并且没有文本旋转
keep-together 属性未实现* (http://www.w3schools.com/xslfo/prop_keep-together.asp)
第三点特别重要烦人的是，我通过使用 iTextSharp 并随后编辑 PDF（混乱）找到了上述一些问题（1,2）的解决方法。
我的问题是：
- 上述问题是否有解决方法？
- 人们在使用 nfop 时还遇到过哪些其他问题？
- .net 是否有替代的 XSL FO 处理器？
I require a free .net XSL-FO processor and have initially tested nfop's functionality. I have found some shortcomings which are significant in allowing me to meet the requirements for my project.
The issues I have encountered are:
- SVG do not render
watermark functionality is basically impossible to render - body renders before all other panels, no SVG (above) and no text rotation
keep-together attribute is not implemented* (http://www.w3schools.com/xslfo/prop_keep-together.asp)
The third point is particularly annoying, I have found workarounds for some of the above issues(1,2) by using iTextSharp and editing the PDF afterwards (messy).
My questions are:
- Are there workarounds for any of the issues mentioned above?
- What other issues have people encountered with nfop?
- Are there alternative XSL FO processors for .net?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
需要考虑的具有.NET接口的其他FOP引擎：
FOP 标准合规性和错误/问题的级别因 FOP 引擎而异，因此我建议在开发时使用多个 FOP 引擎（许多提供试用版）以确定您的 FOP 是否存在问题或渲染引擎的错误/问题。
Other FOP engines with .NET interfaces to consider:
The level of FOP standards compliance and bugs/issues varies between FOP engines, so I would recommend using several FOP engines(many offer trial versions) when developing in order to determine if there is a problem with your FOP or a bug/issue with your rendering engine.
我找到了一种解决保持在一起属性问题的方法。
我没有使用此属性，而是使用以下方法将表行元素链接在一起：
上述属性似乎已实现。
我使用以下网站作为参考：
http://www.ibm.com/developerworks/xml/ Library/x-tippgbk/index.html
我仍然想听听 nfop 的其他问题/解决方法/替代方案。
I have found 1 work around for the keep-together attribute issue.
Instead of using this attribute, I chain table-row elements together using:
The above attribute appears to be implemented.
I used the following site as a reference:
http://www.ibm.com/developerworks/xml/library/x-tippgbk/index.html
I still would like to hear other issues/workarounds/alternatives for nfop.
谢谢你的回答，麦兹。
不幸的是，由于预算限制等原因，这些选项对我来说不可用。
我将不得不使用 iTextSharp 并随后手动添加水印（是的）。
Thanks for your answer Mads.
Unfortunately those options are unavailable to me, due to budget constraints and what-not.
I will have to use iTextSharp and add in the watermark afterward manually (yay).
好吧，这只小狗再次抬起了头，我遇到了“将块保持在同一页上”的问题。
我发现
工作有魅力。
Well this puppy reared its head again and I was confronted with the "keeping blocks on the same page" issue.
I found
worked a charm.