xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1415683 - /xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext
Date Fri, 30 Nov 2012 15:15:47 GMT
Author: psancho
Date: Fri Nov 30 15:15:46 2012
New Revision: 1415683

URL: http://svn.apache.org/viewvc?rev=1415683&view=rev
Log:
FOP complex script: ordered list with code (use <br>) + titles hierarchy + links labels

Modified:
    xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext

Modified: xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext?rev=1415683&r1=1415682&r2=1415683&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext Fri Nov 30 15:15:46 2012
@@ -21,43 +21,36 @@ This page describes the [complex scripts
 Complex script features are enabled by default. If some application of FOP does not require
this support, then it can be disabled in three ways:
 
 
-1.  **Command line:** The command line option `-nocs` turns off complex script features:
`fop -nocs -fo mydocument.fo -pdf mydocument.pdf` 
-
-1.  **Embedding:**  `userAgent.setComplexScriptFeaturesEnabled(false);` 
-
-1.  **Optional setting in fop.xconf file:**  `
-<fop version="1.0">
-  <complex-scripts disabled="true"/>
-  ...
-</fop>
-          ` 
+1.  **Command line:**<br/>The command line option `-nocs` turns off complex script
features:<br/>`fop -nocs -fo mydocument.fo -pdf mydocument.pdf`<br/> 
+1.  **Embedding:**<br/>`userAgent.setComplexScriptFeaturesEnabled(false);` 
+1.  **Optional setting in fop.xconf file:**<br/>`<fop version="1.0">`<br/>`<complex-scripts
disabled="true"/>`<br/>`...`<br/>`</fop>`
 
 When complex scripts features are enabled, additional information related to bidirectional
level resolution, the association between characters and glyphs, and glyph position adjustments
are added to the internal, parsed representation of the XSL-FO tree and its corresponding
formatted area tree. This additional information will somewhat increase the memory requirements
for processing documents that use these features.
 A document author need not make explicit use of any complex scripts feature in order for
this additional information to be created. For example, if the author makes use of a font
that contains OpenType GSUB and/or GPOS tables, then those tables will be automatically used
unless complex scripts features are disabled.
-# Changes to your XSL-FO input files <a id="source"></a>
+## Changes to your XSL-FO input files <a id="source"></a>
 
 In most circumstances, XSL-FO content does not need to change in order to make use of complex
scripts features; however, in certain contexts, fully automatic processing is not sufficient.
In these cases, an author may make use of the following XSL-FO constructs:
 
 
-- The [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#script) property.
+- The [script](http://www.w3.org/TR/2006/REC-xsl11-20061205/#script) property.
 
-- The [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#language) property.
+- The [language](http://www.w3.org/TR/2006/REC-xsl11-20061205/#language) property.
 
-- The [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#writing-mode) property.
+- The [writing-mode](http://www.w3.org/TR/2006/REC-xsl11-20061205/#writing-mode) property.
 
-- The number to string conversion properties: [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#format)
, [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-separator) , [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-size)
, [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#letter-value) , and `fox:number-conversion-features`
.
+- The number to string conversion properties: [format](http://www.w3.org/TR/2006/REC-xsl11-20061205/#format)
, [grouping-separator](http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-separator) ,
[grouping-size](http://www.w3.org/TR/2006/REC-xsl11-20061205/#grouping-size) , [letter-value](http://www.w3.org/TR/2006/REC-xsl11-20061205/#letter-value)
, and `fox:number-conversion-features` .
 
-- The [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override) element.
+- The [fo:bidi-override](http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override)
element.
 
 - 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.
 
 - Explicit join control characters: U+200C ZWNJ and U+200D ZWJ.
 
-## Authoring Details <a id="details"></a>
+### Authoring Details <a id="details"></a>
 
 The complex scripts related effects of the above enumerated XSL-FO constructs are more fully
described in the following sub-sections.
 
-### Script Property <a id="script_property"></a>
+#### Script Property <a id="script_property"></a>
 
 In order to apply font specific complex script features, it is necessary to know the script
that applies to the text undergoing layout processing. This script is determined using the
following algorithm:
 
@@ -68,7 +61,7 @@ In order to apply font specific complex 
 
 In case the automatic algorithm does not produce the desired results, an author may explicitly
specify a `script` property with the desired script. If specified, it must be one of the four-letter
script code specified in [ISO 15924 Code List](http://unicode.org/iso15924/iso15924-codes.html)
or in the [Extended Script Codes](#extended_script_codes) 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.
 
-#### Standard Script Codes ## <a id="standard_script_codes"></a>
+##### Standard Script Codes <a id="standard_script_codes"></a>
 
 The following table enumerates the standard ISO 15924 4-letter codes recognized by FOP.
 
@@ -107,7 +100,7 @@ The following table enumerates the stand
 |  `zyyy`  | Undetermined |
 |  `zzzz`  | Uncoded |
 
-#### Extended Script Codes ## <a id="extended_script_codes"></a>
+#### Extended Script Codes <a id="extended_script_codes"></a>
 
 The following table enumerates a number of non-standard extended script codes recognized
by FOP.
 
@@ -123,21 +116,21 @@ The following table enumerates a number 
 |  `tml2`  | Tamil | OpenType Indic Version 2 (May 2008 and following) behavior. |
 |  `tel2`  | Telugu | OpenType Indic Version 2 (May 2008 and following) behavior. |
 <warning>Explicit use of one of the above extended script codes is not portable, and
should be limited to use with FOP only.</warning>When performing automatic script determination,
FOP selects the OpenType Indic Version 2 script codes by default. If the author requires Version
1 behavior, then an explicit, non-extension script code should be specified in a governing
`script` property.
-## Language Property <a id="language_property"></a>
+### Language Property <a id="language_property"></a>
 
 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 [](http://www.w3.org/TR/2006/REC-xsl11-20061205/#language) property.
 
 When specifying the `language` property, the value of the property must be either an [ISO639-2
3-letter code](http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes) or an [ISO639-1 2-letter
code](http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) . 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.
 
-### Writing Mode Property <a id="writing_mode_property"></a>
+#### Writing Mode Property <a id="writing_mode_property"></a>
 
-### Number Conversion Properties <a id="number_conversion_properties"></a>
+#### Number Conversion Properties <a id="number_conversion_properties"></a>
 
-### Bidi Override Element <a id="bidi_override_element"></a>
+#### Bidi Override Element <a id="bidi_override_element"></a>
 
-### Bidi Control Characters <a id="bidi_controls"></a>
+#### Bidi Control Characters <a id="bidi_controls"></a>
 
-### Join Control Characters <a id="join_controls"></a>
+#### Join Control Characters <a id="join_controls"></a>
 
 ## Supported Scripts <a id="supported_scripts"></a>
 



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


Mime
View raw message