Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.1.2
-
Fix Version/s: 6.0
-
Component/s: Font Engine
-
Labels:None
-
Environment:PRO
Description
A customer has asked us to enhance the FontManager so that they can get more consistent results in font substitution font pairing from system to system.
The font manager currently has a few extension points but it still tries to read all system fonts before reading the customer paths. When the properties object is create ordering is lost which is also a potential problem.
The font manager currently has a few extension points but it still tries to read all system fonts before reading the customer paths. When the properties object is create ordering is lost which is also a potential problem.
I've done quite a bit of work to try and clean thing up in the FontPropertiesManager as well as the FontManager. The FontManager API has been kept intact with the addition of a few new methods that allow the skipping of the default system font search. The FontPropertiesManager API has changed to make it more flexible. Core functionality hasn't changed but there is a new constructor that avoid the auto scan feature.