Author: jeremias
Date: Mon Jan 28 23:30:08 2008
New Revision: 616191
URL: http://svn.apache.org/viewvc?rev=616191&view=rev
Log:
A more detailed comment on RTF output explaining that RTF has limitations
besides the incomplete implementation on the FOP side.
Modified:
xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
URL:
http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml?rev=616191&r1=616190&r2=616191&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
(original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml Mon
Jan 28 23:30:08 2008
@@ -661,8 +661,14 @@
<p>
JFOR, an open source XSL-FO to RTF converter has been integrated into
Apache FOP.
This will create an RTF (rich text format) document that will
- attempt to contain as much information from the fo document as
- possible. The RTF output follows Microsoft's RTF specifications
+ attempt to contain as much information from the XSL-FO document as
+ possible. It should be noted that is not possible (due to RTF's
limitations) to map all
+ XSL-FO features to RTF. For complex documents, the RTF output will never
reach the feature
+ level from PDF, for example. Thus, using RTF output is only recommended
for simple documents
+ such as letters.
+ </p>
+ <p>
+ The RTF output follows Microsoft's RTF specifications
and produces best results on Microsoft Word.
</p>
<note>RTF output is currently unmaintained and lacks many features compared
to other output
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
