Update 1.1rc1 release date to 2012-07-02 (post-dated to accommodate vote and release...

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-1_1rc1@1353225 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/README b/README
index 23b91c78d29f497d303b5fc45ae08b67834285d5..0fc91455d41d4c448186a9938bedb569b55272fd 100644 (file)
--- a/README
+++ b/README
@@ -94,7 +94,7 @@ http://xmlgraphics.apache.org/fop/stable/running.html
 ==============================================================================
 
 Version 1.1rc1
-===========
+==============
 
 This is a candidate release of the next,  minor (dot) release of Apache FOP,
 which primarily addresses bug fixes and also adds a number of new features.
@@ -120,7 +120,7 @@ Major Changes in Version 1.1rc1
   either bidirectional processing or advanced typographic tables in
   fonts (e.g., the GSUB and GPOS tables of OpenType).
 * Adds support for fo:bidi-override and (relatively) full support
-  for writing-mode='tb-rl' (or equivalent).
+  for writing-mode='rl-tb' (or equivalent).
 * Adds support for Unicode BIDI Control characters: U+200E LEFT-TO-RIGHT
   MARK (LRM), U+200F RIGHT-TO-LEFT MARK (RLM), U+202A LEFT-TO-RIGHT EMBEDDING
   (LRE), U+202B RIGHT-TO-LEFT EMBEDDING (RLE), U+202D LEFT-TO-RIGHT OVERRIDE

diff --git a/lib/xmlgraphics-commons-1.5rc1.jar b/lib/xmlgraphics-commons-1.5rc1.jar
index a8733f14cd9a1a2330523ee235ec016366ab5840..7de03ff74cb76ac01d3eaf04c72ada899712f771 100644 (file)
Binary files a/lib/xmlgraphics-commons-1.5rc1.jar and b/lib/xmlgraphics-commons-1.5rc1.jar differ

diff --git a/src/documentation/content/doap.rdf b/src/documentation/content/doap.rdf
index dfac6ff9859b08865d294070db527c26534911fc..98c505747564f4a2cd25c3bd0d63dcbdcbef620f 100644 (file)
--- a/src/documentation/content/doap.rdf
+++ b/src/documentation/content/doap.rdf
@@ -77,7 +77,7 @@
     <release>
       <Version>
         <name>Upcoming release (candidate)</name>
-        <created>2012-06-03</created>
+        <created>2012-07-02</created>
         <revision>1.1rc1</revision>
       </Version>
     </release

diff --git a/src/documentation/content/xdocs/1.1rc1/complexscripts.xml b/src/documentation/content/xdocs/1.1rc1/complexscripts.xml
index c622fe192ba6f25b5d5b37cfda0aa34a8159fb4b..69720553139523435c7a144396a6e81f4e7ad5fd 100644 (file)
--- a/src/documentation/content/xdocs/1.1rc1/complexscripts.xml
+++ b/src/documentation/content/xdocs/1.1rc1/complexscripts.xml
@@ -26,7 +26,7 @@
       <title>Overview</title>
       <p>
         This page describes the
-        <a href="http://en.wikipedia.org/wiki/Complex_scripts">complex scripts</a>
+        <link href="http://en.wikipedia.org/wiki/Complex_scripts">complex scripts</link>
         features of Apache™ FOP, which include:
       </p>
       <ul>
@@ -80,16 +80,16 @@
         sufficient. In these cases, an author may make use of the following XSL-FO constructs:
       </p>
       <ul>
-        <li>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#script"><code>script</code></a> property.</li>
-        <li>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#language"><code>language</code></a> property.</li>
-        <li>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#writing-mode"><code>writing-mode</code></a> property.</li>
+        <li>The <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#script"><code>script</code></link> property.</li>
+        <li>The <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#language"><code>language</code></link> property.</li>
+        <li>The <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#writing-mode"><code>writing-mode</code></link> property.</li>
         <li>The number to string conversion properties:
-          <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#format"><code>format</code></a>,
-          <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-separator"><code>grouping-separator</code></a>,
-          <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-size"><code>grouping-size</code></a>,
-          <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#letter-value"><code>letter-value</code></a>,
+          <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#format"><code>format</code></link>,
+          <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-separator"><code>grouping-separator</code></link>,
+          <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-size"><code>grouping-size</code></link>,
+          <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#letter-value"><code>letter-value</code></link>,
           and <code>fox:number-conversion-features</code>.</li>
-        <li>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override"><code>fo:bidi-override</code></a> element.</li>
+        <li>The <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override"><code>fo:bidi-override</code></link> element.</li>
         <li>Explicit bidirectional control characters: U+200E LRM, U+200F RLM, U+202A LRE,
           U+202B RLE, U+202C PDF, U+202D LRO, U+202E RLO.</li>
         <li>Explicit join control characters: U+200C ZWNJ and U+200D ZWJ.</li>
@@ -107,7 +107,7 @@
         </p>
         <ol>
           <li>If the FO element that governs the text specifies a
-            <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#script"><code>script</code></a>
+            <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#script"><code>script</code></link>
             property and its value is not the empty string or <code>"auto"</code>, then that script is used.</li>
           <li>Otherwise, the dominant script of the text is determined automatically by finding the
             script whose constituent characters appear most frequently in the text.</li>
@@ -115,8 +115,8 @@
         <p>In case the automatic algorithm does not produce the desired results, an author may
           explicitly specify a <code>script</code> property with the desired script. If specified,
           it must be one of the four-letter script code specified in
-          <a href="http://unicode.org/iso15924/iso15924-codes.html">ISO 15924 Code List</a> or
-          in the <a href="#extended_script_codes">Extended Script Codes</a> table.  Comparison
+          <link href="http://unicode.org/iso15924/iso15924-codes.html">ISO 15924 Code List</link> or
+          in the <link href="#extended_script_codes">Extended Script Codes</link> table.  Comparison
           of script codes is performed in a case-insensitive manner, so it does not matter what case
           is used when specifying these codes in an XSL-FO document.</p>
         <section id="standard_script_codes">
@@ -335,28 +335,94 @@
           language specific processing rules to be applied. For example, a font designed for the Arabic script may support
           typographic variations according to whether the written language is Arabic, Farsi (Persian), Sindhi, Urdu, or
           another language written with the Arabic script. In order to apply these language specific features, the author
-          may explicitly mark the text with a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#language"><code>language</code></a>
+          may explicitly mark the text with a <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#language"><code>language</code></link>
           property.</p>
         <p>When specifying the <code>language</code> property, the value of the property must be either an
-          <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes">ISO639-2 3-letter code</a> or an
-          <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO639-1 2-letter code</a>.  Comparison of language
+          <link href="http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes">ISO639-2 3-letter code</link> or an
+          <link href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO639-1 2-letter code</link>.  Comparison of language
           codes is performed in a case-insensitive manner, so it does not matter what case is used when specifying these
           codes in an XSL-FO document.</p>
       </section>
       <section id="writing_mode_property">
         <title>Writing Mode Property</title>
+        <p>The <code>writing-mode</code> property is used to determine the axes and direction of the inline
+          progression direction, the block progression direction, the column progression direction (in tables
+          and flows), the shift direction, region placement, the resolution of writing-mode relative property
+          values (such as start, end, before, after), and the default block (paragraph) bidirectionality
+          level.
+        </p>
+        <p>The <code>writing-mode</code> property is inherited, so it can appear on any XSL-FO element type; however,
+          it applies (semantically) only to the following element types:
+        </p>
+        <ul>
+          <li><code>fo:page-sequence</code></li>
+          <li><code>fo:simple-page-master</code></li>
+          <li><code>fo:region-*</code></li>
+          <li><code>fo:block-container</code></li>
+          <li><code>fo:inline-container</code></li>
+          <li><code>fo:table</code></li>
+        </ul>
+        <p>If it is not specified on one of these element types, but is specified on an ancestor element, then the value specified on that
+          ancestor element (the inherited value) is used; otherwise, the initial value <code>lr-tb</code> is used.</p>
+        <p>At present, only the following values of the <code>writing-mode</code> property are supported:</p>
+        <ul>
+          <li><code>lr-tb</code></li>
+          <li><code>rl-tb</code></li>
+          <li><code>lr</code></li>
+          <li><code>rl</code></li>
+        </ul>
+        <p>Writing modes that employ a vertical inline progression direction are not yet supported.</p>
       </section>
+      <!-- [TBD] - NEED TO DOCUMENT
       <section id="number_conversion_properties">
         <title>Number Conversion Properties</title>
       </section>
+      -->
       <section id="bidi_override_element">
         <title>Bidi Override Element</title>
+        <p>The <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override"><code>fo:bidi-override</code></link>
+          element may be used to override default bidirectional processing behavior,
+          including default embedding levels and default character directionality. In the absence of either this element
+          or use of explicit <link href="#bidi_controls">Bidi Control Characters</link>, the default behavior prescribed
+          by the <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</link>
+          applies.
+        </p>
       </section>
       <section id="bidi_controls">
         <title>Bidi Control Characters</title>
+        <p>In addition to the use of the <link href="#bidi_override_element">Bidi Override Element</link>, an author
+          may make use of the following explicit Unicode Bidi Control Characters:</p>
+        <ul>
+          <li>U+200E - LEFT-TO-RIGHT MARK (LRM)</li>
+          <li>U+200F - RIGHT-TO-LEFT MARK (RLM)</li>
+          <li>U+202A - LEFT-TO-RIGHT EMBEDDING (LRE)</li>
+          <li>U+202B - RIGHT-TO-LEFT EMBEDDING (RLE)</li>
+          <li>U+202C - POP DIRECTIONAL FORMATTING (PDF)</li>
+          <li>U+202D - LEFT-TO-RIGHT OVERRIDE (LRO)</li>
+          <li>U+202E - RIGHT-TO-LEFT OVERRIDE (RLO)</li>
+        </ul>
+        <p>If an embedding or override is not terminated (using U+202C PDF) prior to the end of a
+          <link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#d0e4879">delimited text range</link>,
+          then it is automatically terminated by FOP.
+        </p>
       </section>
       <section id="join_controls">
         <title>Join Control Characters</title>
+        <p>In order to prevent joining behavior in contexts where joining occurs by default,
+          for example, between U+0628 ARABIC LETTER BEH and U+0646 ARABIC LETTER NOON,
+          an author may used a U+200C ZERO WIDTH NON-JOINER (ZWNJ).
+        </p>
+        <p>Conversely, in order to force joining behavior in contexts where joining does not occur by default,
+          for example, between U+0628 ARABIC LETTER BEH and U+0020 SPACE, an author may used a U+200D ZERO WIDTH JOINER (ZWJ).
+        </p>
+        <p>The behavior of ZWNJ and ZWJ is script specific. See
+          <link href="http://www.unicode.org/versions/Unicode6.1.0/ch08.pdf">The Unicode Standard, Chapter 8,
+          Middle Eastern Scripts</link> for information on the use of these control characters with the Arabic
+          script. See
+          <link href="http://www.unicode.org/versions/Unicode6.1.0/ch09.pdf">The Unicode Standard, Chapter 9,
+          South Asian Scripts - I</link> for information on the use of these control characters with common
+          Indic scripts.
+        </p>
       </section>
     </section>
     <section id="supported_scripts">
@@ -377,103 +443,103 @@
           <th style="text-align:left">Comments</th>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Arabic_alphabet">Arabic</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Arabic_alphabet">Arabic</link></td>
           <td class="yes">full</td>
           <td class="yes">full</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Bengali_alphabet">Bengali</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Bengali_alphabet">Bengali</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Burmese_alphabet">Burmese</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Burmese_alphabet">Burmese</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Devanagari_alphabet">Devanagari</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Devanagari_alphabet">Devanagari</link></td>
           <td class="partial">partial</td>
           <td class="partial">partial</td>
           <td style="text-align:left">join controls (ZWJ, ZWNJ) not yet supported</td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Khmer_alphabet">Khmer</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Khmer_alphabet">Khmer</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Gujarati_alphabet">Gujarati</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Gujarati_alphabet">Gujarati</link></td>
           <td class="partial">partial</td>
           <td class="no">none</td>
           <td style="text-align:left">pre-alpha</td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Gurmukhī_alphabet">Gurmukhi</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Gurmukhī_alphabet">Gurmukhi</link></td>
           <td class="partial">partial</td>
           <td class="no">none</td>
           <td style="text-align:left">pre-alpha</td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Hebrew_alphabet">Hebrew</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Hebrew_alphabet">Hebrew</link></td>
           <td class="yes">full</td>
           <td class="partial">partial</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Kannada_alphabet">Kannada</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Kannada_alphabet">Kannada</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Lao_alphabet">Lao</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Lao_alphabet">Lao</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Malayalam_alphabet">Malayalam</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Malayalam_alphabet">Malayalam</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Mongolian_script">Mongolian</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Mongolian_script">Mongolian</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Oriya_script">Oriya</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Oriya_script">Oriya</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Tamil_alphabet">Tamil</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Tamil_alphabet">Tamil</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Telugu_alphabet">Telugu</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Telugu_alphabet">Telugu</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Tibetan_alphabet">Tibetan</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Tibetan_alphabet">Tibetan</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
         </tr>
         <tr>
-          <td><a href="http://en.wikipedia.org/wiki/Thai_alphabet">Thai</a></td>
+          <td><link href="http://en.wikipedia.org/wiki/Thai_alphabet">Thai</link></td>
           <td class="no">none</td>
           <td class="no">none</td>
           <td></td>
@@ -500,55 +566,55 @@
             <th style="text-align:left">Comments</th>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=24">Arial Unicode MS</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1081">1.01</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=24">Arial Unicode MS</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1081">1.01</link></td>
             <td style="text-align:center">50377</td>
             <td>limited GPOS support</td>
           </tr>
           <tr>
-            <td><a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;id=ArabicFonts">Lateef</a></td>
+            <td><link href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;id=ArabicFonts">Lateef</link></td>
             <td class="yes" style="text-align:left">1.0</td>
             <td style="text-align:center">1147</td>
             <td>language features for Kurdish (KUR), Sindhi (SND), Urdu (URD)</td>
           </tr>
           <tr>
-            <td><a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;id=ArabicFonts">Scheherazade</a></td>
+            <td><link href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;id=ArabicFonts">Scheherazade</link></td>
             <td class="yes" style="text-align:left">1.0</td>
             <td style="text-align:center">1197</td>
             <td>language features for Kurdish (KUR), Sindhi (SND), Urdu (URD)</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=261">Simplified Arabic</a></td>
-            <td class="no" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=867">1.01</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=261">Simplified Arabic</link></td>
+            <td class="no" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=867">1.01</link></td>
             <td/>
             <td>contains invalid, out of order coverage table entries</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/font.aspx?FID=261">Simplified Arabic</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1645">5.00</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/font.aspx?FID=261">Simplified Arabic</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1645">5.00</link></td>
             <td style="text-align:center">414</td>
             <td>lacks GPOS support</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/font.aspx?FID=261">Simplified Arabic</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/font.aspx?FID=261">Simplified Arabic</link></td>
             <td class="yes" style="text-align:left">5.92</td>
             <td style="text-align:center">473</td>
             <td>includes GPOS for advanced position adjustment</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=264">Traditional Arabic</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/family.aspx?FMID=877">1.01</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=264">Traditional Arabic</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/family.aspx?FMID=877">1.01</link></td>
             <td style="text-align:center">530</td>
             <td>lacks GPOS support</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/font.aspx?FID=264">Traditional Arabic</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1658">5.00</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/font.aspx?FID=264">Traditional Arabic</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1658">5.00</link></td>
             <td style="text-align:center">530</td>
             <td>lacks GPOS support</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/font.aspx?FID=264">Traditional Arabic</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/font.aspx?FID=264">Traditional Arabic</link></td>
             <td class="yes" style="text-align:left">5.92</td>
             <td style="text-align:center">589</td>
             <td>includes GPOS for advanced position adjustment</td>
@@ -571,26 +637,26 @@
             <th style="text-align:left">Comments</th>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=370">Aparajita</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1700">1.00</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=370">Aparajita</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1700">1.00</link></td>
             <td style="text-align:center">706</td>
             <td/>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=374">Kokila</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1749">1.00</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=374">Kokila</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1749">1.00</link></td>
             <td style="text-align:center">706</td>
             <td/>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=243">Mangal</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1759">5.01</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=243">Mangal</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1759">5.01</link></td>
             <td style="text-align:center">885</td>
             <td>designed for use in user interfaces</td>
           </tr>
           <tr>
-            <td><a href="http://www.microsoft.com/typography/fonts/family.aspx?FID=384">Utsaah</a></td>
-            <td class="yes" style="text-align:left"><a href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1811">1.00</a></td>
+            <td><link href="http://www.microsoft.com/typography/fonts/family.aspx?FID=384">Utsaah</link></td>
+            <td class="yes" style="text-align:left"><link href="http://www.microsoft.com/typography/fonts/font.aspx?FMID=1811">1.00</link></td>
             <td style="text-align:center">706</td>
             <td/>
           </tr>
@@ -618,10 +684,10 @@
         described above:
       </p>
       <ul>
-        <li><a href="http://www.unicode.org/">The Unicode Standard</a></li>
-        <li><a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</a></li>
-        <li><a href="http://www.microsoft.com/typography/otspec/ttochap1.htm">OpenType Advanced Typographic Extensions</a></li>
-        <li><a href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=CmplxRndExamples">Examples of Complex Rendering</a></li>
+        <li><link href="http://www.unicode.org/">The Unicode Standard</link></li>
+        <li><link href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</link></li>
+        <li><link href="http://www.microsoft.com/typography/otspec/ttochap1.htm">OpenType Advanced Typographic Extensions</link></li>
+        <li><link href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=CmplxRndExamples">Examples of Complex Rendering</link></li>
       </ul>
     </section>
   </body>

diff --git a/src/documentation/content/xdocs/1.1rc1/known-issues.xml b/src/documentation/content/xdocs/1.1rc1/known-issues.xml
index 622e6a79a10722b7e50f44167cd1f7b8a3b71bc5..c0107317d30fa40fad602c0dfc27dbe97c319ac4 100644 (file)
--- a/src/documentation/content/xdocs/1.1rc1/known-issues.xml
+++ b/src/documentation/content/xdocs/1.1rc1/known-issues.xml
@@ -17,69 +17,38 @@
 -->
 <!-- $Id$ -->
 <known-issues>
-  <!-- NEED TO REVIEW ALL OF THE FOLLOWING
   <known-issue>
-    MIF and SVG output support have not been restored, yet.
+    Support for Unicode characters outside of the Base Multilingual Plane (BMP), i.e., characters
+    whose code points are greater than 65535, is not yet implemented.
+    See <link href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51843">bug 51843</link>.
   </known-issue>
   <known-issue>
-    RTF output is inferior to other output formats supported by FOP.
-    For details, please see the "Output Targets" page of the release
-    you're using.
+    The writing-mode property does not produce the expected behavior when specified on
+    <code>fo:simple-page-master</code>  or <code>fo:region-*</code> elements.
+    See <link href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53276">bug 53276</link>.
   </known-issue>
   <known-issue>
-    Auto table layout is not implemented, yet.
+    Support for Devanagari and other Indic scripts is not yet complete.
   </known-issue>
   <known-issue>
-    Footnotes may overlap with text of the region-body in multi-column 
-    documents.
+    Use of Unicode U+200C ZERO WIDTH NON-JOINER (ZWNJ) or U+200D ZERO WIDTH JOINER (ZWJ)
+    does not prevent or force contextual substitution, respectively, when used with Arabic script.
   </known-issue>
   <known-issue>
-    Space resolution does not work between footnote regions.
+    Use of Unicode U+200C ZERO WIDTH NON-JOINER (ZWNJ) or U+200D ZERO WIDTH JOINER (ZWJ)
+    does not affect conjunct formation or other special behavior prescribed when used with Indic scripts.
   </known-issue>
   <known-issue>
-    Block containers with no height currently don't create a fence for
-    spaces as they should (they behave like a normal block).
+    Support for automatic line breaking at orthographic syllable segment boundaries in Indic
+    or Southeast Asian scripts is not yet available. In the mean time, use U+200B ZERO WIDTH SPACE (ZWSP).
   </known-issue>
   <known-issue>
-    Preserved linefeeds in fo:character are not handled correctly.
+    Complex script content is presently supported only with AT, IF, and PDF output formats.
   </known-issue>
   <known-issue>
-    An empty block currently produces a fence for stacking constraints
-    which it shouldn't.
+    When complex script text encounters an  <code>fo:inline</code> or <code>fo:character</code> boundary,
+    contextual substitution and ligature formation will not occur across the boundary. This prevents,
+    for example, applying a different color to an Arabic Letter within an Arabic word, unless that letter
+    is a non-joining letter (on both sides).
   </known-issue>
-  <known-issue>
-    There are several small problems around white space handling.
-  </known-issue>
-  <known-issue>
-    Images currently don't shrink so they fit on a page when they are 
-    too big and shrinking is allowed to happen.
-  </known-issue>
-  <known-issue>
-    Inline container may not work as expected.
-  </known-issue>
-  <known-issue>
-    The letter-spacing and word-spacing properties may not work as expected.
-  </known-issue>
-  <known-issue>
-    Leaders with leader-pattern="use-content" may not work as expected.
-  </known-issue>
-  <known-issue>
-    The keep-with-previous property doesn't work inside tables and lists, yet.
-  </known-issue>
-  <known-issue>
-    If two consecutive pages don't have the same available width, the 
-    content currently isn't properly fit into the available space on
-    the new page.
-  </known-issue>
-  <known-issue>
-    Background images on page number citations are not placed correctly.
-  </known-issue>
-  <known-issue>
-    Not all FO elements can be referenced by their "id", most notably:
-    table-body, table-header, table-footer and table-row.
-  </known-issue>
-  <known-issue>
-    Border and padding conditionality are not supported on table-cells, yet.
-  </known-issue>
-  -->
 </known-issues>

diff --git a/src/documentation/content/xdocs/1.1rc1/knownissues_overview.xml b/src/documentation/content/xdocs/1.1rc1/knownissues_overview.xml
index 0ac8033368786cc0f10413cd8545283c4c3ade8a..f27f98f3265018142a2db3f698bf495e0a7b4204 100644 (file)
--- a/src/documentation/content/xdocs/1.1rc1/knownissues_overview.xml
+++ b/src/documentation/content/xdocs/1.1rc1/knownissues_overview.xml
@@ -61,7 +61,12 @@
   </section>
   <section>
     <title>Other known issues</title>
-    <p>This section lists other known issues.</p>
+    <p>This section lists some other issues that post-date the release of FOP 1.0. For known issues that pre-date FOP 1.0, see
+      <link href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2001-01-01&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">older bugs that remain open</link>.
+      For all open issues that post-date FOP 1.0, see
+      <link href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2010-07-20&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">newer bugs that remain open</link>.
+    </p>
+    <!-- See <root>/known-issues.xml for the source document of this section! -->
     <xi:include href="cocoon://knownissues-raw-static_1.1rc1.xml#xpointer(/document/body/*)"/>
   </section>
 </section>

diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index d980edbb17c4ca0cc36f8dd354e65fe6d85e29fe..47fa65e6e31672de1de529ccffd7a032f45a3f8b 100644 (file)
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -146,7 +146,7 @@
         <p>
           When it's ready and the committers have enough time to go
           through the time-consuming process of creating a release. Version
-          1.1rc1 was released on 3 June 2012. A subsequent final
+          1.1rc1 was released on 02 July 2012. A subsequent final
           Version 1.1 is expected to be released within 1 to 3 months following
           this release candidate. If you want to speed up the process, consider <link
           href="dev/index.html#involved">contributing</link> to FOP.

diff --git a/src/documentation/content/xdocs/news-data.xml b/src/documentation/content/xdocs/news-data.xml
index 9495528e5582aec040d38d053b34d412a74ef6a2..4b8956cd1cf3296a26929ca797894ef51a68a3ed 100644 (file)
--- a/src/documentation/content/xdocs/news-data.xml
+++ b/src/documentation/content/xdocs/news-data.xml
@@ -17,7 +17,7 @@
 -->
 <!-- $Id$ -->
 <news>
-  <item date="2012-06-03" title="Apache™ FOP 1.1rc1 Available">
+  <item date="2012-07-02" title="Apache™ FOP 1.1rc1 Available">
     <p>
       This is a candidate release for an upcoming FOP Version 1.1 (stable) release.
       release of the new FOP codebase. This release

diff --git a/src/documentation/content/xdocs/status.xml b/src/documentation/content/xdocs/status.xml
index ccefe58ebfbfe517df60da68cdf44aeedf820afc..1b6f1dc2b11159e38a0876f95bfb3d33216bfe6e 100644 (file)
--- a/src/documentation/content/xdocs/status.xml
+++ b/src/documentation/content/xdocs/status.xml
@@ -27,9 +27,9 @@
   <body>
     <section>
       <title>Status</title>
-      <p>Last updated 3 June 2012.</p>
+      <p>Last updated 02 July 2012.</p>
       <p>
-        Apache™ FOP version 1.1rc1 (candidate) was released on 3 June 2012.
+        Apache™ FOP version 1.1rc1 (candidate) was released on 02 July 2012.
       </p>
     </section>
     <section>
@@ -37,7 +37,7 @@
       <p>
         The FOP code base is gradually evolving, from Version 0.90,
        released on 22 November 2005, to Version 1.1, expected to be released during
-        the Summer of 2012. Further releases in the 1.x series and byond are expected.
+        the Summer of 2012. Further releases in the 1.x series and beyond are expected.
       </p>
       <p>
         FOP releases prior to version 0.90 were based on a different

diff --git a/src/documentation/resources/stylesheets/known-issues2document.xsl b/src/documentation/resources/stylesheets/known-issues2document.xsl
index 8e10c35a2114b4800f6f8af56f5df33e61b13dc2..ad0c4d70a5ab033b7713c5fe0f64c44a40dd6997 100644 (file)
--- a/src/documentation/resources/stylesheets/known-issues2document.xsl
+++ b/src/documentation/resources/stylesheets/known-issues2document.xsl
@@ -46,4 +46,10 @@
     </li>
   </xsl:template>
   
+  <xsl:template match="@*|*|text()|processing-instruction()|comment()">
+    <xsl:copy>
+      <xsl:apply-templates select="@*|*|text()|processing-instruction()|comment()"/>
+    </xsl:copy>
+  </xsl:template>
+
 </xsl:stylesheet>

diff --git a/status.xml b/status.xml
index 765d8713a0143fdb5c0954f605e8e249ebab157a..a55f79feae8d28154bc39d69ceb6b450112883ff 100644 (file)
--- a/status.xml
+++ b/status.xml
@@ -61,8 +61,7 @@
       users, i.e. when the behaviour changes and could affect the layout of existing
       documents. Example: the fix of marks layering will be such a case when it's done.
     -->
-    <release version="1.1rc1" date="3 June 2012">
-    <release version="FOP Trunk" date="TBD">
+    <release version="1.1rc1" date="02 July 2012">
       <action context="Code" dev="GA" type="fix">
         Eliminate javadocs warnings.
       </action>