[FOray-commit] SF.net SVN: foray: [7090] trunk/foray/doc/web/module/font/index.html

Revision: 7090
Author:   victormote
Date:     2006-04-28 09:42:03 -0700 (Fri, 28 Apr 2006)
ViewCVS:  http://svn.sourceforge.net/foray/?rev=7090&view=rev

Log Message:
-----------
Move some font doc from foray to axsl.

Modified Paths:
--------------
    trunk/foray/doc/web/module/font/index.html
Modified: trunk/foray/doc/web/module/font/index.html
===================================================================
--- trunk/foray/doc/web/module/font/index.html	2006-04-28 01:51:24 UTC (rev 7089)
+++ trunk/foray/doc/web/module/font/index.html	2006-04-28 16:42:03 UTC (rev 7090)
@@ -18,19 +18,12 @@
 <h2>Contents</h2>
 <ul>
   <li><a href="#intro">Introduction</a></li>
-  <li><a href="#xsl-fo">XSL-FO Conformance</a>
-    <ul>
-      <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>
-    </ul>
-  </li>
   <li><a href="#system-fonts">Troubleshooting System Fonts</a></li>
 </ul>
 
 <h2><a name="intro">Introduction</a></h2>
 <p>FOrayFont is an implementation of the
-<a href="http://www.axsl.org/font/index.html" rel="external">axslFont</a>
+<a href="http://www.axsl.org/font/" rel="external">axslFont</a>
 interface, which should be consulted for details on the general API, sample
 code, etc.
 Although it is possible to use the FOrayFont package directly, there is
@@ -60,89 +53,6 @@
   for future use.</li>
 </ul>
 
-<h2><a name="xsl-fo">XSL-FO Conformance</a></h2>
-<p>FOrayFont is intended to provide tools that can be used to build applications
-conformant to the XSL-FO standard. The following table lists items related to
-this conformance:</p>
-<table>
-  <thead>
-  <tr>
-    <td>Standard Item</td>
-    <td>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>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>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>
-
-<h3><a name="font-selection-strategy">Notes on font-selection-strategy</a></h3>
-<p>FOray provides support for "character-by-character", which is also
-currently used when "auto" is selected. FOray can conceivably provide tools to
-applications that need a smarter "auto" strategy, but does not do so now.
-The standard appears to provide "auto" as an option for those with a specific
-strategy in mind, and we have no such strategy in mind.
-If you would like to see a specific strategy implemented, please contact us on
-the user mailing list.
-</p>
-
-<h3><a name="simulated-small-caps">Notes on simulated small-caps</a></h3>
-<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="system-fonts">Troubleshooting System Fonts</a></h2>
 <p>If your application is not getting the SystemFont returned that you think
 it should, check the following:</p>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.