Return-Path: X-Original-To: apmail-xmlgraphics-commits-archive@www.apache.org Delivered-To: apmail-xmlgraphics-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C1D8CD233 for ; Fri, 30 Nov 2012 15:22:53 +0000 (UTC) Received: (qmail 81263 invoked by uid 500); 30 Nov 2012 15:22:53 -0000 Mailing-List: contact commits-help@xmlgraphics.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@xmlgraphics.apache.org Delivered-To: mailing list commits@xmlgraphics.apache.org Received: (qmail 81235 invoked by uid 99); 30 Nov 2012 15:22:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2012 15:22:53 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2012 15:22:52 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 2B9602388A4A for ; Fri, 30 Nov 2012 15:22:32 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r840182 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/trunk/complexscripts.html Date: Fri, 30 Nov 2012 15:22:31 -0000 To: commits@xmlgraphics.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121130152232.2B9602388A4A@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Fri Nov 30 15:22:31 2012 New Revision: 840182 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 Fri Nov 30 15:22:31 2012 @@ -1 +1 @@ -1415683 +1415686 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 Fri Nov 30 15:22:31 2012 @@ -549,101 +549,69 @@ A document author need not make explicit - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Code Script Comments
bng2 Bengali OpenType Indic Version 2 (May 2008 and following) behavior.
dev2 Devanagari OpenType Indic Version 2 (May 2008 and following) behavior.
gur2 Gurmukhi OpenType Indic Version 2 (May 2008 and following) behavior.
gjr2 Gujarati OpenType Indic Version 2 (May 2008 and following) behavior.
knd2 Kannada OpenType Indic Version 2 (May 2008 and following) behavior.
mlm2 Malayalam OpenType Indic Version 2 (May 2008 and following) behavior.
ory2 Oriya OpenType Indic Version 2 (May 2008 and following) behavior.
tml2 Tamil OpenType Indic Version 2 (May 2008 and following) behavior.
tel2 Telugu OpenType Indic Version 2 (May 2008 and following) behavior.
Explicit use of one of the above extended script codes is not portable, and should be limited to use with FOP only.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
+

Explicit use of one of the above extended script codes is not portable, and should be limited to use with FOP only.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

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 property.

When specifying the language property, the value of the property must be either an ISO639-2 3-letter code or an ISO639-1 2-letter code . 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

-

Number Conversion Properties

-

Bidi Override Element

-

Bidi Control Characters

-

Join Control Characters

-

Supported Scripts

+

Writing Mode Property

+

Number Conversion Properties

+

Bidi Override Element

+

Bidi Control Characters

+

Join Control Characters

+

Supported Scripts

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.

@@ -795,9 +763,9 @@ A document author need not make explicit
-

Supported Fonts

+

Supported Fonts

Support for specific fonts is enumerated in the following sub-sections. If a given font is not listed, then it has not been tested with these complex scripts features.

-

Arabic Fonts

+

Arabic Fonts

@@ -884,7 +852,7 @@ A document author need not make explicit
-

Devanagari Fonts

+

Devanagari Fonts

@@ -931,7 +899,7 @@ A document author need not make explicit
-

Other Limitations

+

Other Limitations

Complex scripts support in Apache FOP is relatively new, so there are certain limitations. Please help us identify and close any gaps.

  • @@ -941,7 +909,7 @@ A document author need not make explicit

    Shaping context does not extend across an element boundary. This limitation prevents the use of fo:character , fo:inline or fo:wrapper in order to colorize individual Arabic letters without affecting shaping behavior across the element boundary.

- +

In addition to the XSL-FO specification, a number of external resources provide guidance about authoring documents that employ complex scripts and the features described above:

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