You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by ga...@apache.org on 2012/07/05 21:15:15 UTC
svn commit: r1357814 [1/7] - in /xmlgraphics/fop/branches/fop-1_1: ./
src/documentation/content/ src/documentation/content/xdocs/
src/documentation/content/xdocs/1.1rc1/
src/documentation/content/xdocs/1.1rc1/fotree/
src/documentation/content/xdocs/1.1...
Author: gadams
Date: Thu Jul 5 19:15:13 2012
New Revision: 1357814
URL: http://svn.apache.org/viewvc?rev=1357814&view=rev
Log:
Reapply 1.1rc1 changes.
Added:
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/accessibility.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/anttask.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/compiling.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/complexscripts.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/configuration.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/embedding.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/events.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/extensions.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/fonts.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/fotree/
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/fotree/disabled-testcases.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/graphics.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/hyphenation.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/index.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/intermediate.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/known-issues.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/knownissues_overview.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/layoutengine/
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/layoutengine/disabled-testcases.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/metadata.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/output.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/pdfa.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/pdfencryption.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/pdfx.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/running.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/servlets.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/upgrading.xml
Removed:
xmlgraphics/fop/branches/fop-1_1/checkstyle-5.1.xml
Modified:
xmlgraphics/fop/branches/fop-1_1/NOTICE
xmlgraphics/fop/branches/fop-1_1/README
xmlgraphics/fop/branches/fop-1_1/build.xml
xmlgraphics/fop/branches/fop-1_1/known-issues.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/.htaccess
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/doap.rdf
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/bugs.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/compliance.ihtml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/download.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/faq.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/fo.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/index.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/knownissues.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/license.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/maillist.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/news-data.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/news.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/quickstartguide.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/site.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/status.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/tabs.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/team.xml
xmlgraphics/fop/branches/fop-1_1/src/documentation/resources/stylesheets/known-issues2document.xsl
xmlgraphics/fop/branches/fop-1_1/status.xml
Modified: xmlgraphics/fop/branches/fop-1_1/NOTICE
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/NOTICE?rev=1357814&r1=1357813&r2=1357814&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/NOTICE (original)
+++ xmlgraphics/fop/branches/fop-1_1/NOTICE Thu Jul 5 19:15:13 2012
@@ -1,5 +1,5 @@
Apache FOP
-Copyright 1999-2010 The Apache Software Foundation
+Copyright 1999-2012 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
Modified: xmlgraphics/fop/branches/fop-1_1/README
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/README?rev=1357814&r1=1357813&r2=1357814&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/README (original)
+++ xmlgraphics/fop/branches/fop-1_1/README Thu Jul 5 19:15:13 2012
@@ -22,8 +22,8 @@ Apache FOP is the world's first print fo
objects. It is a Java application that reads a formatting object tree
conforming to the XSL 1.1 Recommendation (05 December 2006) and then turns it
into a PDF document, certain other output formats or allows you to preview it
-directly on screen. Some parts of the XSL 1.1 specification (work in progress!)
-have also been implemented.
+directly on screen. Note that not all parts of the XSL 1.1 specification
+have yes been implemented.
Apache FOP is part of Apache's XML Graphics project. The homepage of Apache
FOP is http://xmlgraphics.apache.org/fop/.
@@ -93,6 +93,41 @@ http://xmlgraphics.apache.org/fop/stable
RELEASE NOTES
==============================================================================
+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.
+See below for details.
+
+Compliance
+----------
+
+This release implements the XSL 1.0 and 1.1 recommendations to a relatively
+high degree of compliance. See the compliance page
+http://xmlgraphics.apache.org/fop/compliance.html for further details.
+
+Known issues
+------------
+
+A detailed list of known issues in this release is available at
+http://xmlgraphics.apache.org/fop/1.1/knownissues_overview.html.
+
+Major Changes in Version 1.1rc1
+-------------------------------
+
+* Added support for complex scripts (e.g. Arabic, Indic, etc).
+* Added possibility to embed TrueType fonts in the PostScript output.
+* Added possibility to reduce the file size of accessible PDF outputs by using
+ Object Streams (a PDF 1.5 feature).
+* Added support for 128bit PDF encryption.
+
+A more detailed list of changes in this release is available at
+http://xmlgraphics.apache.org/fop/1.1rc1/changes_1.1rc1.html.
+
+A more detailed list of changes in this and earlier releases is available at
+http://xmlgraphics.apache.org/fop/changes.html.
+
Version 1.0
===========
Modified: xmlgraphics/fop/branches/fop-1_1/build.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/build.xml?rev=1357814&r1=1357813&r2=1357814&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/build.xml (original)
+++ xmlgraphics/fop/branches/fop-1_1/build.xml Thu Jul 5 19:15:13 2012
@@ -143,8 +143,8 @@ list of possible build targets.
<property name="Name" value="Apache FOP"/>
<property name="name" value="fop"/>
<property name="NAME" value="FOP"/>
- <property name="version" value="svn-trunk"/>
- <property name="year" value="1999-2010"/>
+ <property name="version" value="1.1rc1"/>
+ <property name="year" value="1999-2012"/>
<property name="javac.debug" value="on"/>
<property name="javac.optimize" value="off"/>
<property name="javac.deprecation" value="on"/>
@@ -477,7 +477,7 @@ list of possible build targets.
<attribute name="Build-Id" value="${ts} (${user.name} [${os.name} ${os.version} ${os.arch}, Java ${java.runtime.version}, Target Java ${javac.target}])"/>
<section name="org/apache/fop/">
<attribute name="Specification-Title" value="XSL-FO - Extensible Stylesheet Language"/>
- <attribute name="Specification-Version" value="1.0"/>
+ <attribute name="Specification-Version" value="1.1"/>
<attribute name="Specification-Vendor" value="World Wide Web Consortium"/>
<attribute name="Specification-URL" value="http://www.w3.org/TR/xsl"/>
<attribute name="Implementation-Title" value="${Name}"/>
@@ -1438,14 +1438,20 @@ NOTE:
</delete>
</target>
<target name="validate-xdocs" description="Validate the xdocs. Point schemas.dir to Forrest's 'schemas' directory.">
- <property name="schemas.dir" value="../xml-forrest/src/resources/schema"/>
+ <property name="schemas.dir" value="../xml-forrest/main/webapp/resources/schema"/>
<xmlvalidate failonerror="no">
- <fileset dir="${xdocs.dir}" includes="**.xml"/>
+ <fileset dir="${xdocs.dir}">
+ <include name="**.xml"/>
+ <exclude name="**/site.xml"/>
+ <exclude name="**/news-data.xml"/>
+ </fileset>
<xmlcatalog>
<entity publicId="-//APACHE//DTD Compliance V1.0//EN" location="src/documentation/resources/schema/dtd/compliance-v10.dtd"/>
<entity publicId="-//APACHE//DTD Documentation V1.1//EN" location="${schemas.dir}/dtd/document-v11.dtd"/>
+ <entity publicId="-//APACHE//DTD Documentation V1.3//EN" location="${schemas.dir}/dtd/document-v13.dtd"/>
<entity publicId="-//APACHE//DTD Specification V1.1//EN" location="${schemas.dir}/dtd/specification-v11.dtd"/>
<entity publicId="-//APACHE//DTD FAQ V1.1//EN" location="${schemas.dir}/dtd/faq-v11.dtd"/>
+ <entity publicId="-//APACHE//DTD FAQ V1.3//EN" location="${schemas.dir}/dtd/faq-v13.dtd"/>
<entity publicId="-//APACHE//DTD Changes V1.1//EN" location="${schemas.dir}/dtd/changes-v11.dtd"/>
<entity publicId="-//APACHE//DTD Todo V1.1//EN" location="${schemas.dir}/dtd/todo-v11.dtd"/>
<entity publicId="-//APACHE//DTD Cocoon Documentation Book V1.0//EN" location="${schemas.dir}/dtd/book-cocoon-v10.dtd"/>
Modified: xmlgraphics/fop/branches/fop-1_1/known-issues.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/known-issues.xml?rev=1357814&r1=1357813&r2=1357814&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/known-issues.xml (original)
+++ xmlgraphics/fop/branches/fop-1_1/known-issues.xml Thu Jul 5 19:15:13 2012
@@ -17,75 +17,69 @@
-->
<!-- $Id$ -->
<known-issues>
- <known-issue>
- MIF and SVG output support have not been restored, yet.
- </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.
- </known-issue>
- <known-issue>
- Auto table layout is not implemented, yet.
- </known-issue>
- <known-issue>
- Footnotes may overlap with text of the region-body in multi-column
- documents.
- </known-issue>
- <known-issue>
- Space resolution does not work between footnote regions.
- </known-issue>
- <known-issue>
- There's a problem involving nested block-containers and
- reference-orientation 180/-180 (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36391">Bugzilla #36391</a>)
- </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).
- </known-issue>
- <known-issue>
- Preserved linefeeds in fo:character are not handled correctly.
- </known-issue>
- <known-issue>
- An empty block currently produces a fence for stacking constraints
- which it shouldn't.
- </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>
- 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>
- keep-with-previous 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-issue>
- Column balancing in multi-column documents may not work as expected
- (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36356">Bugzilla #36356</a>)
- </known-issue>
+ <!-- NEED TO REVIEW ALL OF THE FOLLOWING
+ <known-issue>
+ MIF and SVG output support have not been restored, yet.
+ </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.
+ </known-issue>
+ <known-issue>
+ Auto table layout is not implemented, yet.
+ </known-issue>
+ <known-issue>
+ Footnotes may overlap with text of the region-body in multi-column
+ documents.
+ </known-issue>
+ <known-issue>
+ Space resolution does not work between footnote regions.
+ </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).
+ </known-issue>
+ <known-issue>
+ Preserved linefeeds in fo:character are not handled correctly.
+ </known-issue>
+ <known-issue>
+ An empty block currently produces a fence for stacking constraints
+ which it shouldn't.
+ </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>
Modified: xmlgraphics/fop/branches/fop-1_1/src/documentation/content/.htaccess
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/.htaccess?rev=1357814&r1=1357813&r2=1357814&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/.htaccess (original)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/.htaccess Thu Jul 5 19:15:13 2012
@@ -1,27 +1,27 @@
# redirect moved files
-RedirectMatch Permanent ^/fop/anttask(.*) http://xmlgraphics.apache.org/fop/1.0/anttask$1
-RedirectMatch Permanent ^/fop/compiling(.*) http://xmlgraphics.apache.org/fop/1.0/compiling$1
-RedirectMatch Permanent ^/fop/configuration(.*) http://xmlgraphics.apache.org/fop/1.0/configuration$1
-RedirectMatch Permanent ^/fop/embedding(.*) http://xmlgraphics.apache.org/fop/1.0/embedding$1
-RedirectMatch Permanent ^/fop/extensions(.*) http://xmlgraphics.apache.org/fop/1.0/extensions$1
-RedirectMatch Permanent ^/fop/fonts(.*) http://xmlgraphics.apache.org/fop/1.0/fonts$1
-RedirectMatch Permanent ^/fop/graphics(.*) http://xmlgraphics.apache.org/fop/1.0/graphics$1
-RedirectMatch Permanent ^/fop/hyphenation(.*) http://xmlgraphics.apache.org/fop/1.0/hyphenation$1
-RedirectMatch Permanent ^/fop/intermediate(.*) http://xmlgraphics.apache.org/fop/1.0/intermediate$1
-RedirectMatch Permanent ^/fop/output(.*) http://xmlgraphics.apache.org/fop/1.0/output$1
-RedirectMatch Permanent ^/fop/pdfa(.*) http://xmlgraphics.apache.org/fop/1.0/pdfa$1
-RedirectMatch Permanent ^/fop/pdfencryption(.*) http://xmlgraphics.apache.org/fop/1.0/pdfencryption$1
-RedirectMatch Permanent ^/fop/pdfx(.*) http://xmlgraphics.apache.org/fop/1.0/pdfx$1
-RedirectMatch Permanent ^/fop/running(.*) http://xmlgraphics.apache.org/fop/1.0/running$1
-RedirectMatch Permanent ^/fop/servlets(.*) http://xmlgraphics.apache.org/fop/1.0/servlets$1
-RedirectMatch Permanent ^/fop/upgrading(.*) http://xmlgraphics.apache.org/fop/1.0/upgrading$1
+RedirectMatch Permanent ^/fop/anttask(.*) http://xmlgraphics.apache.org/fop/1.1rc1/anttask$1
+RedirectMatch Permanent ^/fop/compiling(.*) http://xmlgraphics.apache.org/fop/1.1rc1/compiling$1
+RedirectMatch Permanent ^/fop/configuration(.*) http://xmlgraphics.apache.org/fop/1.1rc1/configuration$1
+RedirectMatch Permanent ^/fop/embedding(.*) http://xmlgraphics.apache.org/fop/1.1rc1/embedding$1
+RedirectMatch Permanent ^/fop/extensions(.*) http://xmlgraphics.apache.org/fop/1.1rc1/extensions$1
+RedirectMatch Permanent ^/fop/fonts(.*) http://xmlgraphics.apache.org/fop/1.1rc1/fonts$1
+RedirectMatch Permanent ^/fop/graphics(.*) http://xmlgraphics.apache.org/fop/1.1rc1/graphics$1
+RedirectMatch Permanent ^/fop/hyphenation(.*) http://xmlgraphics.apache.org/fop/1.1rc1/hyphenation$1
+RedirectMatch Permanent ^/fop/intermediate(.*) http://xmlgraphics.apache.org/fop/1.1rc1/intermediate$1
+RedirectMatch Permanent ^/fop/output(.*) http://xmlgraphics.apache.org/fop/1.1rc1/output$1
+RedirectMatch Permanent ^/fop/pdfa(.*) http://xmlgraphics.apache.org/fop/1.1rc1/pdfa$1
+RedirectMatch Permanent ^/fop/pdfencryption(.*) http://xmlgraphics.apache.org/fop/1.1rc1/pdfencryption$1
+RedirectMatch Permanent ^/fop/pdfx(.*) http://xmlgraphics.apache.org/fop/1.1rc1/pdfx$1
+RedirectMatch Permanent ^/fop/running(.*) http://xmlgraphics.apache.org/fop/1.1rc1/running$1
+RedirectMatch Permanent ^/fop/servlets(.*) http://xmlgraphics.apache.org/fop/1.1rc1/servlets$1
+RedirectMatch Permanent ^/fop/upgrading(.*) http://xmlgraphics.apache.org/fop/1.1rc1/upgrading$1
# redirect to versioned documentation
# Current stable release
Redirect Temp /fop/stable http://xmlgraphics.apache.org/fop/1.0
# Current unstable release (or trunk if no beta is the latest release)
-Redirect Temp /fop/unstable http://xmlgraphics.apache.org/fop/trunk
+Redirect Temp /fop/unstable http://xmlgraphics.apache.org/fop/1.1rc1
# Latest release
Redirect Temp /fop/current http://xmlgraphics.apache.org/fop/1.0
Modified: xmlgraphics/fop/branches/fop-1_1/src/documentation/content/doap.rdf
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/doap.rdf?rev=1357814&r1=1357813&r2=1357814&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/doap.rdf (original)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/doap.rdf Thu Jul 5 19:15:13 2012
@@ -15,7 +15,6 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-<?xml-stylesheet type="text/xsl" href="../xsl/p2.xsl"?>
<rdf:RDF xml:lang="en"
xmlns="http://usefulinc.com/ns/doap#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
@@ -76,18 +75,25 @@
</asfext:implements>
<release>
<Version>
- <name>Previous stable release</name>
- <created>2008-08-05</created>
- <revision>0.95</revision>
+ <name>Upcoming release (candidate)</name>
+ <created>2012-07-02</created>
+ <revision>1.1rc1</revision>
</Version>
</release>
<release>
<Version>
- <name>Latest stable release</name>
+ <name>Current release (stable)</name>
<created>2010-07-21</created>
<revision>1.0</revision>
</Version>
</release>
+ <release>
+ <Version>
+ <name>Previous release (stable)</name>
+ <created>2008-08-05</created>
+ <revision>0.95</revision>
+ </Version>
+ </release>
<repository>
<SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/"/>
Added: xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/accessibility.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/accessibility.xml?rev=1357814&view=auto
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/accessibility.xml (added)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/accessibility.xml Thu Jul 5 19:15:13 2012
@@ -0,0 +1,167 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id$ -->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd">
+<document>
+ <header>
+ <title>Apache⢠FOP: Accessibility</title>
+ </header>
+ <body>
+ <section id="overview">
+ <title>Overview</title>
+ <p>
+ This page describes the
+ <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a>
+ features of Apache⢠FOP.
+ <a href="http://www.section508.gov/">Section 508</a> defines accessibility in the context
+ of electronic documents for the USA but other countries have similar requirements.
+ </p>
+ <p>
+ Accessibility features are available only for the PDF output format and there are some
+ implementation limitations. Also, certain actions must be undertaken by the content creator
+ to ensure that FOP can create a truly accessible document.
+ </p>
+ </section>
+ <section>
+ <title>Enabling accessibility</title>
+ <p>There are 3 ways to enable accessibility:</p>
+ <ol>
+ <li>
+ <strong>Command line:</strong> The command line option -a turns on accessibility:
+ <code>fop -a -fo mydocument.fo -pdf mydocument.pdf</code>
+ </li>
+ <li>
+ <strong>Embedding:</strong> <code>userAgent.setAccessibility(true);</code>
+ </li>
+ <li>
+ <strong>Optional setting in fop.xconf file:</strong>
+ <pre>
+ <fop version="1.0">
+ <accessibility>true</accessibility>
+ ...
+ </fop>
+ </pre>
+ </li>
+ </ol>
+ <p>
+ When accessibility is enabled, additional information relating to the logical structure of
+ the document is added to the PDF. That information allows the PDF viewer (or a
+ text-to-speech application) to retrieve the natural reading order of the document.
+ </p>
+ <note>The processing of the logical structure is memory-hungry. You may need to adjust the
+ Java heap size in order to process larger files.</note>
+ </section>
+ <section id="source">
+ <title>Changes to your XSL-FO input files</title>
+ <p>
+ Apache FOP cannot automatically generate accessible PDFs. Some of the work can only be
+ performed by the content provider. Following are some changes that may be necessary to
+ your XSL-FO content in order to generate really accessible documents:
+ </p>
+ <ul>
+ <li>Table cells must have a table row as their parent.</li>
+ <li>
+ Images must have an alternate text: use the <code>fox:alt-text</code> extension attribute
+ (in the <a href="extensions.html#fox-namespace">fox namespace</a>) on
+ <code>fo:external-graphic</code> and <code>fo:instream-foreign-object</code> to specify a
+ short text describing the image.
+ </li>
+ <li>
+ Ensure that the order of <code>fo:block-container</code> elements in a page corresponds to
+ the reading order.
+ </li>
+ <li>
+ Specify the natural language of the document using the language and country properties
+ (or via the <code>xml:lang</code> shorthand property).
+ </li>
+ </ul>
+ </section>
+ <section id="customTags">
+ <title>Customized Tagging</title>
+ <p>The <a href="#PDFReference">PDF Reference</a> defines a set of standard Structure Types to
+ tag content. For example, âPâ is used for identifying paragraphs, âH1â to âH6â for headers,
+ âLâ for lists, âDivâ for block-level groups of elements, etc. This standard set is aimed at
+ improving interoperability between applications producing or consuming PDF. </p>
+ <p>FOP provides a default mapping of Formatting Objects to elements from that standard set.
+ For example, <code>fo:page-sequence</code> is mapped to âPartâ, <code>fo:block</code> is
+ mapped to âPâ, <code>fo:list-block</code> to âLâ, etc.</p>
+ <p>You may want to customize that mapping to improve the accuracy of the tagging or deal with
+ particular FO constructs. For example, you may want to make use of the âH1â to âH6â tags to
+ make the hierarchical structure of the document appear in the PDF. This is achieved by using
+ the <code>role</code> XSL-FO property:</p>
+ <source>...
+<fo:block role="H1" font-weight="bold">I. A Level 1 Heading</fo:block>
+<fo:block>This is the first paragraph of the first section...</fo:block>
+...</source>
+ <p>If a non-standard structure type is specified, FOP will issue a warning and fall back to
+ the default tag associated to the Formatting Object.</p>
+ </section>
+ <section id="testing">
+ <title>Testing</title>
+ <p>
+ Accessible PDFs can be tested, for example, using Adobe Acrobat Professional. Its
+ Accessibility Check feature creates a report indicating any deficiencies with a PDF
+ document. Alternatively, you can just let a screen reader read the document aloud.
+ </p>
+ </section>
+ <section id="limitations">
+ <title>Limitations</title>
+ <p>
+ Accessibility support in Apache FOP is relatively new, so there are certain
+ limitations. Please help us identify and close any gaps.
+ </p>
+ <ul>
+ <li>
+ The natural language can currently only be specified at the page-sequence level. The
+ document language is derived from the language of the first page-sequence. It is
+ currently not possible to override the language inside the content below the
+ page-sequence level.
+ </li>
+ <li>
+ It's currently not possible to specify the expanded form of an abbreviation or acronym.
+ </li>
+ <li>
+ SVG graphics (or images in general) are treated as a single figure. Text contained in
+ SVGs is not accessible. It's only possible to work with <code>fox:alt-text</code>.
+ </li>
+ <li>
+ The side regions (region-before, region-after etc.) are currently not specially
+ identified. Screen readers may read their content at page changes.
+ </li>
+ </ul>
+ </section>
+ <section id="links">
+ <title>Related Links</title>
+ <p>
+ Many resources providing guidance about creating accessible documents can be found on the
+ web. Here are a few links, along with additional resources around the topic:
+ </p>
+ <ul>
+ <li><a href="http://www.section508.gov/">US Government - Website on Section 508</a></li>
+ <li><a href="http://en.wikipedia.org/wiki/Accessibility">Wikipedia on Accessibility in general</a></li>
+ <li><a href="http://en.wikipedia.org/wiki/Portable_Document_Format#Accessibility">Wikipedia on Accessibility in PDF</a></li>
+ <li id="PDFReference">
+ <a href="http://partners.adobe.com/public/developer/en/pdf/PDFReference.pdf">PDF
+ Reference 1.4</a> (look up chapters 9.7 "Tagged PDF" and 9.8 "Accessibility Support")
+ </li>
+ <li><a href="pdfa.html">PDF/A support in Apache FOP</a></li>
+ <li><a href="http://wiki.apache.org/xmlgraphics-fop/PDF_Accessibility">Developer-oriented details on the accessibility features (on the Wiki)</a></li>
+ </ul>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Added: xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/anttask.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/anttask.xml?rev=1357814&view=auto
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/anttask.xml (added)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/anttask.xml Thu Jul 5 19:15:13 2012
@@ -0,0 +1,236 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id$ -->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>Apache⢠FOP: Ant task</title>
+ <version>$Revision$</version>
+ </header>
+ <body>
+ <p>
+ Apache⢠FOP provides an Ant task for automating the document build process.
+ </p>
+ <section id="basics">
+ <title>Description</title>
+ <p>
+ The FOP Ant task will convert XSL-FO documents to PDF, PS, PCL etc. output
+ (see <a href="output.html">Output formats</a> for available formats).
+ </p>
+ <p>
+ To call FOP tasks within Ant, first add a FOP task definition to your Ant build file.
+ One method of defining the task is as follows:
+ </p>
+ <source><![CDATA[
+<property name="fop.home" value="....path to your FOP HOME directory..."/>
+
+<taskdef name="fop"
+ classname="org.apache.fop.tools.anttasks.Fop">
+ <classpath>
+ <fileset dir="${fop.home}/lib">
+ <include name="*.jar"/>
+ </fileset>
+ <fileset dir="${fop.home}/build">
+ <include name="fop.jar"/>
+ <include name="fop-hyph.jar" />
+ </fileset>
+ </classpath>
+</taskdef>
+ ]]></source>
+<p>
+ Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.</p>
+ </section>
+ <!-- TODO: Installation/Configuration -->
+ <section id="parameters"><title>Parameters for FOP Ant task</title>
+ <table><caption>Parameters specified as attributes</caption>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required</th>
+ </tr>
+ <tr>
+ <td>fofile</td>
+ <td>XSL-FO file to be rendered</td>
+ <td>Yes, if no fileset nested element is used</td>
+ </tr>
+ <tr>
+ <td>xmlfile</td>
+ <td>XML input file</td>
+ <td>Yes, if no fofile is specified</td>
+ </tr>
+ <tr>
+ <td>xsltfile</td>
+ <td>XSLT input file</td>
+ <td>Yes, if no fofile is specified</td>
+ </tr>
+ <tr>
+ <td>outfile</td>
+ <td>Output filename</td>
+ <td>Yes, when fofile is used. (This attribute is not valid for filesets.)</td>
+ </tr>
+ <tr>
+ <td>format</td>
+ <td>Possible output formats:<br/>
+ <code>application/X-fop-awt-preview</code><br/>
+ <code>application/X-fop-print</code><br/>
+ <code>application/X-fop-areatree</code><br/>
+ <code>application/pdf</code><br/>
+ <code>application/postscript</code><br/>
+ <code>application/mif</code><br/>
+ <code>application/rtf</code>,
+ <code>text/richtext</code>,
+ <code>text/rtf</code><br/>
+ <code>application/x-pcl</code>,
+ <code>application/vnd.hp-PCL</code><br/>
+ <code>application/x-afp</code>,
+ <code>application/vnd.ibm.modcap</code><br/>
+ <code>text/plain</code><br/>
+ <code>image/svg+xml</code><br/>
+ <code>image/gif</code><br/>
+ <code>image/png</code><br/>
+ <code>image/tiff</code><br/>
+ </td>
+ <td>No, defaults to <code>application/pdf</code></td>
+ </tr>
+ <tr>
+ <td>outdir</td>
+ <td>Output directory</td>
+ <td>Required if a fileset is used to specify the files to render; optional for fofile. (Can alternatively specify the full path in the fofile value.)</td>
+ </tr>
+ <tr>
+ <td>force</td>
+ <td>Recreate target files, even if they are newer than their corresponding
+ source files. Note: This attribute is available in post-0.20.5
+ versions (0.20.x nightly build and 1.0dev) only; target files are
+ always generated (i.e., force=true) in 0.20.5 release.
+ </td>
+ <td>No, default is <code>false</code></td>
+ </tr>
+ <tr>
+ <td>basedir</td>
+ <td>Base directory to resolve relative references (e.g., graphics files) within the
+ FO document.
+ </td>
+ <td>No, for single FO File entry, default is to use the location
+ of that FO file.
+ </td>
+ </tr>
+ <tr>
+ <td>relativebase</td>
+ <td>For fileset usage only. A value of <code>true</code> specifies using the location
+ of each .fo file as the base directory for resolving relative file references located
+ within that .fo file. A value of <code>false</code> specifies using the value of
+ basedir for all files within the fileset, or just the current working directory
+ if basedir is not specified.
+ </td>
+ <td>No, default is <code>false</code>.
+ </td>
+ </tr>
+ <tr>
+ <td>userconfig</td>
+ <td>User configuration file (same as the FOP "-c" command line option).</td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>messagelevel</td>
+ <td>Logging level<br/>
+ Possible values: <code>error</code>, <code>warn</code>, <code>info</code>, <code>verbose</code>, <code>debug</code>. <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
+ <td>No, defaults to <code>verbose</code></td>
+ </tr>
+ <tr>
+ <td>logFiles</td>
+ <td>Controls whether the names of the files that are processed are logged
+ (<code>true</code>) or not (<code>false</code>). <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
+ <td>No, default is <code>true</code></td>
+ </tr>
+ <tr>
+ <td>throwexceptions</td>
+ <td>Controls whether or not an exception is thrown if an error occurs during rendering.</td>
+ <td>Default is <code>true</code></td>
+ </tr>
+ </table>
+ <p/>
+ <table><caption>Parameters specified as nested elements</caption>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required</th>
+ </tr>
+ <tr>
+ <td>fileset</td>
+ <td><a href="http://ant.apache.org/manual/CoreTypes/fileset.html">FileSets</a>
+ are used to specify multiple XSL-FO files to be rendered.</td>
+ <td>Yes, if no fofile attribute is supplied</td>
+ </tr>
+ </table>
+ </section>
+ <section id="examples">
+ <title>Examples</title>
+ <p>
+ The following example converts a single XSL-FO file to a PDF document:
+ </p>
+
+ <source><![CDATA[
+<target name="generate-pdf" description="Generates a single PDF file">
+ <fop format="application/pdf"
+ fofile="c:\working\foDirectory\foDocument.fo"
+ outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
+</target>
+ ]]></source>
+ <p>
+ This example converts all XSL-FO files within an entire directory to PostScript:
+ </p>
+ <source><![CDATA[
+<target name="generate-multiple-ps"
+ description="Generates multiple PostScript files">
+ <fop format="application/postscript"
+ outdir="${build.dir}" messagelevel="debug">
+ <fileset dir="${fo.examples.dir}">
+ <include name="*.fo"/>
+ </fileset>
+ </fop>
+</target>
+ ]]></source>
+ <p>
+ The following example transforms and converts a single XML and XSLT file to an AFP document:
+ </p>
+ <source><![CDATA[
+<target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
+ <fop format="application/x-afp"
+ xmlfile="c:\working\foDirectory\Document.xml"
+ xsltfile="c:\working\foDirectory\Document.xslt"
+ outfile="c:\working\afpDirectory\Document.afp" />
+</target>
+ ]]></source>
+ <p>
+ This example transforms and converts all XML files within an entire directory to PostScript:
+ </p>
+ <source><![CDATA[
+<target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
+ <fop format="application/postscript"
+ xsltfile="c:\working\foDirectory\Document.xslt"
+ outdir="${build.dir}" messagelevel="debug">
+ <fileset dir="${test.dir}">
+ <include name="*.xml"/>
+ </fileset>
+ </fop>
+</target>
+ ]]></source>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Added: xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/compiling.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/compiling.xml?rev=1357814&view=auto
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/compiling.xml (added)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/compiling.xml Thu Jul 5 19:15:13 2012
@@ -0,0 +1,147 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id$ -->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>Apache⢠FOP: Building from Source Code</title>
+ <version>$Revision$</version>
+ </header>
+ <body>
+ <section id="build-needed">
+ <title>Do You Need To Build?</title>
+<!-- text for released versions -->
+<!-- <p>
+ FOP distributions are either pre-compiled binary or source.
+ If you are using a binary distribution, it is already built and there is no need to build it again.
+ See the <a href="../download.html">Download Instructions</a> for information about whether a
+ binary or source distribution is best for your needs.
+ </p>-->
+<!-- /text for released versions -->
+<!-- text for trunk -->
+ <p>
+ Apache⢠FOP snapshots are either pre-compiled binary or source.
+ If you are using a binary snapshot, it is already built and there is no need to build it again.
+ If you got the source code from a repository snapshot or via Subversion you will need to build FOP.
+ See the <a href="../download.html">Download Instructions</a> for information about where to obtain binary or repository snapshots, and whether a
+ binary or source snapshot is best for your needs.
+ </p>
+<!-- /text for trunk -->
+ </section>
+ <section id="env">
+ <title>Set Up Your Environment</title>
+ <section id="env-jdk">
+ <title>JDK</title>
+ <p>
+ Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.4
+ (A Java Runtime Environment is not sufficient).
+ </p>
+ </section>
+ <section id="env-classpath">
+ <title>CLASSPATH</title>
+ <p>
+ There is generally no need to setup a classpath. All libraries needed to compile FOP are included
+ in the source distribution and are referenced by the build script.
+ You will only need to adjust the classpath if you build FOP in some other way. See the build
+ script build.xml for details.
+ </p>
+ </section>
+ <section id="env-java-home">
+ <title>JAVA_HOME</title>
+ <p>
+ The build script uses <a href="ext:ant">Apache Ant</a>, a popular
+ Java-based build tool, which usually requires that the environment variable JAVA_HOME point to
+ your local JDK root directory. This is true even if you use JDK 1.4 or above, which normally
+ does not need this setting.
+ </p>
+ </section>
+ <section id="env-ant">
+ <title>Apache Ant</title>
+ <p>
+ <a href="ext:ant">Apache Ant</a> (Version 1.7 or later) must be installed in order to
+ build FOP. Following best practices we don't include Ant with FOP anymore. You can find the
+ <a href="ext:ant/manual/">instructions to install Ant in the Ant manual</a> on the web.
+ </p>
+ </section>
+ </section>
+ <section id="build-script">
+ <title>Run the Build Script</title>
+ <p>
+ Change to the FOP root directory and build FOP by executing the build script (build.xml)
+ using the "ant" command.
+ </p>
+ <note>
+ The "ant" command is only available on your system if you've properly
+ <a href="ext:ant/manual/">installed Apache Ant</a> and added Ant's location to the PATH
+ environment variable.
+ </note>
+ <p>
+ The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It
+ contains information for numerous build targets, many of which are building blocks to more
+ useful target, and others which are primarily used by the FOP developers.
+ You may benefit from looking through this file to learn more about the various build targets.
+ To obtain a complete list of useful build targets:
+ </p>
+ <source>ant -projecthelp</source>
+ <p>The most useful targets are:</p>
+ <ul>
+ <li>
+ <strong>package</strong>: Generates the JAR files (default). This is the normal build that
+ produces a jar file usable for running FOP.
+ </li>
+ <li>
+ <strong>clean </strong>: Cleans the build directory. This is useful for making sure that
+ any build errors are cleaned up before starting a new build. It should not ordinarily be
+ needed, but may be helpful if you are having problems with the build process itself.
+ </li>
+ <li>
+ <strong>javadocs</strong>: Creates the FOP API documentation.
+ <note>A minimum JDK version of 1.4.2 is required for generating the javadocs.</note>
+ </li>
+ </ul>
+ <p>To run the build:</p>
+ <source>ant [target ...]</source>
+ <p>For example to do a normal build for the "all" target (which is the default):</p>
+ <source>ant</source>
+ <p>OR</p>
+ <source>ant all</source>
+ <p>To clean the build directory first:</p>
+ <source>ant clean all</source>
+ <note>
+ If you want to shorten the build time you can just call the "package" target which
+ doesn't perform any automated tests during the build.
+ </note>
+ </section>
+ <section id="problems">
+ <title id="Troubleshooting">Troubleshooting</title>
+ <p>If you have problems building FOP, please try the following:</p>
+ <ul>
+ <li>Run the build with the target of "clean", then rerun the build.</li>
+ <li>Delete the build directory completely, then rerun the build.</li>
+ <li>
+ Make sure you do not have a non-FOP version of xerces.jar, xalan.jar, batik.jar,
+ or another dependency product somewhere in your CLASSPATH.
+ </li>
+ <li>
+ If the build still fails, see the <a href="../gethelp.html">Getting Help</a>
+ page for further help.
+ </li>
+ </ul>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Added: xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/complexscripts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/complexscripts.xml?rev=1357814&view=auto
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/complexscripts.xml (added)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/1.1rc1/complexscripts.xml Thu Jul 5 19:15:13 2012
@@ -0,0 +1,694 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!-- $Id$ -->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd">
+<document>
+ <header>
+ <title>Apache⢠FOP: Complex Scripts</title>
+ </header>
+ <body>
+ <section id="overview">
+ <title>Overview</title>
+ <p>
+ This page describes the
+ <link href="http://en.wikipedia.org/wiki/Complex_scripts">complex scripts</link>
+ features of Apache⢠FOP, which include:
+ </p>
+ <ul>
+ <li>Support for languages written with right-to-left scripts, such as Arabic and Hebrew scripts.</li>
+ <li>Support for languages written with South Asian and Southeast Asian scripts, such as Devanagari,
+ Khmer, Tamil, Thai, and others.</li>
+ <li>Support for advanced substitution, reordering, and positioning of glyphs according to language
+ and script sensitive rules.</li>
+ <li>Support for advanced number to string formatting.</li>
+ </ul>
+ </section>
+ <section>
+ <title>Disabling complex scripts</title>
+ <p>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:</p>
+ <ol>
+ <li>
+ <strong>Command line:</strong> The command line option <code>-nocs</code> turns off complex script
+ features: <code>fop -nocs -fo mydocument.fo -pdf mydocument.pdf</code>
+ </li>
+ <li>
+ <strong>Embedding:</strong> <code>userAgent.setComplexScriptFeaturesEnabled(false);</code>
+ </li>
+ <li>
+ <strong>Optional setting in fop.xconf file:</strong>
+ <pre>
+<fop version="1.0">
+ <complex-scripts disabled="true"/>
+ ...
+</fop>
+ </pre>
+ </li>
+ </ol>
+ <p>
+ 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.
+ </p>
+ <note>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.</note>
+ </section>
+ <section id="source">
+ <title>Changes to your XSL-FO input files</title>
+ <p>
+ 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:
+ </p>
+ <ul>
+ <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:
+ <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 <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>
+ </ul>
+ </section>
+ <section id="details">
+ <title>Authoring Details</title>
+ <p>The complex scripts related effects of the above enumerated XSL-FO constructs are more
+ fully described in the following sub-sections.</p>
+ <section id="script_property">
+ <title>Script Property</title>
+ <p>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:
+ </p>
+ <ol>
+ <li>If the FO element that governs the text specifies 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>
+ </ol>
+ <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
+ <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">
+ <title>Standard Script Codes</title>
+ <p>The following table enumerates the standard ISO 15924 4-letter codes recognized by FOP.</p>
+ <table class="ForrestTable tw30">
+ <tr>
+ <th style="text-align:center">Code</th>
+ <th style="text-align:left">Script</th>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>arab</code></td>
+ <td>Arabic</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>beng</code></td>
+ <td>Bengali</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>bopo</code></td>
+ <td>Bopomofo</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>cyrl</code></td>
+ <td>Cyrillic</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>deva</code></td>
+ <td>Devanagari</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>ethi</code></td>
+ <td>Ethiopic</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>geor</code></td>
+ <td>Georgian</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>grek</code></td>
+ <td>Greek</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>gujr</code></td>
+ <td>Gujarati</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>guru</code></td>
+ <td>Gurmukhi</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>hang</code></td>
+ <td>Hangul</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>hani</code></td>
+ <td>Han</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>hebr</code></td>
+ <td>Hebrew</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>hira</code></td>
+ <td>Hiragana</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>kana</code></td>
+ <td>Katakana</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>knda</code></td>
+ <td>Kannada</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>khmr</code></td>
+ <td>Khmer</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>laoo</code></td>
+ <td>Lao</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>latn</code></td>
+ <td>Latin</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>mlym</code></td>
+ <td>Malayalam</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>mymr</code></td>
+ <td>Burmese</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>mong</code></td>
+ <td>Mongolian</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>orya</code></td>
+ <td>Oriya</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>sinh</code></td>
+ <td>Sinhalese</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>taml</code></td>
+ <td>Tamil</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>telu</code></td>
+ <td>Telugu</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>thai</code></td>
+ <td>Thai</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>tibt</code></td>
+ <td>Tibetan</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>zmth</code></td>
+ <td>Math</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>zsym</code></td>
+ <td>Symbol</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>zyyy</code></td>
+ <td>Undetermined</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>zzzz</code></td>
+ <td>Uncoded</td>
+ </tr>
+ </table>
+ </section>
+ <section id="extended_script_codes">
+ <title>Extended Script Codes</title>
+ <p>The following table enumerates a number of non-standard extended script codes recognized by FOP.</p>
+ <table class="ForrestTable tw70">
+ <colgrp>
+ <col style="width:10%"/>
+ <col style="width:20%"/>
+ <col style="width:80%"/>
+ </colgrp>
+ <tr>
+ <th>Code</th>
+ <th>Script</th>
+ <th>Comments</th>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>bng2</code></td>
+ <td>Bengali</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>dev2</code></td>
+ <td>Devanagari</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>gur2</code></td>
+ <td>Gurmukhi</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>gjr2</code></td>
+ <td>Gujarati</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>knd2</code></td>
+ <td>Kannada</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>mlm2</code></td>
+ <td>Malayalam</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>ory2</code></td>
+ <td>Oriya</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>tml2</code></td>
+ <td>Tamil</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ <tr>
+ <td style="text-align:center"><code>tel2</code></td>
+ <td>Telugu</td>
+ <td>OpenType Indic Version 2 (May 2008 and following) behavior.</td>
+ </tr>
+ </table>
+ <warning>
+ Explicit use of one of the above extended script codes is not portable,
+ and should be limited to use with FOP only.
+ </warning>
+ <note>
+ 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 <code>script</code>
+ property.
+ </note>
+ </section>
+ </section>
+ <section id="language_property">
+ <title>Language Property</title>
+ <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 <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
+ <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">
+ <title>Supported Scripts</title>
+ <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>
+ <colgrp>
+ <col style="width: 15%"/>
+ <col style="width: 10%"/>
+ <col style="width: 10%"/>
+ <col style="width: 65%"/>
+ </colgrp>
+ <tr>
+ <th style="text-align:left">Script</th>
+ <th>Support</th>
+ <th>Tested</th>
+ <th style="text-align:left">Comments</th>
+ </tr>
+ <tr>
+ <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><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><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><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><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><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><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><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><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><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><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><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><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><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><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><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><link href="http://en.wikipedia.org/wiki/Thai_alphabet">Thai</link></td>
+ <td class="no">none</td>
+ <td class="no">none</td>
+ <td></td>
+ </tr>
+ </table>
+ </section>
+ <section id="supported_fonts">
+ <title>Supported Fonts</title>
+ <p>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.</p>
+ <section id="fonts_arabic">
+ <title>Arabic Fonts</title>
+ <table>
+ <colgrp>
+ <col style="width: 15%"/>
+ <col style="width: 10%"/>
+ <col style="width: 10%"/>
+ <col style="width: 65%"/>
+ </colgrp>
+ <tr>
+ <th style="text-align:left">Font</th>
+ <th style="text-align:left">Version</th>
+ <th style="text-align:center">Glyphs</th>
+ <th style="text-align:left">Comments</th>
+ </tr>
+ <tr>
+ <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><link href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&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><link href="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&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><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><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><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><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><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><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>
+ </tr>
+ </table>
+ </section>
+ <section id="devanagari_fonts">
+ <title>Devanagari Fonts</title>
+ <table>
+ <colgrp>
+ <col style="width: 15%"/>
+ <col style="width: 10%"/>
+ <col style="width: 10%"/>
+ <col style="width: 65%"/>
+ </colgrp>
+ <tr>
+ <th style="text-align:left">Font</th>
+ <th style="text-align:left">Version</th>
+ <th style="text-align:center">Glyphs</th>
+ <th style="text-align:left">Comments</th>
+ </tr>
+ <tr>
+ <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><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><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><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>
+ </table>
+ </section>
+ </section>
+ <section id="limitations">
+ <title>Other Limitations</title>
+ <p>
+ Complex scripts support in Apache FOP is relatively new, so there are certain
+ limitations. Please help us identify and close any gaps.
+ </p>
+ <ul>
+ <li>Only the PDF output format fully supports complex scripts features at the present time.</li>
+ <li>Shaping context does not extend across an element boundary. This limitation prevents the use of
+ <code>fo:character</code>, <code>fo:inline</code> or <code>fo:wrapper</code> in order to colorize
+ individual Arabic letters without affecting shaping behavior across the element boundary.</li>
+ </ul>
+ </section>
+ <section id="links">
+ <title>Related Links</title>
+ <p>
+ 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:
+ </p>
+ <ul>
+ <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&item_id=CmplxRndExamples">Examples of Complex Rendering</link></li>
+ </ul>
+ </section>
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org