fo2pdf --> Oxygenxml

Doc/Sda1/fo.xml

@@ -108,28 +108,21 @@
     xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>
     document</title>
 
-    <titleabbrev>Simple <abbrev
-    xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev></titleabbrev>
+    <titleabbrev>Simple <xref linkend="glo_FO"/></titleabbrev>
 
     <para>A renderer for printed output from XML content also needs
     instructions how to format the different elements. A common way to define
     these formatting properties is by using <emphasis>Formatting
-    Objects</emphasis> (<abbrev
-    xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>)
-    standard. <abbrev
-    xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>
-    documents may be compared to HTML. A HTML document has to be rendered by a
-    piece of software called a browser in order to be viewed as an image.
-    Likewise <abbrev
-    xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>
-    documents have to be rendered by a piece of software called a formatting
-    objects processor which typically yields PostScript or PDF output. As a
-    starting point we take a simple example:</para>
+    Objects</emphasis> (<xref linkend="glo_FO"/>) standard. <xref
+    linkend="glo_FO"/> documents may be compared to HTML. A HTML document has
+    to be rendered by a piece of software called a browser in order to be
+    viewed as an image. Likewise <xref linkend="glo_FO"/> documents have to be
+    rendered by a piece of software called a formatting objects processor
+    which typically yields PostScript or PDF output. As a starting point we
+    take a simple example:</para>
 
     <figure xml:id="foHelloWorld">
-      <title>The most simple <abbrev
-      xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>
-      document</title>
+      <title>The most simple <xref linkend="glo_FO"/> document</title>
 
       <programlisting language="xml">&lt;?xml version="1.0" encoding="utf-8"?&gt;
 &lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
@@ -148,21 +141,14 @@
     &lt;/fo:flow&gt;
   &lt;/fo:page-sequence&gt;
 &lt;/fo:root&gt;</programlisting>
-    </figure>
 
-    <para>PDF generation is initiated by executing a <abbrev
-    xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>
-    processor. At the MI department the script <code>fo2pdf</code> invokes
-    <orgname>RenderX</orgname>'s <productname
-    xlink:href="http://www.renderx.com">xep</productname> processor:</para>
-
-    <programlisting language="none">fo2pdf -fo hello.fo -pdf hello.pdf</programlisting>
-
-    <para>This creates a PDF file which may be printed or previewed by e.g.
-    <productname xlink:href="http://www.adobe.com">Adobe</productname>'s
-    acrobat reader or evince under Linux. For a list of command line options
-    see <productname xlink:href="http://www.renderx.com/reference.html">xep's
-    documentation</productname>.</para>
+      <para>The <productname>Oxygenxml</productname> <xref linkend="glo_IDE"/>
+      supports <xref linkend="glo_FO"/> to <xref linkend="glo_PDF"/>
+      conversion. You may optionally pipe a <xref linkend="glo_XSL"/>
+      transformation result to a <xref linkend="glo_FO"/> processor by
+      defining a single transformation scenario. Watch out for the <quote>Fo
+      Processor</quote> tab.</para>
+    </figure>
   </section>
 
   <section xml:id="layoutParam">
@@ -172,9 +158,8 @@
     very impressive. In order to develop more elaborated examples we have to
     understand the underlying layout model being defined in a <link
     xlink:href="http://www.w3.org/TR/xsl/#fo_simple-page-master">fo:simple-page-master</link>
-    element. First of all <abbrev
-    xlink:href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo-section">FO</abbrev>
-    allows to subdivide a physical page into different regions:</para>
+    element. First of all <xref linkend="glo_FO"/> allows for subdividing a
+    physical page into different regions:</para>
 
     <figure xml:id="foRegionList">
       <title>Regions being defined in a page.</title>

ws/Docbook/Config/xxe6/spell/dict_en.txt

@@ -17,6 +17,7 @@ no-brainer
 passphrases	
 plugin	
 plugins	
+pregenerated	
 pythagorean	
 serializer	
 Unicode