[aXSL-commit] SF.net SVN: axsl: [463] trunk/axsl/doc/web/font/index.html
An API for XSL-FO.
Status: Alpha
Brought to you by:
victormote
Menu
▾
▴
[aXSL-commit] SF.net SVN: axsl: [463] trunk/axsl/doc/web/font/index.html
|
From: <vic...@us...> - 2006-04-28 16:41:41
|
Revision: 463 Author: victormote Date: 2006-04-28 09:41:30 -0700 (Fri, 28 Apr 2006) ViewCVS: http://svn.sourceforge.net/axsl/?rev=463&view=rev Log Message: ----------- Move some font doc from foray to axsl. Modified Paths: -------------- trunk/axsl/doc/web/font/index.html Modified: trunk/axsl/doc/web/font/index.html =================================================================== --- trunk/axsl/doc/web/font/index.html 2006-04-28 02:54:47 UTC (rev 462) +++ trunk/axsl/doc/web/font/index.html 2006-04-28 16:41:30 UTC (rev 463) @@ -19,10 +19,14 @@ <h2>Contents</h2> <ul> <li><a href="#intro">Introduction</a></li> - <li><a href="#features">Features</a></li> - <li><a href="#configure">Font Configuration</a></li> + <li><a href="#xsl-fo">XSL-FO Conformance</a></li> <li><a href="#api">API</a></li> <li><a href="#sample">Sample Code</a></li> + <li><a href="#font-selection-strategy">Notes on +font-selection-strategy</a></li> + <li><a href="#simulated-small-caps">Notes on simulated small-caps</a></li> + <li><a href="#configure">Font Configuration</a></li> + <li><a href="#charset">Character Set</a></li> <li><a href="#implementations">Known Implementations</a></li> <li><a href="#reference-apps">Reference Applications</a></li> </ul> @@ -31,32 +35,66 @@ <p>Information on this page reflects information about the current aXSL repository.</p> -<h2><a name="features">Features</a></h2> -<ul> - <li>Unicode 4.0 compatibility. -The aXSL interfaces use 32-bit int representations for characters, providing -room for the 21-bit Unicode 4.0 extended character set. -Here are some useful links regarding this issue: - <ul> - <li><a -href="http://java.sun.com/developer/technicalArticles/Intl/Supplementary/">Supplementary -Characters in the Java Platform</a></li> - </ul> - </li> -</ul> +<h2><a name="xsl-fo">XSL-FO Conformance</a></h2> +<p>aXSLFont is intended to provide an interface that can be used to build +applications conformant to the XSL-FO standard. +The following table lists items related to this conformance. +Consult implementation documentation for implementation limitations or +exceptions:</p> +<table> + <thead> + <tr> + <td>Standard Item</td> + <td>XSL-FO 1.0 Citations</td> + <td>Conformance</td> + </tr> + </thead> + <tr> + <td>font-family</td> + <td>7.8.2</td> + <td>yes</td> + </tr> + <tr> + <td>font-selection-strategy</td> + <td>7.8.3</td> + <td>N/A. This is really an FO Tree issue. See +<a href="#font-selection-strategy">"Notes on font-selection-strategy"</a> + below.</td> + </tr> + <tr> + <td>font-size</td> + <td>7.8.4</td> + <td>Yes.</td> + </tr> + <tr> + <td>font-stretch</td> + <td>7.8.5</td> + <td>Yes.</td> + </tr> + <tr> + <td>font-size-adjust</td> + <td>7.8.6</td> + <td>N/A. This is actually not a font system issue, but an FO Tree issue.</td> + </tr> + <tr> + <td>font-style</td> + <td>7.8.7</td> + <td>Yes.</td> + </tr> + <tr> + <td>font-variant</td> + <td>7.8.8</td> + <td>Yes. See also <a href="#simulated-small-caps">"Notes on simulated + small-caps" below.</a></td> + </tr> + <tr> + <td>font-weight</td> + <td>7.8.9</td> + <td>Yes.</td> + </tr> +</table> -<h2><a name="configure">Font Configuration</a></h2> -<p>Many applications need a way for users to communicate information about -available fonts to them. -aXSL has developed a font-configuration DTD that can optionally be used for -this purpose. -It is quite possible to use the axslFont interfaces and use some other scheme -for obtaining information about available fonts. -See <a href="configure.html">Font Configuration</a> for user documentation -about this DTD.</p> - <h2><a name="api">API</a></h2> - <p>axslFont follows a client-server architecture. The client application (<strong>CA</strong>) requests information and an axslFont implementation provides it. @@ -176,6 +214,55 @@ <pre>FontServer fontServer = fontConsumer.getFontServer(); fontServer.releaseFontConsumer(fontConsumer);</pre> +<h2><a name="font-selection-strategy">Notes on font-selection-strategy</a></h2> +<p>To implement font-selection-strategy="character-by-character".</p> + +<p>Regarding font-selection-strategy="auto", the standard appears to provide +this possibility as an option for those with a specific strategy in mind. +We don't currently have such a strategy in mind. +If you would like to see a specific strategy implemented, please contact us on +the user mailing list.</p> + +<h2><a name="simulated-small-caps">Notes on simulated small-caps</a></h2> +<p>Simulated small-caps must be handled outside of the font system. +Flagging a font-description in the font-configuration file with a +simulated-font-stretch value merely does the following +1) allows that font to be selected with either normal or small-caps variant, +<em>and </em> +2) tells the font system what percentage the user wishes to use for small-caps, +if small-caps is selected. +So, for font-variant="small-caps", if a true small-caps variant for the font is +found, it will be selected. +If not, but a simulated small-caps font is available, it will be selected. +In the first case, the font system sees two different fonts with two different +sets of metrics. In the second case, it sees only one font. +The client application must handle the switching back and forth from one point +size to another to get the correct metrics information from this one font.</p> + +<h2><a name="configure">Font Configuration</a></h2> +<p>Many applications need a way for users to communicate information about +available fonts to them. +aXSL has developed a font-configuration DTD that can optionally be used for +this purpose. +It is quite possible to use the axslFont interfaces and use some other scheme +for obtaining information about available fonts. +See <a href="configure.html">Font Configuration</a> for user documentation +about this DTD.</p> + +<h2><a name="charset">Character Set</a></h2> +<ul> + <li>Unicode 4.0 compatibility. +The aXSL interfaces use 32-bit int representations for characters, providing +room for the 21-bit Unicode 4.0 extended character set. +Here are some useful links regarding this issue: + <ul> + <li><a +href="http://java.sun.com/developer/technicalArticles/Intl/Supplementary/">Supplementary +Characters in the Java Platform</a></li> + </ul> + </li> +</ul> + <h2><a name="implementations">Known Implementations</a></h2> <p>The known implementations of axslFont are:</p> <ul> @@ -183,7 +270,7 @@ </ul> <h2><a name="reference-apps">Reference Applications</a></h2> -<p>Reference applications contain working code that uses axslFont:</p> +<p>Reference applications contain working code that <em>uses </em>axslFont:</p> <ul> <li>[open source] <a href="http://www.foray.org/">FOray</a></li> </ul> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
