Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
F
fontconfig
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 153
    • Issues 153
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 18
    • Merge Requests 18
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fontconfig
  • fontconfig
  • Issues
  • #35

Closed
Open
Opened Mar 30, 2010 by Bugzilla Migration User@bugzilla-migration

Side effect of the binding inheritance by binding="same"

Submitted by Behdad Esfahbod

Assigned to fon..@..op.org

Link to original bug (#27377)

Description

Akira hints at that on the fedora fonts list in message sent on 2010-03-19. He writes:

I'm wondering if we should recommend the use of /binding="same"/ in the locale-specific overrides rule of the template because it introduces the unexpected result depending on the queries pattern.

Here is the example of it:

$ rpm -qa *-fonts | grep mono dejavu-sans-mono-fonts-2.30-2.fc12.noarch liberation-mono-fonts-1.05.2.20091019-5.fc13.noarch $ rpm -q vlgothic-fonts vlgothic-fonts-20100126-2.fc13.noarch

$ fc-match monospace:lang=ja VL-Gothic-Regular.ttf: "VL Gothic" "regular" $ fc-match monospace:lang=ja-jp VL-Gothic-Regular.ttf: "VL Gothic" "regular" $ fc-match monospace:lang=en VL-Gothic-Regular.ttf: "VL Gothic" "regular" $ fc-match monospace:lang=en-us VL-Gothic-Regular.ttf: "VL Gothic" "regular"

Also same result for serif, but not for sans-serif, since apparently fontconfig always deals with it as "sans" for the initial query pattern, translating it to "sans-serif". and all of rules are targetting "sans-serif" but not "sans". so it's luckily working.

Version: 2.7

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: fontconfig/fontconfig#35