[aXSL-commit] SF.net SVN: axsl:[2990] trunk/axsl/axsl-font/src/main /java/org/axsl/font/package-info.java

[<vic...@us...>]

Revision: 2990
          http://sourceforge.net/p/axsl/code/2990
Author:   victormote
Date:     2026-03-09 00:13:11 +0000 (Mon, 09 Mar 2026)
Log Message:
-----------
Documentation changes only.

Modified Paths:
--------------
    trunk/axsl/axsl-font/src/main/java/org/axsl/font/package-info.java

Modified: trunk/axsl/axsl-font/src/main/java/org/axsl/font/package-info.java
===================================================================
--- trunk/axsl/axsl-font/src/main/java/org/axsl/font/package-info.java	2026-03-08 23:34:35 UTC (rev 2989)
+++ trunk/axsl/axsl-font/src/main/java/org/axsl/font/package-info.java	2026-03-09 00:13:11 UTC (rev 2990)
@@ -23,13 +23,33 @@
 
 /**
  * <p>Interfaces allowing client applications to register, track, and use fonts in a vendor-neutral way.
- * An aXSL client application writes its programs using the aXSL interfaces.
- * It then obtains a concrete vendor-specific implementation of FontServer, and concrete vendor-specific implementations
- * of FontConsumer for each document or other user of font information that it processes.
- * From that point, the client application can request FontUse instances from the appropriate FontConsumer.
- * FontUse and Font instances then provide the client application with various font-related services.
- * The only contact a client application must have with a concrete implementation is the provision of a concrete
- * FontServer and FontConsumer instance(s).</p>
+ * An aXSL client application writes its programs using the aXSL interfaces, shielding it from the details of the
+ * implementation, and allowing implementations to be swapped in and out more readily.</p>
+ *
+ * <p>Much of the design of aXSL Font is driven by the need to handle multiple encodings for one font.
+ * This somewhat an artifact of pre-Unicode days, and it is possible that the extra complexity that is caused by this
+ * design feature can be retired at some point in the future.
+ * Adobe announced in 2021 that it will no longer support Type 1 fonts starting in 2023:</p>
+ *
+ * <p>To use aXSL Font:</p>
+ * <ol>
+ *   <li>Obtains a concrete vendor-specific implementation of {@link FontServer}.</li>
+ *   <li>Use the {@link FontServer} to create a {@link FontConsumer}, which is the document-level object that keeps
+ *   track of which fonts have been used in the document.
+ *   <li>As fonts are needed by the client application, it obtains them from methods in {@link FontConsumer}, which
+ *   returns them in the form of a {@link ConsumerFont}.</li>
+ *   <li>The {@link ConsumerFont} is a wrapper around a {@link Font} instance.
+ *   It creates and manages instances of {@link FontUse}, which is a wrapper around the {@link Font} and an
+ *   {@link org.axsl.ps.Encoding}.</li>
+ *   <li>The {@link FontUse} instance converts Unicode code points to font glyph indexes that can be written into an
+ *   output document.
+ *   It also keeps track of which glyphs have been used, for purposes of creating subsets.</li>
+ * </ol>
+ *
+ * @see <a href="https://helpx.adobe.com/fonts/kb/postscript-type-1-fonts-end-of-support.html">PostScript Type 1 fonts
+ * end of support</a>
+ * @see <a href="http://www.foray.org/module/font/index.html">FOray Font</a> for a reference implementation of aXSL
+ * Font.
  */
 
 package org.axsl.font;

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