A more detailed comment on RTF output explaining that RTF has limitations besides the incomplete implementation on the FOP side.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@616191 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 8 insertions, 2 deletions

diff --git a/src/documentation/content/xdocs/trunk/output.xml b/src/documentation/content/xdocs/trunk/output.xml
index 7a2a79862..663168a3c 100644
--- a/src/documentation/content/xdocs/trunk/output.xml
+++ b/src/documentation/content/xdocs/trunk/output.xml
@@ -661,8 +661,14 @@ out = proc.getOutputStream();]]></source>
   <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