xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840550 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/trunk/complexscripts.html
Date Mon, 03 Dec 2012 14:04:18 GMT
Author: buildbot
Date: Mon Dec  3 14:04:17 2012
New Revision: 840550

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec  3 14:04:17 2012
@@ -1 +1 @@
-1416506
+1416525

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html Mon Dec  3 14:04:17
2012
@@ -608,10 +608,78 @@ A document author need not make explicit
 <p>Certain fonts that support complex script features can make use of language information
in order for 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">http://www.w3.org/TR/2006/REC-xsl11-20061205/#language</a>
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 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>
 <h3 id="writing-mode-property-wzxhzdk20wzxhzdk21">Writing Mode Property <a id="writing_mode_property"></a></h3>
+<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>
+<p><code>fo:page-sequence</code> </p>
+</li>
+<li>
+<p><code>fo:simple-page-master</code> </p>
+</li>
+<li>
+<p><code>fo:region-*</code> </p>
+</li>
+<li>
+<p><code>fo:block-container</code> </p>
+</li>
+<li>
+<p><code>fo:inline-container</code> </p>
+</li>
+<li>
+<p><code>fo:table</code> </p>
+</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>
+<p><code>lr-tb</code> </p>
+</li>
+<li>
+<p><code>rl-tb</code> </p>
+</li>
+<li>
+<p><code>lr</code> </p>
+</li>
+<li>
+<p><code>rl</code> </p>
+</li>
+</ul>
+<p>Writing modes that employ a vertical inline progression direction are not yet supported.</p>
 <h3 id="number-conversion-properties-wzxhzdk22wzxhzdk23">Number Conversion Properties
<a id="number_conversion_properties"></a></h3>
 <h3 id="bidi-override-element-wzxhzdk24wzxhzdk25">Bidi Override Element <a id="bidi_override_element"></a></h3>
+<p>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">fo:bidi-override</a>
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 <a href="#bidi_controls">Bidi Control Characters</a> , the
default behavior prescribed by the <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode
Bidirectional Algorithm</a> applies.</p>
 <h3 id="bidi-control-characters-wzxhzdk26wzxhzdk27">Bidi Control Characters <a id="bidi_controls"></a></h3>
+<p>In addition to the use of the <a href="#bidi_override_element">Bidi Override
Element</a> , an author may make use of the following explicit Unicode Bidi Control
Characters:</p>
+<ul>
+<li>
+<p>U+200E - LEFT-TO-RIGHT MARK (LRM)</p>
+</li>
+<li>
+<p>U+200F - RIGHT-TO-LEFT MARK (RLM)</p>
+</li>
+<li>
+<p>U+202A - LEFT-TO-RIGHT EMBEDDING (LRE)</p>
+</li>
+<li>
+<p>U+202B - RIGHT-TO-LEFT EMBEDDING (RLE)</p>
+</li>
+<li>
+<p>U+202C - POP DIRECTIONAL FORMATTING (PDF)</p>
+</li>
+<li>
+<p>U+202D - LEFT-TO-RIGHT OVERRIDE (LRO)</p>
+</li>
+<li>
+<p>U+202E - RIGHT-TO-LEFT OVERRIDE (RLO)</p>
+</li>
+</ul>
+<p>If an embedding or override is not terminated (using U+202C PDF) prior to the end
of a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#d0e4879">delimited text
range</a> , then it is automatically terminated by FOP.</p>
 <h3 id="join-control-characters-wzxhzdk28wzxhzdk29">Join Control Characters <a id="join_controls"></a></h3>
+<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 <a href="http://www.unicode.org/versions/Unicode6.1.0/ch08.pdf">The
Unicode Standard, Chapter 8, Middle Eastern Scripts</a> for information on the use of
these control characters with the Arabic script. See <a href="http://www.unicode.org/versions/Unicode6.1.0/ch09.pdf">The
Unicode Standard, Chapter 9, South Asian Scripts - I</a> for information on the use
of these control characters with common Indic scripts.</p>
 <h2 id="supported-scripts-wzxhzdk30wzxhzdk31">Supported Scripts <a id="supported_scripts"></a></h2>
 <p>Support for specific complex scripts is enumerated in the following table. Support
for those marked as not being supported is expected to be added in future revisions.</p>
 <table>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message