Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • F fontconfig
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 181
    • Issues 181
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fontconfig
  • fontconfig
  • Issues
  • #255
Closed
Open
Issue created Aug 23, 2020 by Matthias Clasen@matthiasc

Consider caching charset subset relation

I have code here that computes the FcCharSetIsSubset relations for all fonts in the current configuration, saves that data to a file, and loads it again:

https://gitlab.gnome.org/GNOME/pango/-/merge_requests/229

That makes coverage trimming much cheaper, since most of the charset comparisons can be avoided. The code probably belongs into fontconfig, but I don't have the energy to rewrite it and figure out how to integrate it into fc-cache.

It is slighty tricky, since it is global information, not per-directory.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking