Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major 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.

        Activity

        Hide
        Patrick Corless added a comment -

        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.

        Show
        Patrick Corless added a comment - 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.
        Hide
        Patrick Corless added a comment -

        Customer has reported fix has resolved their font substitution issue.

        Show
        Patrick Corless added a comment - Customer has reported fix has resolved their font substitution issue.
        Hide
        Patrick Corless added a comment -

        A customer has reported a regression. Font substitution no longer woks of the font properties file cache is disabled. The issue is related to a file lock check being done which is causing the font scan to not execute.

        Show
        Patrick Corless added a comment - A customer has reported a regression. Font substitution no longer woks of the font properties file cache is disabled. The issue is related to a file lock check being done which is causing the font scan to not execute.
        Hide
        Patrick Corless added a comment -

        Verified default font paths are no scanned regardless of a user disabling the file cache.

        Show
        Patrick Corless added a comment - Verified default font paths are no scanned regardless of a user disabling the file cache.
        Hide
        Patrick Corless added a comment -

        Marking as closed

        Show
        Patrick Corless added a comment - Marking as closed

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Patrick Corless
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: