[aXSL-commit] SF.net SVN: axsl: [511] trunk/axsl/doc/web
An API for XSL-FO.
Status: Alpha
Brought to you by:
victormote
Menu
▾
▴
[aXSL-commit] SF.net SVN: axsl: [511] trunk/axsl/doc/web
|
From: <vic...@us...> - 2006-05-05 17:48:34
|
Revision: 511 Author: victormote Date: 2006-05-05 10:48:06 -0700 (Fri, 05 May 2006) ViewCVS: http://svn.sourceforge.net/axsl/?rev=511&view=rev Log Message: ----------- Update names and locations of module docs to match new scheme. Modified Paths: -------------- trunk/axsl/doc/web/00-rsrc/include/leftmenu.html Added Paths: ----------- trunk/axsl/doc/web/area-r/ trunk/axsl/doc/web/area-r/index.html trunk/axsl/doc/web/fo-r/ trunk/axsl/doc/web/fo-r/index.html trunk/axsl/doc/web/font-r/ trunk/axsl/doc/web/font-r/configure.html trunk/axsl/doc/web/font-r/encoding.html trunk/axsl/doc/web/font-r/index.html trunk/axsl/doc/web/graphic-r/ trunk/axsl/doc/web/graphic-r/index.html trunk/axsl/doc/web/pdf-w/ trunk/axsl/doc/web/pdf-w/index.html trunk/axsl/doc/web/ps-r/ trunk/axsl/doc/web/ps-r/index.html Removed Paths: ------------- trunk/axsl/doc/web/area-out/ trunk/axsl/doc/web/area-r/index.html trunk/axsl/doc/web/fo-r/index.html trunk/axsl/doc/web/font/ trunk/axsl/doc/web/font-r/configure.html trunk/axsl/doc/web/font-r/encoding.html trunk/axsl/doc/web/font-r/index.html trunk/axsl/doc/web/fotree/ trunk/axsl/doc/web/graphic/ trunk/axsl/doc/web/graphic-r/index.html trunk/axsl/doc/web/pdf-out/ trunk/axsl/doc/web/pdf-w/index.html trunk/axsl/doc/web/ps/ trunk/axsl/doc/web/ps-r/index.html Modified: trunk/axsl/doc/web/00-rsrc/include/leftmenu.html =================================================================== --- trunk/axsl/doc/web/00-rsrc/include/leftmenu.html 2006-05-05 17:39:01 UTC (rev 510) +++ trunk/axsl/doc/web/00-rsrc/include/leftmenu.html 2006-05-05 17:48:06 UTC (rev 511) @@ -47,19 +47,19 @@ <tr> <td class="Bullet1"> </td> <td class="Menu1"> - <a class="Menu" href="/ps/">axslPS</a> + <a class="Menu" href="/ps-r/">axslPS-R</a> </td> </tr> <tr> <td class="Bullet1"> </td> <td class="Menu1"> - <a class="Menu" href="/graphic/">axslGraphic</a> + <a class="Menu" href="/graphic-r/">axslGraphic-R</a> </td> </tr> <tr> <td class="Bullet1"> </td> <td class="Menu1"> - <a class="Menu" href="/font/">axslFont</a> + <a class="Menu" href="/font-r/">axslFont-R</a> </td> </tr> <tr> @@ -71,19 +71,19 @@ <tr> <td class="Bullet1"> </td> <td class="Menu1"> - <a class="Menu" href="/pdf-out/">axslPDF-Out</a> + <a class="Menu" href="/pdf-w/">axslPDF-W</a> </td> </tr> <tr> <td class="Bullet1"> </td> <td class="Menu1"> - <a class="Menu" href="/fotree/">axslFOTree</a> + <a class="Menu" href="/fo-r/">axslFO-R</a> </td> </tr> <tr> <td class="Bullet1"> </td> <td class="Menu1"> - <a class="Menu" href="/area-out/">axslArea-Out</a> + <a class="Menu" href="/area-r/">axslArea-R</a> </td> </tr> <tr class="MenuHead"> Copied: trunk/axsl/doc/web/area-r (from rev 508, trunk/axsl/doc/web/area-out) Deleted: trunk/axsl/doc/web/area-r/index.html =================================================================== --- trunk/axsl/doc/web/area-out/index.html 2006-05-05 16:51:49 UTC (rev 508) +++ trunk/axsl/doc/web/area-r/index.html 2006-05-05 17:48:06 UTC (rev 511) @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> - -<head> - <title>aXSL: axslArea-Out</title> - <meta name="content-revised" - content="$Date$"/> - <!--#include virtual="/00-rsrc/include/standard-head.html" --> -</head> - -<body> - -<!--#include virtual="/00-rsrc/include/leftmenu.html" --> - -<h1>aXSL: axslArea-Out</h1> -<h2>Contents</h2> -<ul> - <li><a href="#intro">Introduction</a></li> - <li><a href="#implementations">Known Implementations</a></li> - <li><a href="#reference-apps">Reference Applications</a></li> -</ul> - -<h2><a name="intro">Introduction</a></h2> -<p>The Area-Out module provides interfaces for making Area Tree content -available to rendering applications.</p> - -<h2><a name="implementations">Known Implementations</a></h2> -<p>The known implementations of axslArea-Out are:</p> -<ul> - <li>[open source] <a rel="external" -href="http://www.foray.org/module/text/">FOrayArea</a></li> -</ul> - -<h2><a name="reference-apps">Reference Applications</a></h2> -<p>Reference applications contain working code that <em>uses </em>axslArea-Out:</p> -<ul> - <li>[open source] <a rel="external" href="http://www.foray.org/">FOray</a></li> -</ul> - -<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> -</body> -</html> Copied: trunk/axsl/doc/web/area-r/index.html (from rev 510, trunk/axsl/doc/web/area-out/index.html) =================================================================== --- trunk/axsl/doc/web/area-r/index.html (rev 0) +++ trunk/axsl/doc/web/area-r/index.html 2006-05-05 17:48:06 UTC (rev 511) @@ -0,0 +1,46 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> + +<head> + <title>aXSL: axslArea-Out</title> + <meta name="content-revised" + content="$Date$"/> + <!--#include virtual="/00-rsrc/include/standard-head.html" --> +</head> + +<body> + +<!--#include virtual="/00-rsrc/include/leftmenu.html" --> + +<h1>aXSL: axslArea-Out</h1> +<h2>Contents</h2> +<ul> + <li><a href="#intro">Introduction</a></li> + <li><a href="#implementations">Known Implementations</a></li> + <li><a href="#reference-apps">Reference Applications</a></li> +</ul> + +<h2><a name="intro">Introduction</a></h2> +<p>The Area-Out module provides interfaces for making Area Tree content +available to rendering applications.</p> + +<h2><a name="implementations">Known Implementations</a></h2> +<p>The known implementations of axslArea-Out are:</p> +<ul> + <li>[open source] <a rel="external" +href="http://www.foray.org/module/text/">FOrayArea</a></li> +</ul> + +<h2><a name="reference-apps">Reference Applications</a></h2> +<p>Reference applications contain working code that <em>uses </em>axslArea-Out:</p> +<ul> + <li>[open source] <a rel="external" href="http://www.foray.org/">FOray</a></li> +</ul> + +<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> +</body> +</html> Copied: trunk/axsl/doc/web/fo-r (from rev 508, trunk/axsl/doc/web/fotree) Deleted: trunk/axsl/doc/web/fo-r/index.html =================================================================== --- trunk/axsl/doc/web/fotree/index.html 2006-05-05 16:51:49 UTC (rev 508) +++ trunk/axsl/doc/web/fo-r/index.html 2006-05-05 17:48:06 UTC (rev 511) @@ -1,65 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> - -<head> - <title>aXSL: axslFOTree</title> - <meta name="content-revised" - content="$Date$"/> - <!--#include virtual="/00-rsrc/include/standard-head.html" --> -</head> - -<body> - -<!--#include virtual="/00-rsrc/include/leftmenu.html" --> - -<h1>aXSL: axslFOTree</h1> -<h2>Contents</h2> -<ul> - <li><a href="#intro">Introduction</a></li> - <li><a href="#missing">Missing Interfaces?</a></li> - <li><a href="#implementations">Known Implementations</a></li> - <li><a href="#reference-apps">Reference Applications</a></li> -</ul> - -<h2><a name="intro">Introduction</a></h2> -<p>The FOTree module provides access to the XSL-FO objects and properties in the -underlying document content. Implementations parse an FO file or content stream -and make that data available to client applications.</p> - -<h2><a name="missing">Missing Interfaces?</a></h2> -<p>There are several pagination-related XSL-FO objects that do not have -corresponding classes in the aXSL FOTree. -These are not unimportant, but their operation is entirely internal to the -FOTree. -Client applications only need to know what SimplePageMaster they should use, so -the "details" of these classes are hidden from the client applications:</p> - -<ul> - <li>LayoutMasterSet</li> - <li>PageSequenceMaster</li> - <li>SinglePageMasterReference</li> - <li>RepeatablePageMasterReference</li> - <li>RepeatablePageMasterAlternatives</li> - <li>ConditionalPageMasterReference</li> -</ul> - -<h2><a name="implementations">Known Implementations</a></h2> -<p>The known implementations of axslFOTree are:</p> -<ul> - <li>[open source] <a rel="external" -href="http://www.foray.org/module/fotree/">FOrayFOTree</a></li> -</ul> - -<h2><a name="reference-apps">Reference Applications</a></h2> -<p>Reference applications contain working code that <em>uses </em>axslFOTree:</p> -<ul> - <li>[open source] <a rel="external" href="http://www.foray.org/">FOray</a></li> -</ul> - -<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> -</body> -</html> Copied: trunk/axsl/doc/web/fo-r/index.html (from rev 510, trunk/axsl/doc/web/fotree/index.html) =================================================================== --- trunk/axsl/doc/web/fo-r/index.html (rev 0) +++ trunk/axsl/doc/web/fo-r/index.html 2006-05-05 17:48:06 UTC (rev 511) @@ -0,0 +1,65 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> + +<head> + <title>aXSL: axslFOTree</title> + <meta name="content-revised" + content="$Date$"/> + <!--#include virtual="/00-rsrc/include/standard-head.html" --> +</head> + +<body> + +<!--#include virtual="/00-rsrc/include/leftmenu.html" --> + +<h1>aXSL: axslFOTree</h1> +<h2>Contents</h2> +<ul> + <li><a href="#intro">Introduction</a></li> + <li><a href="#missing">Missing Interfaces?</a></li> + <li><a href="#implementations">Known Implementations</a></li> + <li><a href="#reference-apps">Reference Applications</a></li> +</ul> + +<h2><a name="intro">Introduction</a></h2> +<p>The FOTree module provides access to the XSL-FO objects and properties in the +underlying document content. Implementations parse an FO file or content stream +and make that data available to client applications.</p> + +<h2><a name="missing">Missing Interfaces?</a></h2> +<p>There are several pagination-related XSL-FO objects that do not have +corresponding classes in the aXSL FOTree. +These are not unimportant, but their operation is entirely internal to the +FOTree. +Client applications only need to know what SimplePageMaster they should use, so +the "details" of these classes are hidden from the client applications:</p> + +<ul> + <li>LayoutMasterSet</li> + <li>PageSequenceMaster</li> + <li>SinglePageMasterReference</li> + <li>RepeatablePageMasterReference</li> + <li>RepeatablePageMasterAlternatives</li> + <li>ConditionalPageMasterReference</li> +</ul> + +<h2><a name="implementations">Known Implementations</a></h2> +<p>The known implementations of axslFOTree are:</p> +<ul> + <li>[open source] <a rel="external" +href="http://www.foray.org/module/fotree/">FOrayFOTree</a></li> +</ul> + +<h2><a name="reference-apps">Reference Applications</a></h2> +<p>Reference applications contain working code that <em>uses </em>axslFOTree:</p> +<ul> + <li>[open source] <a rel="external" href="http://www.foray.org/">FOray</a></li> +</ul> + +<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> +</body> +</html> Copied: trunk/axsl/doc/web/font-r (from rev 508, trunk/axsl/doc/web/font) Deleted: trunk/axsl/doc/web/font-r/configure.html =================================================================== --- trunk/axsl/doc/web/font/configure.html 2006-05-05 16:51:49 UTC (rev 508) +++ trunk/axsl/doc/web/font-r/configure.html 2006-05-05 17:48:06 UTC (rev 511) @@ -1,403 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> - -<head> - <title>axslFont: Font Configuration</title> - <meta name="content-revised" - content="$Date$"/> - <!--#include virtual="/00-rsrc/include/standard-head.html" --> -</head> - -<body> - -<!--#include virtual="/00-rsrc/include/leftmenu.html" --> - -<h1>axslFont: Font Configuration</h1> -<h2>Contents</h2> -<ul> - <li><a href="#intro">Introduction</a></li> - <li><a href="#root"><axsl-font-config> element</a></li> - <li><a href="#server"><server> element</a></li> - <li><a href="#parameter"><parameter> element</a></li> - <li><a href="#glyph-list"><glyph-list> element</a></li> - <li><a href="#encoding"><encoding> element</a></li> - <li><a href="#font-group"><font-group> element</a></li> - <li><a href="#font"><font> element</a></li> - <li><a href="#font-family"><font-family> element</a></li> - <li><a href="#font-desc"><font-description> element</a></li> - <li><a href="#font-family-alias"><font-family-alias> - element</a></li> - <li><a href="#alias-configuration"><font-family-alias> - element</a></li> -</ul> - -<p class="Warning">Future changes to the font configuration are expected, so -that more features can be added.</p> - -<h3><a name="intro">Introduction</a></h3> -<p>Some applications are able to obtain all of the information that they need - about available fonts from some universal system registry, usually - maintained by the operating system. - In such cases, a font-configuration is not needed. - However, in any case where such information is not available, may not be - available, or not adequate for the application, some standard method of - communicating information about available fonts is needed. - The <a rel="external" href="/dtds/0.1/en/axsl-font-config.dtd">aXSL - font-configuration DTD</a> is an attempt to standardize the format of - such information, so that users can avoid the need to maintain multiple - configurations for multiple applications. - A <a rel="external" - href="http://svn.sourceforge.net/viewcvs.cgi/axsl/trunk/axsl/axsl-font/config/sample-axsl-font-config.xml?view=markup">sample - configuration file</a> is also provided, which may be useful either for - cut-and-paste or consultation as font-configuration files are created.</p> - -<p>The configuration contemplates two general types of fonts. First are those -for which at least some information is available from some other registry. -In this document, these are referred to as System Fonts (SF). Second are those -for which no external information is available at all. These are referred to -as Free-standing Fonts (FSF).</p> - -<p>The aXSL font-configuration is optimized for flexibility, which makes it -somewhat more verbose and complex than it could be. -It draws a sharp distinction between configuration of the font itself, which -is generally done in the <font> element, and configuration of the way it -is used and selected by an application, which is generally done in the -<font-description> element. -This distincion allows a font to be used in more than one way. -Here are some examples where this may possibly be useful:</p> -<ul> - <li>The same font to be used with more than one encoding.</li> - <li>The same font can be used in the same or different ways in more than - one font family.</li> -</ul> - -<h3><a name="root"><axsl-font-config> element</a></h3> - <p>All attributes of axsl-font-config set global defaults that can be - overridden by subsidiary elements.</p> - <ul> - <li><strong>xml:base</strong> sets the global base URL from which all - relative subsidiary URLs will be located.</li> - <li><strong>embed</strong> sets the global default value for the embed - attribute used by the font element.</li> - </ul> - -<h3><a name="server"><server> element</a></h3> -<p><strong>Important:</strong> Most users do not need to configure server - elements and can safely skip this section.</p> - -<pre><server - setup-free-standing-fonts="true" - setup-system-fonts="false"/></pre> - -<ul> - <li><strong>setup-free-standing-fonts</strong> should be set to either - "true" or "false" depending on whether free-standing fonts should be - configured.</li> - <li><strong>setup-system-fonts</strong> should be set to either "true" or - "false" depending on whether system fonts should be configured.</li> -</ul> - -<h3><a name="parameter"><parameter> element</a></h3> -<pre><parameter - key="font-root" - value="file://C:/some/path"/></pre> -<p>A parameter contains two attributes, "key" and either "value" or -"from-environment". -These are used within the configuration file as a simple substitution. -Wherever the text of "key", enclosed in curly braces, occurs in attributes, -it will be substituted with the text of "value" or with the value of the -environment variable named in "from-environment". -This is useful especially for making the paths to files more flexible.</p> - -<p>Note that support for environment variables may vary from one programming -language to another, from one environment to another, and from one -implementation to another. -For example, some java platforms only support environment variables set using -the java "-D" switch. -Others can get environment variables from the operating system. -Consult the documentation for your implementation to determine the exact level -of support for this feature.</p> - -<h3><a name="glyph-list"><glyph-list> element</a></h3> -<p><strong>Important: </strong> Most users do not need to configure custom -glyph-list elements and can safely skip this section. -If you do need to specify or create a glyph-list see the -<a href="encoding.html">Encoding</a> documentation.</p> - -<h3><a name="encoding"><encoding> element</a></h3> -<p><strong>Important: </strong> Most users do not need to configure custom -encoding elements and can safely skip this section. -If you do need to specify or create an encoding see the -<a href="encoding.html">Encoding</a> documentation.</p> - -<h3><a name="font-group"><font-group> element</a></h3> -<p>The only purpose of the font-group element is as a wrapper for font -elements that have similar attributes, or that should be grouped together -for some other reason. -An attribute set on font-group will be inherited by contained font elements, -unless those elements override the attibute.</p> - <ul> - <li><strong>label</strong> is for identification purposes only, and is - not used by the system.</li> - <li><strong>xml:base</strong> sets the base URL from which all - relative subsidiary URLs will be located.</li> - <li><strong>embed</strong> sets the default value for the embed - attribute used by the font element.</li> - </ul> - - -<h3><a name="font"><font> element</a></h3> -<p>Here is a sample <font> element in the font configuration file:</p> - -<pre><font - id="DomCasual-Adobe" - embed="subset" - metrics-file="type1/adobe/091/dc______.afm" - font-file="type1/adobe/091/dc______.pfb"> -</font></pre> - -<ul> - <li><strong>id</strong> is an XML ID type attribute, and must be unique within -the font-configuration file. -It is used to identify the font, specifically as the target of "font" -attributes in -<a href="#font-desc"><font-description></a> elements.</li> - <li><strong>embed</strong> may be set to <code>all</code>, <code>subset</code>, -or <code>none</code>, and defaults to <code>none</code>. If the font is not embedded -in the output, the document will be created correctly, but the user may not be able -to view it correctly, depending on their local viewer environment.</li> - <li><strong>metrics-file</strong> provides a URL that contains -font metric information for this font. -TrueType and OpenType fonts do not need to specifiy a metrics file, because the -font-file contains all metric information. -However, Type 1 fonts and device-embedded fonts must provide a metrics file. - - <p>Both PFM and AFM font metrics files are supported. However, -it is highly recommended that AFM files be used where possible for the -following reasons:</p> - <ul> - <li>As far as we can tell, PFM files are only usable for fonts that - are encoded using WinAnsiEncoding. We do not know how to map Unicode - characters to symbolic fonts or other non-ANSI character sets.</li> - <li>Since only WinAnsiEncoding is supported, only characters available - in that encoding can be used. Many fonts have additional characters - that can be accessed using other encodings, but that encoding data is - not stored in a PFM file.</li> - <li>PFM files are limited to 512 kerning pairs. Many fonts have more - than 512 pairs, so some pairs that would be kerned using an AFM file - will not be kerned using a PFM file.</li> - <li>The PFM format is a Microsoft format that appears to be no longer - supported by them.</li> - <li>PFM files are binary files, not readily edited. AFM files on the - other hand are text files, which can be edited. This of course is both - useful and dangerous.</li> - </ul> - </li> - <li><strong>font-file</strong> provides a file path or URL to the font file -itself. -Required for fonts that will be embedded and for fonts that do not have a -separate metrics file.</li> -</ul> - -<p>For both metrics-file and font-file, relative paths and URLs are resolved -relative to any parent xml:base attribute. -Relative xml:base attributes are themselves resolved relative to any parent -xml:base attribute. -If no xml:base attribute is set on the root element, applications my set the -base either to some configured value known to them, or to the current working -directory.</p> - -<p>The description above is for the typical configuration of a free-standing - font. - Some applications need to be able to concurrently support and configure - system fonts along with free-standing fonts. - These can be obtained in one of two ways:</p> -<ul> - <li>If the applications supports it, SFs can be obtained by simply asking - for them by name. - To specify this, exclude the "embed", "metrics-file", and "font-file" - attributes.</li> - <li>If the application supports it, SFs can be manufactured from a font file - in much the same manner as a free-standing font. - The advantage to this method is that the font can be embedded in an output - document. - To use this approach, you must include the "embed" and "font-file" - attributes in the same way that you would for a free-standing font.</li> -</ul> -<p>In either of these cases, the following attribute must be included for the - <font> element.</p> -<ul> - <li><strong>system-name</strong> (optional) is the name which should be - supplied to the external registry when requesting the System Font. - Note that this is the name of the <em>font</em>, not the - <em>font-family</em>.</li> -</ul> - -<p>The <font> is intended to represent exactly one logical font. -This font can be a simple SF, a simple FSF, or a font that can manifest itself -as both an SF and an FSF. -In some cases it is possible to abuse the <font> element to represent -one SF and a different FSF. -This practice is discouraged. -A better solution is to use the <font-family-alias> and related -<alias-configuration> elements to alias different fonts in different -circumstances.</p> - -<h3><a name="font-family"><font-family> element</a></h3> -<p>The font-family element contains one or more font-description elements. -When the font-family is selected in a document, the font-description elements -are searched for a match on the remaining descriptive items (weight, style, -etc.)</p> - -<ul> - <li><strong>name</strong> (required) is the value that should be matched - against the font-family provided in the document.</li> - <li><strong>embed</strong> (optional) is the default embed value for all - contained font-description elements.</li> - <li><strong>simulate-small-caps</strong> (optional) is the default - simulate-small-caps value for all contained font-description elements.</li> -</ul> - -<h3><a name="font-desc"><font-description> element</a></h3> -<pre><font-description - font="NewBaskervilleItalic-Adobe" - style="italic" - weight="normal" - simulate-small-caps="80%" - encoding="WinAnsiEncoding"/></pre> - -<ul> - <li><strong>font</strong> (required) is an XML IDREF type attribute, and - must match the "id" attribute of some <font> element.</li> - <li><strong>style</strong> (optional, default "normal") = normal | italic - | oblique | backslant. - Corresponds to the XSL-FO font-style property.</li> - <li><strong>weight</strong> (optional, default "normal") = 100 | 200 | 300 - | (normal | 400) | 500 | 600 | (bold | 700) | 800 | 900. - Corresponds to the XSL-FO font-weight property. Following is an - unofficial guide to the weight values: - <table> - <thead> - <tr> - <td>Description</td> - <td>Weight</td> - </tr> - </thead> - <tbody> - <tr> - <td>Ultralight</td> - <td>100</td> - </tr> - <tr> - <td>Light</td> - <td>200</td> - </tr> - <tr> - <td>SemiLight</td> - <td>300</td> - </tr> - <tr> - <td>Normal, Regular, Roman, Book</td> - <td>400</td> - </tr> - <tr> - <td>Medium</td> - <td>500</td> - </tr> - <tr> - <td>SemiBold</td> - <td>600</td> - </tr> - <tr> - <td>Bold</td> - <td>700</td> - </tr> - <tr> - <td>Black</td> - <td>800</td> - </tr> - <tr> - <td>UltraBlack</td> - <td>900</td> - </tr> - </tbody> - - </table> - </li> - <li><strong>simulate-small-caps</strong> takes a percentage, and the "%" - character should be included. - It performs two functions for applications that can simulate small-caps. - First, in the font-selection process, the existence of this attribute - indicates that this font-description can be selected when small-caps are - needed (it can also be selected when small-caps are not needed). - Second, if selected, it tells the application what percentage of the - font-size that is used for regular caps should be used for the simulated - small-cap glyphs. - For example, a value of "80%", when applied to a font-size of 12 points, - will result in small-caps at 9.6 points. - </li> - <li><strong>encoding</strong> (optional, default "InternalEncoding") - corresponds to a defined encoding scheme. - This attribute is generally useful only for Type 1 fonts. - It should typically be set to "WinAnsiEncoding" for fonts using a standard - Roman character set, and to "InternalEncoding" (the default) for most other - fonts. - However, other standard encodings are available, and custom encodings can - be created if needed. - See <a href="encoding.html">Encoding</a> for details.</li> -</ul> - -<p>Note that the purpose of separating a font-description from its underlying -font is to allow the same font to be used multiple ways. -The same font can be used within different font-family entries, and can be -defined with different characteristics.</p> - -<p>The result of defining two font-description elements with identical -characteristics in the same font family is undefined. -With 9 font-stretch possibilities, 4 for font-style, 2 for font-variant, and 9 -for font-weight, there are 648 possible fonts in a font-family.</p> - -<h3><a name="font-family-alias"><font-family-alias> element</a></h3> - <pre><font-family-alias alias="sans-serif" - default-family="Base14-Helvetica"> - <alias-configuration name="pdf" font-family="Base14-Helvetica"/> - <alias-configuration name="awt" font-family="AWT-sans-serif"/> -</font-family-alias></pre> -<p>The <font-family-alias> and child <alias-configuration> -elements are designed to allow a font-configuration to be used for different -purposes. -The combination of the two allows a font-family to be accessed using more than -one name, and allows more than one font-family to be accessed using the same -name. -In the example above, the font-family "Base14-Helvetica" can be accessed using -either the font-family name "Base14-Helvetica" or its alias "sans-serif". -On the other hand, the alias "sans-serif" can point to either "Base14-Helvetica" -or "AWT-sans-serif", depending on the context or active configuration.</p> - -<ul> - <li><strong>alias</strong> (required) defines the alias name that should be - matched to the font-family requested.</li> - <li>default-family (required) indicates the name of the font-family that - should be substituted for the alias if no matching child - <alias-configuration> element is found.</li> -</ul> - -<h3><a name="alias-configuration"><alias-configuration> element</a></h3> -<p>The <alias-configuration> element is an optional child to the -<font-family-alias> element, and allows an alias name to point to -different font-family elements depending upon some configuration name. -The configuration name is application-dependent. -Some applications may choose not to use them at all, and others may have -a complex scheme for determining which configuration to use in a given -circumstance. -A typical use is to distinguish between fonts available for print applications, -like PDF and PostScript, from those available for viewing documents on the -screen, such as AWT applications.</p> - -<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> -</body> -</html> Copied: trunk/axsl/doc/web/font-r/configure.html (from rev 510, trunk/axsl/doc/web/font/configure.html) =================================================================== --- trunk/axsl/doc/web/font-r/configure.html (rev 0) +++ trunk/axsl/doc/web/font-r/configure.html 2006-05-05 17:48:06 UTC (rev 511) @@ -0,0 +1,403 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> + +<head> + <title>axslFont: Font Configuration</title> + <meta name="content-revised" + content="$Date$"/> + <!--#include virtual="/00-rsrc/include/standard-head.html" --> +</head> + +<body> + +<!--#include virtual="/00-rsrc/include/leftmenu.html" --> + +<h1>axslFont: Font Configuration</h1> +<h2>Contents</h2> +<ul> + <li><a href="#intro">Introduction</a></li> + <li><a href="#root"><axsl-font-config> element</a></li> + <li><a href="#server"><server> element</a></li> + <li><a href="#parameter"><parameter> element</a></li> + <li><a href="#glyph-list"><glyph-list> element</a></li> + <li><a href="#encoding"><encoding> element</a></li> + <li><a href="#font-group"><font-group> element</a></li> + <li><a href="#font"><font> element</a></li> + <li><a href="#font-family"><font-family> element</a></li> + <li><a href="#font-desc"><font-description> element</a></li> + <li><a href="#font-family-alias"><font-family-alias> + element</a></li> + <li><a href="#alias-configuration"><font-family-alias> + element</a></li> +</ul> + +<p class="Warning">Future changes to the font configuration are expected, so +that more features can be added.</p> + +<h3><a name="intro">Introduction</a></h3> +<p>Some applications are able to obtain all of the information that they need + about available fonts from some universal system registry, usually + maintained by the operating system. + In such cases, a font-configuration is not needed. + However, in any case where such information is not available, may not be + available, or not adequate for the application, some standard method of + communicating information about available fonts is needed. + The <a rel="external" href="/dtds/0.1/en/axsl-font-config.dtd">aXSL + font-configuration DTD</a> is an attempt to standardize the format of + such information, so that users can avoid the need to maintain multiple + configurations for multiple applications. + A <a rel="external" + href="http://svn.sourceforge.net/viewcvs.cgi/axsl/trunk/axsl/axsl-font/config/sample-axsl-font-config.xml?view=markup">sample + configuration file</a> is also provided, which may be useful either for + cut-and-paste or consultation as font-configuration files are created.</p> + +<p>The configuration contemplates two general types of fonts. First are those +for which at least some information is available from some other registry. +In this document, these are referred to as System Fonts (SF). Second are those +for which no external information is available at all. These are referred to +as Free-standing Fonts (FSF).</p> + +<p>The aXSL font-configuration is optimized for flexibility, which makes it +somewhat more verbose and complex than it could be. +It draws a sharp distinction between configuration of the font itself, which +is generally done in the <font> element, and configuration of the way it +is used and selected by an application, which is generally done in the +<font-description> element. +This distincion allows a font to be used in more than one way. +Here are some examples where this may possibly be useful:</p> +<ul> + <li>The same font to be used with more than one encoding.</li> + <li>The same font can be used in the same or different ways in more than + one font family.</li> +</ul> + +<h3><a name="root"><axsl-font-config> element</a></h3> + <p>All attributes of axsl-font-config set global defaults that can be + overridden by subsidiary elements.</p> + <ul> + <li><strong>xml:base</strong> sets the global base URL from which all + relative subsidiary URLs will be located.</li> + <li><strong>embed</strong> sets the global default value for the embed + attribute used by the font element.</li> + </ul> + +<h3><a name="server"><server> element</a></h3> +<p><strong>Important:</strong> Most users do not need to configure server + elements and can safely skip this section.</p> + +<pre><server + setup-free-standing-fonts="true" + setup-system-fonts="false"/></pre> + +<ul> + <li><strong>setup-free-standing-fonts</strong> should be set to either + "true" or "false" depending on whether free-standing fonts should be + configured.</li> + <li><strong>setup-system-fonts</strong> should be set to either "true" or + "false" depending on whether system fonts should be configured.</li> +</ul> + +<h3><a name="parameter"><parameter> element</a></h3> +<pre><parameter + key="font-root" + value="file://C:/some/path"/></pre> +<p>A parameter contains two attributes, "key" and either "value" or +"from-environment". +These are used within the configuration file as a simple substitution. +Wherever the text of "key", enclosed in curly braces, occurs in attributes, +it will be substituted with the text of "value" or with the value of the +environment variable named in "from-environment". +This is useful especially for making the paths to files more flexible.</p> + +<p>Note that support for environment variables may vary from one programming +language to another, from one environment to another, and from one +implementation to another. +For example, some java platforms only support environment variables set using +the java "-D" switch. +Others can get environment variables from the operating system. +Consult the documentation for your implementation to determine the exact level +of support for this feature.</p> + +<h3><a name="glyph-list"><glyph-list> element</a></h3> +<p><strong>Important: </strong> Most users do not need to configure custom +glyph-list elements and can safely skip this section. +If you do need to specify or create a glyph-list see the +<a href="encoding.html">Encoding</a> documentation.</p> + +<h3><a name="encoding"><encoding> element</a></h3> +<p><strong>Important: </strong> Most users do not need to configure custom +encoding elements and can safely skip this section. +If you do need to specify or create an encoding see the +<a href="encoding.html">Encoding</a> documentation.</p> + +<h3><a name="font-group"><font-group> element</a></h3> +<p>The only purpose of the font-group element is as a wrapper for font +elements that have similar attributes, or that should be grouped together +for some other reason. +An attribute set on font-group will be inherited by contained font elements, +unless those elements override the attibute.</p> + <ul> + <li><strong>label</strong> is for identification purposes only, and is + not used by the system.</li> + <li><strong>xml:base</strong> sets the base URL from which all + relative subsidiary URLs will be located.</li> + <li><strong>embed</strong> sets the default value for the embed + attribute used by the font element.</li> + </ul> + + +<h3><a name="font"><font> element</a></h3> +<p>Here is a sample <font> element in the font configuration file:</p> + +<pre><font + id="DomCasual-Adobe" + embed="subset" + metrics-file="type1/adobe/091/dc______.afm" + font-file="type1/adobe/091/dc______.pfb"> +</font></pre> + +<ul> + <li><strong>id</strong> is an XML ID type attribute, and must be unique within +the font-configuration file. +It is used to identify the font, specifically as the target of "font" +attributes in +<a href="#font-desc"><font-description></a> elements.</li> + <li><strong>embed</strong> may be set to <code>all</code>, <code>subset</code>, +or <code>none</code>, and defaults to <code>none</code>. If the font is not embedded +in the output, the document will be created correctly, but the user may not be able +to view it correctly, depending on their local viewer environment.</li> + <li><strong>metrics-file</strong> provides a URL that contains +font metric information for this font. +TrueType and OpenType fonts do not need to specifiy a metrics file, because the +font-file contains all metric information. +However, Type 1 fonts and device-embedded fonts must provide a metrics file. + + <p>Both PFM and AFM font metrics files are supported. However, +it is highly recommended that AFM files be used where possible for the +following reasons:</p> + <ul> + <li>As far as we can tell, PFM files are only usable for fonts that + are encoded using WinAnsiEncoding. We do not know how to map Unicode + characters to symbolic fonts or other non-ANSI character sets.</li> + <li>Since only WinAnsiEncoding is supported, only characters available + in that encoding can be used. Many fonts have additional characters + that can be accessed using other encodings, but that encoding data is + not stored in a PFM file.</li> + <li>PFM files are limited to 512 kerning pairs. Many fonts have more + than 512 pairs, so some pairs that would be kerned using an AFM file + will not be kerned using a PFM file.</li> + <li>The PFM format is a Microsoft format that appears to be no longer + supported by them.</li> + <li>PFM files are binary files, not readily edited. AFM files on the + other hand are text files, which can be edited. This of course is both + useful and dangerous.</li> + </ul> + </li> + <li><strong>font-file</strong> provides a file path or URL to the font file +itself. +Required for fonts that will be embedded and for fonts that do not have a +separate metrics file.</li> +</ul> + +<p>For both metrics-file and font-file, relative paths and URLs are resolved +relative to any parent xml:base attribute. +Relative xml:base attributes are themselves resolved relative to any parent +xml:base attribute. +If no xml:base attribute is set on the root element, applications my set the +base either to some configured value known to them, or to the current working +directory.</p> + +<p>The description above is for the typical configuration of a free-standing + font. + Some applications need to be able to concurrently support and configure + system fonts along with free-standing fonts. + These can be obtained in one of two ways:</p> +<ul> + <li>If the applications supports it, SFs can be obtained by simply asking + for them by name. + To specify this, exclude the "embed", "metrics-file", and "font-file" + attributes.</li> + <li>If the application supports it, SFs can be manufactured from a font file + in much the same manner as a free-standing font. + The advantage to this method is that the font can be embedded in an output + document. + To use this approach, you must include the "embed" and "font-file" + attributes in the same way that you would for a free-standing font.</li> +</ul> +<p>In either of these cases, the following attribute must be included for the + <font> element.</p> +<ul> + <li><strong>system-name</strong> (optional) is the name which should be + supplied to the external registry when requesting the System Font. + Note that this is the name of the <em>font</em>, not the + <em>font-family</em>.</li> +</ul> + +<p>The <font> is intended to represent exactly one logical font. +This font can be a simple SF, a simple FSF, or a font that can manifest itself +as both an SF and an FSF. +In some cases it is possible to abuse the <font> element to represent +one SF and a different FSF. +This practice is discouraged. +A better solution is to use the <font-family-alias> and related +<alias-configuration> elements to alias different fonts in different +circumstances.</p> + +<h3><a name="font-family"><font-family> element</a></h3> +<p>The font-family element contains one or more font-description elements. +When the font-family is selected in a document, the font-description elements +are searched for a match on the remaining descriptive items (weight, style, +etc.)</p> + +<ul> + <li><strong>name</strong> (required) is the value that should be matched + against the font-family provided in the document.</li> + <li><strong>embed</strong> (optional) is the default embed value for all + contained font-description elements.</li> + <li><strong>simulate-small-caps</strong> (optional) is the default + simulate-small-caps value for all contained font-description elements.</li> +</ul> + +<h3><a name="font-desc"><font-description> element</a></h3> +<pre><font-description + font="NewBaskervilleItalic-Adobe" + style="italic" + weight="normal" + simulate-small-caps="80%" + encoding="WinAnsiEncoding"/></pre> + +<ul> + <li><strong>font</strong> (required) is an XML IDREF type attribute, and + must match the "id" attribute of some <font> element.</li> + <li><strong>style</strong> (optional, default "normal") = normal | italic + | oblique | backslant. + Corresponds to the XSL-FO font-style property.</li> + <li><strong>weight</strong> (optional, default "normal") = 100 | 200 | 300 + | (normal | 400) | 500 | 600 | (bold | 700) | 800 | 900. + Corresponds to the XSL-FO font-weight property. Following is an + unofficial guide to the weight values: + <table> + <thead> + <tr> + <td>Description</td> + <td>Weight</td> + </tr> + </thead> + <tbody> + <tr> + <td>Ultralight</td> + <td>100</td> + </tr> + <tr> + <td>Light</td> + <td>200</td> + </tr> + <tr> + <td>SemiLight</td> + <td>300</td> + </tr> + <tr> + <td>Normal, Regular, Roman, Book</td> + <td>400</td> + </tr> + <tr> + <td>Medium</td> + <td>500</td> + </tr> + <tr> + <td>SemiBold</td> + <td>600</td> + </tr> + <tr> + <td>Bold</td> + <td>700</td> + </tr> + <tr> + <td>Black</td> + <td>800</td> + </tr> + <tr> + <td>UltraBlack</td> + <td>900</td> + </tr> + </tbody> + + </table> + </li> + <li><strong>simulate-small-caps</strong> takes a percentage, and the "%" + character should be included. + It performs two functions for applications that can simulate small-caps. + First, in the font-selection process, the existence of this attribute + indicates that this font-description can be selected when small-caps are + needed (it can also be selected when small-caps are not needed). + Second, if selected, it tells the application what percentage of the + font-size that is used for regular caps should be used for the simulated + small-cap glyphs. + For example, a value of "80%", when applied to a font-size of 12 points, + will result in small-caps at 9.6 points. + </li> + <li><strong>encoding</strong> (optional, default "InternalEncoding") + corresponds to a defined encoding scheme. + This attribute is generally useful only for Type 1 fonts. + It should typically be set to "WinAnsiEncoding" for fonts using a standard + Roman character set, and to "InternalEncoding" (the default) for most other + fonts. + However, other standard encodings are available, and custom encodings can + be created if needed. + See <a href="encoding.html">Encoding</a> for details.</li> +</ul> + +<p>Note that the purpose of separating a font-description from its underlying +font is to allow the same font to be used multiple ways. +The same font can be used within different font-family entries, and can be +defined with different characteristics.</p> + +<p>The result of defining two font-description elements with identical +characteristics in the same font family is undefined. +With 9 font-stretch possibilities, 4 for font-style, 2 for font-variant, and 9 +for font-weight, there are 648 possible fonts in a font-family.</p> + +<h3><a name="font-family-alias"><font-family-alias> element</a></h3> + <pre><font-family-alias alias="sans-serif" + default-family="Base14-Helvetica"> + <alias-configuration name="pdf" font-family="Base14-Helvetica"/> + <alias-configuration name="awt" font-family="AWT-sans-serif"/> +</font-family-alias></pre> +<p>The <font-family-alias> and child <alias-configuration> +elements are designed to allow a font-configuration to be used for different +purposes. +The combination of the two allows a font-family to be accessed using more than +one name, and allows more than one font-family to be accessed using the same +name. +In the example above, the font-family "Base14-Helvetica" can be accessed using +either the font-family name "Base14-Helvetica" or its alias "sans-serif". +On the other hand, the alias "sans-serif" can point to either "Base14-Helvetica" +or "AWT-sans-serif", depending on the context or active configuration.</p> + +<ul> + <li><strong>alias</strong> (required) defines the alias name that should be + matched to the font-family requested.</li> + <li>default-family (required) indicates the name of the font-family that + should be substituted for the alias if no matching child + <alias-configuration> element is found.</li> +</ul> + +<h3><a name="alias-configuration"><alias-configuration> element</a></h3> +<p>The <alias-configuration> element is an optional child to the +<font-family-alias> element, and allows an alias name to point to +different font-family elements depending upon some configuration name. +The configuration name is application-dependent. +Some applications may choose not to use them at all, and others may have +a complex scheme for determining which configuration to use in a given +circumstance. +A typical use is to distinguish between fonts available for print applications, +like PDF and PostScript, from those available for viewing documents on the +screen, such as AWT applications.</p> + +<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> +</body> +</html> Deleted: trunk/axsl/doc/web/font-r/encoding.html =================================================================== --- trunk/axsl/doc/web/font/encoding.html 2006-05-05 16:51:49 UTC (rev 508) +++ trunk/axsl/doc/web/font-r/encoding.html 2006-05-05 17:48:06 UTC (rev 511) @@ -1,229 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> - -<head> - <title>axslFont: Font Encoding</title> - <meta name="content-revised" - content="$Date$"/> - <!--#include virtual="/00-rsrc/include/standard-head.html" --> -</head> - -<body> - -<!--#include virtual="/00-rsrc/include/leftmenu.html" --> - -<h1>axslFont: Font Encoding</h1> -<h2>Contents</h2> -<ul> - <li><a href="#encoding-select">Encoding Selection</a></li> - <li><a href="#encoding-custom">Custom Encodings</a></li> - <li><a href="#gl-select">Glyph Lists Selection</a></li> - <li><a href="#gl-custom">Custom Glyph Lists</a></li> -</ul> - -<h2><a name="encoding-select">Encoding Selection</a></h2> -<p>Type 1 fonts can address a maximum of about 224 glyphs at one time (256 is -the maximum that can be addressed with 1 byte, and the first 32 are considered -control codes). -However, a Type 1 font can contain many more glyphs than that. -This is possible because a different set of glyphs can be addressed by -selecting different <em>encoding vectors</em>. -When using a Type 1 font, you may select which encoding vector should -be used by specifying the "encoding" attribute on a font-description element -in the font-configuration.</p> - -<p>Support of various encoding schemes is application dependent. However, the -following named encoding vectors are hard-coded, well-documented encoding -schemes that many applications will make available:</p> - - <table> - <thead> - <tr> - <th>Encoding Vector Name</th> - <th>Predefined Encoding For</th> - </tr> - </thead> - <tbody> - <tr> - <td>AdobeStandardEncoding (can also be referenced as - "StandardEncoding"). Closely matches ISO 8859-1.</td> - <td>PostScript</td> - </tr> - <tr> - <td>ISOLatin1Encoding</td> - <td>PostScript</td> - </tr> - <tr> - <td>WinAnsiEncoding (matches Microsoft Windows code page 1252).</td> - <td>PDF</td> - </tr> - <tr> - <td>SymbolEncoding</td> - <td>n/a</td> - </tr> - <tr> - <td>ZapfDingbatsEncoding</td> - <td>n/a</td> - </tr> - <tr> - <td>CEEncoding (matches Microsoft Windows code page 1250).</td> - <td>n/a</td> - </tr> - <tr> - <td>MacRomanEncoding</td> - <td>PDF</td> - </tr> - <tr> - <td>PDFDocEncoding</td> - <td>n/a</td> - </tr> - <tr> - <td>MacExpertEncoding</td> - <td>PDF</td> - </tr> - <tr> - <td>ExpertEncoding</td> - <td>n/a</td> - </tr> - <tr> - <td>ExpertSubsetEncoding</td> - <td>n/a</td> - </tr> - <tr> - <td>MacStandardEncoding (this is the "Standard Macintosh Ordering" that - is used within some TrueType fonts).</td> - </tr> - </tbody> - </table> - -<p>Note that selection of an encoding that is not predefined for the output -medium will result in the need to write that encoding into the output -document. -The only drawbacks to this are the (probably unnoticable) performance penalty -for writing the encoding into the output, and the somewhat larger output -itself.</p> - -<h2><a name="encoding-custom">Custom Encodings</a></h2> -<p>Custom encodings can also be defined in the font-configuration file. -Once that is done, they are available to be used in font-description entries -just like the predefined encodings.</p> - -<p>To create a custom encoding, first place the data defining the encoding -into a text file. -(The files to create the predefined encodings can be cut-and-pasted -from PostScript and PDF documentation). -The format of the file containing a custom encoding is best documented by -providing an example. -Here is an example from the Latin encodings for PostScript:</p> - -<pre># -- Encoding -- -# Character Name STD ISO CE -# -------------- --- --- --- - -A 101 101 101 -AE 341 306 - -Aacute - 301 301</pre> - -<p>Each line of the file is a record. -Each record consists of two or more fields delimited by whitespace. -The first field is the glyph name. -All additional fields are glyph indexes to which the glyph name points within -specific encoding. -Multiple encodings can be described within a single encoding file by adding -more than two columns. -The illustration above includes encoding information for "StandardEncoding", -"ISOLatin1Encoding", and "CEEncoding", which share enough common characters -to make it useful to place them in the same file. -Blank lines and line starting with an octothorp (#) are ignored. -When processing a specific column of the file, a hyphen in that column serves -to indicate that the line should be ignored for that encoding.</p> - -<p>The glyph index value may be specified using any radix. -The examples above are in octal (base- or radix-8). -Encoding schemes are also sometimes expressed in hexadecimal (radix-16) or -decimal (radix-10). -When creating a custom encoding in the font-configuration, you must specify -the radix that should be used for parsing.</p> - -<p>After creating the encoding file, make it available to your application -by creating an encoding element in the font-configuration file:</p> - -<pre><encoding - name="my-encoding" - glyph-lists="my-glyph-list another-glyph-list"/ - file="file://C:/some/path/encoding.txt" - column-to-parse="2" - radix="8"></pre> - - <ul> - <li><strong>name</strong> indicates the name by which this encoding - should be referred.</li> - <li><strong>glyph-lists</strong> is an ordered, space-delimited list of - glyph lists which should be consulted at parse-time to convert glyph - names into Unicode code points. Glyph lists earlier in the list will be - checked before those listed later in the list. - See the <a href="#gl-select">Glyph List</a> documentation for more - details. - </li> - <li><strong>file</strong> indicates the URL of the file which should be - parsed to obtain the encoding.</li> - <li><strong>column-to-parse</strong> indicates which column of the file - should be used to obtain values for this encoding. - Columns are numbered from the first column with an encoding, which is - actually the second column in the file. - The first column of the file contains the glyph name. - The second column is numbered "1" for purposes of specifing a - column-to-parse. - </li> - <li><strong>radix</strong> indicates the numbering system used to specify - the glyph indexes for the encoding being parsed. If the indexes are - decimal, use radix 10; if octal, use radix 8. If hexadecimal, use radix - 16.</li> - </ul> - -<h2><a name="gl-select">Glyph List Selection</a></h2> -<p>In order to create an EncodingVector instance, an application needs to -have some way of mapping a glyph name to a Unicode code point. -A "glyph list" is used to define this mapping. -Adobe provides two standard glyph lists, both of which are readily available, -and possibly hard-coded into your application. -If so, they are available by reference to their names: "AGL" (the Adobe Glyph -List), and "ZapfDingbats". -Unless the font you are using has a very unusual character set, these should be -sufficient for creation of custom encodings.</p> - -<h2><a name="gl-custom">Custom Glyph Lists</a></h2> -<p>If a custom glyph list is needed (to handle an unusual character set), first -create the list defining the glyph list. -The format of this file is best documented by providing an excerpt from the -Adobe Glyph List:</p> -<pre>B;0042 -Bcircle;24B7</pre> - -<p>Each line of the file is a record. -Each record consists of two fields delimited by a semicolon. -The first field is the glyph name. -The second is the hexadecimal value of the Unicode code point to which that -glyph name is pointed. -Blank lines and line starting with an octothorp (#) are ignored.</p> - -<p>The custom glyph list is then made available to your application by creating -a glyph-list element in the font-configuration file:</p> -<pre><glyph-list - name="my-glyph-list" - file="file://C:/some/path/my-glyph-list.txt"/></pre> - - <ul> - <li><strong>name</strong> indicates the name by which this glyph list - should be referred.</li> - <li><strong>file</strong> indicates the URL of the file which should be - parsed to obtain the custom glyph list.</li> - </ul> - -<!--#include virtual="/00-rsrc/include/leftmenu-end.html" --> -</body> -</html> Copied: trunk/axsl/doc/web/font-r/encoding.html (from rev 510, trunk/axsl/doc/web/font/encoding.html) =================================================================== --- trunk/axsl/doc/web/font-r/encoding.html (rev 0) +++ trunk/axsl/doc/web/font-r/encoding.html 2006-05-05 17:48:06 UTC (rev 511) @@ -0,0 +1,229 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> + +<head> + <title>axslFont: Font Encoding</title> + <meta name="content-revised" + content="$Date$"/> + <!--#include virtual="/00-rsrc/include/standard-head.html" --> +</head> + +<body> + +<!--#include virtual="/00-rsrc/include/leftmenu.html" --> + +<h1>axslFont: Font Encoding</h1> +<h2>Contents</h2> +<ul> + <li><a href="#encoding-select">Encoding Selection</a></li> + <li><a href="#encoding-custom">Custom Encodings</a></li> + <li><a href="#gl-select">Glyph Lists Selection</a></li> + <li><a href="#gl-custom">Custom Glyph Lists</a></li> +</ul> + +<h2><a name="encoding-select">Encoding Selection</a></h2> +<p>Type 1 fonts can address a maximum of about 224 glyphs at one time (256 is +the maximum that can be addressed with 1 byte, and the first 32 are considered +control codes). +However, a Type 1 font can contain many more glyphs than that. +This is possible because a different set of glyphs can be addressed by +selecting different <em>encoding vectors</em>. +When using a Type 1 font, you may select which encoding vector should +be used by specifying the "encoding" attribute on a font-description element +in the font-configuration.</p> + +<p>Support of various encoding schemes is application dependent. However, the +following named encoding vectors are hard-coded, well-documented encoding +schemes that many applications will make available:</p> + + <table> + <thead> + <tr> + <th>Encoding Vector Name</th> + <th>Predefined Encoding For</th> + </tr> + </thead> + <tbody> + <tr> + <td>AdobeStandardEncoding (can also be referenced as + "StandardEncoding"). Closely matches ISO 8859-1.</td> + <td>PostScript</td> + </tr> + <tr> + <td>ISOLatin1Encoding</td> + <td>PostScript</td> + </tr> + <tr> + <td>WinAnsiEncoding (matches Microsoft Windows code page 1252).</td> + <td>PDF</td> + </tr> + <tr> + <td>SymbolEncoding</td> + <td>n/a</td> + </tr> + <tr> + <td>ZapfDingbatsEncoding</td> + <td>n/a</td> + </tr> + <tr> + <td>CEEncoding (matc... [truncated message content] |
