|
From: Victor M. <vi...@ou...> - 2005-09-14 05:55:07
|
I just completed the addition of the FontUse interface, which is actually Font being split into two pieces. IOW the methods in FontUse were all formerly in Font, with the exception of the getFont() method, which ties the two together. There is intended to be a one-to-many relationship between Font and FontUse. FontUse is a Font used in a specific way. It corresponds to the font-description element in the font-configuration. The most important aspect of this is that the Font is separated from its encoding, so that it can be configured to be encoded in more than way. However, it also allows a font to be configured in more than one font-family for other reasons as well, and provides greater flexibility with regard to simulating font characteristics like small-caps, oblique, and the font-stretch characteristics. Implementations should in most cases use the FontUse in places where the Font interface was used before. The Font implementation can be obtained from FontUse through the getFont() method. Future changes will probably have the FontServer returning Collections of both Font instances used and FontUse instances used. Victor Mote |