{
    "mode": "man",
    "parameter": "fonts-conf",
    "section": "5",
    "url": "https://www.chedong.com/phpMan.php/man/fonts-conf/5/json",
    "generated": "2026-06-15T23:00:04Z",
    "synopsis": "/etc/fonts/fonts.conf\n/etc/fonts/fonts.dtd\n/etc/fonts/conf.d\n$XDGCONFIGHOME/fontconfig/conf.d\n$XDGCONFIGHOME/fontconfig/fonts.conf\n~/.fonts.conf.d\n~/.fonts.conf",
    "sections": {
        "NAME": {
            "content": "fonts.conf - Font configuration files\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "/etc/fonts/fonts.conf\n/etc/fonts/fonts.dtd\n/etc/fonts/conf.d\n$XDGCONFIGHOME/fontconfig/conf.d\n$XDGCONFIGHOME/fontconfig/fonts.conf\n~/.fonts.conf.d\n~/.fonts.conf\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Fontconfig is a library designed to provide system-wide font configuration, customization and\napplication access.\n",
            "subsections": []
        },
        "FUNCTIONAL OVERVIEW": {
            "content": "Fontconfig contains two essential modules, the configuration module which builds an  internal\nconfiguration  from XML files and the matching module which accepts font patterns and returns\nthe nearest matching font.\n\nFONT CONFIGURATION\nThe configuration module consists of the FcConfig datatype, libexpat and FcConfigParse  which\nwalks  over  an XML tree and amends a configuration with data found within.  From an external\nperspective, configuration of the library consists of generating a valid XML tree and feeding\nthat  to  FcConfigParse.   The only other mechanism provided to applications for changing the\nrunning configuration is to add fonts and directories to  the  list  of  application-provided\nfont files.\n\nThe  intent  is to make font configurations relatively static, and shared by as many applica‐\ntions as possible.  It is hoped that this will lead to more stable font selection when  pass‐\ning names from one application to another.  XML was chosen as a configuration file format be‐\ncause it provides a format which is easy for external agents to edit while retaining the cor‐\nrect structure and syntax.\n\nFont  configuration  is  separate  from  font  matching; applications needing to do their own\nmatching can access the available fonts from the library and perform private  matching.   The\nintent  is  to  permit applications to pick and choose appropriate functionality from the li‐\nbrary instead of forcing them to choose between this  library  and  a  private  configuration\nmechanism.   The  hope  is that this will ensure that configuration of fonts for all applica‐\ntions can be centralized in one place.  Centralizing font  configuration  will  simplify  and\nregularize font installation and customization.\n\nFONT PROPERTIES\nWhile font patterns may contain essentially any properties, there are some well known proper‐\nties with associated types.  Fontconfig uses some of these properties for font  matching  and\nfont completion.  Others are provided as a convenience for the applications' rendering mecha‐\nnism.\n\nProperty        Type    Description\n--------------------------------------------------------------\nfamily          String  Font family names\nfamilylang      String  Languages corresponding to each family\nstyle           String  Font style. Overrides weight and slant\nstylelang       String  Languages corresponding to each style\nfullname        String  Font full names (often includes style)\nfullnamelang    String  Languages corresponding to each fullname\nslant           Int     Italic, oblique or roman\nweight          Int     Light, medium, demibold, bold or black\nsize            Double  Point size\nwidth           Int     Condensed, normal or expanded\naspect          Double  Stretches glyphs horizontally before hinting\npixelsize       Double  Pixel size\nspacing         Int     Proportional, dual-width, monospace or charcell\nfoundry         String  Font foundry name\nantialias       Bool    Whether glyphs can be antialiased\nhinting         Bool    Whether the rasterizer should use hinting\nhintstyle       Int     Automatic hinting style\nverticallayout  Bool    Use vertical layout\nautohint        Bool    Use autohinter instead of normal hinter\nglobaladvance   Bool    Use font global advance data (deprecated)\nfile            String  The filename holding the font\nindex           Int     The index of the font within the file\nftface          FTFace Use the specified FreeType face object\nrasterizer      String  Which rasterizer is in use (deprecated)\noutline         Bool    Whether the glyphs are outlines\nscalable        Bool    Whether glyphs can be scaled\ncolor           Bool    Whether any glyphs have color\nscale           Double  Scale factor for point->pixel conversions (deprecated)\ndpi             Double  Target dots per inch\nrgba            Int     unknown, rgb, bgr, vrgb, vbgr,\nnone - subpixel geometry\nlcdfilter       Int     Type of LCD filter\nminspace        Bool    Eliminate leading from line spacing\ncharset         CharSet Unicode chars encoded by the font\nlang            String  List of RFC-3066-style languages this\nfont supports\nfontversion     Int     Version number of the font\ncapability      String  List of layout capabilities in the font\nfontformat      String  String name of the font format\nembolden        Bool    Rasterizer should synthetically embolden the font\nembeddedbitmap  Bool    Use the embedded bitmap instead of the outline\ndecorative      Bool    Whether the style is a decorative variant\nfontfeatures    String  List of the feature tags in OpenType to be enabled\nnamelang        String  Language name to be used for the default value of\nfamilylang, stylelang, and fullnamelang\nprgname         String  String  Name of the running program\npostscriptname  String  Font family name in PostScript\n\n\nFONT MATCHING\nFontconfig performs matching by measuring the distance from a provided pattern to all of  the\navailable  fonts  in the system.  The closest matching font is selected.  This ensures that a\nfont will always be returned, but doesn't ensure that it is anything like the requested  pat‐\ntern.\n\nFont  matching starts with an application constructed pattern.  The desired attributes of the\nresulting font are collected together in a pattern.  Each property of the pattern can contain\none  or more values; these are listed in priority order; matches earlier in the list are con‐\nsidered \"closer\" than matches later in the list.\n\nThe initial pattern is modified by applying the list of editing instructions specific to pat‐\nterns found in the configuration; each consists of a match predicate and a set of editing op‐\nerations.  They are executed in the order they appeared in  the  configuration.   Each  match\ncauses the associated sequence of editing operations to be applied.\n\nAfter  the  pattern  has  been  edited,  a sequence of default substitutions are performed to\ncanonicalize the set of available properties; this avoids the need for the  lower  layers  to\nconstantly provide default values for various font properties during rendering.\n\nThe canonical font pattern is finally matched against all available fonts.  The distance from\nthe pattern to the font is measured for each of several properties: foundry, charset, family,\nlang, spacing, pixelsize, style, slant, weight, antialias, rasterizer and outline.  This list\nis in priority order -- results of comparing earlier elements of this list weigh more heavily\nthan later elements.\n\nThere  is one special case to this rule; family names are split into two bindings; strong and\nweak.  Strong family names are given greater precedence in the match than lang elements while\nweak  family  names are given lower precedence than lang elements.  This permits the document\nlanguage to drive font selection when any document specified font is unavailable.\n\nThe pattern representing that font is augmented to include any properties found in  the  pat‐\ntern  but  not  found  in the font itself; this permits the application to pass rendering in‐\nstructions or any other data through the matching system.  Finally, the list of  editing  in‐\nstructions  specific  to  fonts  found in the configuration are applied to the pattern.  This\nmodified pattern is returned to the application.\n\nThe return value contains sufficient information to locate and rasterize the font,  including\nthe file name, pixel size and other rendering data.  As none of the information involved per‐\ntains to the FreeType library, applications are free to use any rasterization engine or  even\nto take the identified font file and access it directly.\n\nThe  match/edit  sequences in the configuration are performed in two passes because there are\nessentially two different operations necessary -- the first is to modify how  fonts  are  se‐\nlected;  aliasing families and adding suitable defaults.  The second is to modify how the se‐\nlected fonts are rasterized.  Those must apply to the selected font, not the original pattern\nas false matches will often occur.\n\nFONT NAMES\nFontconfig  provides  a  textual representation for patterns that the library can both accept\nand generate.  The representation is in three parts, first a list of family names,  second  a\nlist of point sizes and finally a list of additional properties:\n\n<families>-<point sizes>:<name1>=<values1>:<name2>=<values2>...\n\n\nValues  in  a  list  are  separated with commas.  The name needn't include either families or\npoint sizes; they can be elided.  In addition, there are symbolic constants  that  simultane‐\nously indicate both a name and a value.  Here are some examples:\n\nName                            Meaning\n----------------------------------------------------------\nTimes-12                        12 point Times Roman\nTimes-12:bold                   12 point Times Bold\nCourier:italic                  Courier Italic in the default size\nMonospace:matrix=1 .1 0 1       The users preferred monospace font\nwith artificial obliquing\n\n\nThe  '\\',  '-', ':' and ',' characters in family names must be preceded by a '\\' character to\navoid having them misinterpreted. Similarly, values containing '\\', '=',  '',  ':'  and  ','\nmust  also  have them preceded by a '\\' character. The '\\' characters are stripped out of the\nfamily name and values as the font name is read.\n",
            "subsections": []
        },
        "DEBUGGING APPLICATIONS": {
            "content": "To help diagnose font and applications problems, fontconfig is built with a large  amount  of\ninternal  debugging left enabled. It is controlled by means of the FCDEBUG environment vari‐\nable. The value of this variable is interpreted as a number, and each bit within  that  value\ncontrols different debugging messages.\n\nName         Value    Meaning\n---------------------------------------------------------\nMATCH            1    Brief information about font matching\nMATCHV           2    Extensive font matching information\nEDIT             4    Monitor match/test/edit execution\nFONTSET          8    Track loading of font information at startup\nCACHE           16    Watch cache files being written\nCACHEV          32    Extensive cache file writing information\nPARSE           64    (no longer in use)\nSCAN           128    Watch font files being scanned to build caches\nSCANV          256    Verbose font file scanning information\nMEMORY         512    Monitor fontconfig memory usage\nCONFIG        1024    Monitor which config files are loaded\nLANGSET       2048    Dump char sets used to construct lang values\nMATCH2        4096    Display font-matching transformation in patterns\n\n\nAdd the value of the desired debug levels together and assign that (in base 10) to the FCDE‐\nBUG environment variable before running the application. Output from these statements is sent\nto stdout.\n",
            "subsections": []
        },
        "LANG TAGS": {
            "content": "Each font in the database contains a list of languages it supports.  This is computed by com‐\nparing the Unicode coverage of the font with the orthography of each language.  Languages are\ntagged using an RFC-3066 compatible naming and occur in two parts -- the ISO 639 language tag\nfollowed a hyphen and then by the ISO 3166 country code.  The hyphen and country code may  be\nelided.\n\nFontconfig  has orthographies for several languages built into the library.  No provision has\nbeen made for adding new ones aside from rebuilding the library.  It currently  supports  122\nof  the 139 languages named in ISO 639-1, 141 of the languages with two-letter codes from ISO\n639-2 and another 30 languages with only three-letter codes.  Languages  with  both  two  and\nthree letter codes are provided with only the two letter code.\n\nFor  languages used in multiple territories with radically different character sets, fontcon‐\nfig includes  per-territory  orthographies.   This  includes  Azerbaijani,  Kurdish,  Pashto,\nTigrinya and Chinese.\n",
            "subsections": []
        },
        "CONFIGURATION FILE FORMAT": {
            "content": "Configuration  files for fontconfig are stored in XML format; this format makes external con‐\nfiguration tools easier to write and ensures that they will  generate  syntactically  correct\nconfiguration files.  As XML files are plain text, they can also be manipulated by the expert\nuser using a text editor.\n\nThe fontconfig document type definition resides in the external entity \"fonts.dtd\";  this  is\nnormally stored in the default font configuration directory (/etc/fonts).  Each configuration\nfile should contain the following structure:\n\n<?xml version=\"1.0\"?>\n<!DOCTYPE fontconfig SYSTEM \"fonts.dtd\">\n<fontconfig>\n...\n</fontconfig>\n\n",
            "subsections": [
                {
                    "name": "<FONTCONFIG>",
                    "content": "This is the top level element for a font configuration and  can  contain  <dir>,  <cachedir>,\n<include>, <match> and <alias> elements in any order.\n"
                },
                {
                    "name": "<DIR PREFIX= DEFAULT\">\"",
                    "content": "This element contains a directory name which will be scanned for font files to include in the\nset of available fonts. If 'prefix' is set to \"xdg\", the value in the XDGDATAHOME  environ‐\nment  variable  will be added as the path prefix. please see XDG Base Directory Specification\nfor more details.\n"
                },
                {
                    "name": "<CACHEDIR PREFIX= DEFAULT\">\"",
                    "content": "This element contains a directory name that is supposed to be stored or  read  the  cache  of\nfont  information.   If multiple elements are specified in the configuration file, the direc‐\ntory that can be accessed first in the list will be used to store the  cache  files.   If  it\nstarts with '~', it refers to a directory in the users home directory.  If 'prefix' is set to\n\"xdg\", the value in the XDGCACHEHOME environment variable will be added as the path prefix.\nplease  see  XDG  Base  Directory  Specification  for more details.  The default directory is\n``$XDGCACHEHOME/fontconfig'' and it contains the cache files named  ``<hash  value>-<archi‐\ntecture>.cache-<version>'', where <version> is the fontconfig cache file version number (cur‐\nrently 7).\n\n<INCLUDE IGNOREMISSING= NO\" PREFIX=\"DEFAULT\">\"\nThis element contains the name of an additional configuration file or directory.  If a direc‐\ntory,  every  file  within  that directory starting with an ASCII digit (U+0030 - U+0039) and\nending with the string ``.conf'' will be processed in sorted order.  When the XML datatype is\ntraversed  by  FcConfigParse,  the contents of the file(s) will also be incorporated into the\nconfiguration by passing the filename(s) to FcConfigLoadAndParse.  If 'ignoremissing' is set\nto \"yes\" instead of the default \"no\", a missing file or directory will elicit no warning mes‐\nsage from the library.  If 'prefix' is set to \"xdg\", the value in the  XDGCONFIGHOME  envi‐\nronment  variable  will be added as the path prefix. please see XDG Base Directory Specifica‐\ntion for more details.\n"
                },
                {
                    "name": "<CONFIG>",
                    "content": "This element provides a place to consolidate additional configuration information.   <config>\ncan contain <blank> and <rescan> elements in any order.\n"
                },
                {
                    "name": "<BLANK>",
                    "content": "Fonts  often  include \"broken\" glyphs which appear in the encoding but are drawn as blanks on\nthe screen.  Within the <blank> element, place each Unicode characters which is  supposed  to\nbe  blank  in an <int> element.  Characters outside of this set which are drawn as blank will\nbe elided from the set of characters supported by the font.\n"
                },
                {
                    "name": "<RESCAN>",
                    "content": "The <rescan> element holds an <int> element which indicates the default interval between  au‐\ntomatic  checks for font configuration changes.  Fontconfig will validate all of the configu‐\nration files and directories and automatically rebuild the internal datastructures when  this\ninterval passes.\n"
                },
                {
                    "name": "<SELECTFONT>",
                    "content": "This  element  is  used  to  black/white list fonts from being listed or matched against.  It\nholds acceptfont and rejectfont elements.\n"
                },
                {
                    "name": "<ACCEPTFONT>",
                    "content": "Fonts matched by an acceptfont element are \"whitelisted\"; such fonts are explicitly  included\nin the set of fonts used to resolve list and match requests; including them in this list pro‐\ntects them from being \"blacklisted\" by a rejectfont  element.   Acceptfont  elements  include\nglob and pattern elements which are used to match fonts.\n"
                },
                {
                    "name": "<REJECTFONT>",
                    "content": "Fonts  matched  by  an rejectfont element are \"blacklisted\"; such fonts are excluded from the\nset of fonts used to resolve list and match requests as if they didn't exist in  the  system.\nRejectfont elements include glob and pattern elements which are used to match fonts.\n"
                },
                {
                    "name": "<GLOB>",
                    "content": "Glob  elements  hold  shell-style  filename matching patterns (including ? and *) which match\nfonts based on their complete pathnames.  This can be used to exclude a  set  of  directories\n(/usr/share/fonts/uglyfont*), or particular font file types (*.pcf.gz), but the latter mecha‐\nnism relies rather heavily on filenaming conventions which can't be relied upon.   Note  that\nglobs only apply to directories, not to individual fonts.\n"
                },
                {
                    "name": "<PATTERN>",
                    "content": "Pattern  elements perform list-style matching on incoming fonts; that is, they hold a list of\nelements and associated values.  If all of those elements have a  matching  value,  then  the\npattern  matches  the font.  This can be used to select fonts based on attributes of the font\n(scalable, bold, etc), which is a more reliable mechanism than using file  extensions.   Pat‐\ntern elements include patelt elements.\n"
                },
                {
                    "name": "<PATELT NAME= PROPERTY\">\"",
                    "content": "Patelt  elements  hold  a single pattern element and list of values.  They must have a 'name'\nattribute which indicates the pattern element name.  Patelt  elements  include  int,  double,\nstring, matrix, bool, charset and const elements.\n"
                },
                {
                    "name": "<MATCH TARGET= PATTERN\">\"",
                    "content": "This  element  holds  first  a  (possibly empty) list of <test> elements and then a (possibly\nempty) list of <edit> elements.  Patterns which match all of the tests are subjected  to  all\nthe  edits.  If 'target' is set to \"font\" instead of the default \"pattern\", then this element\napplies to the font name resulting from a match rather than a font pattern to be matched.  If\n'target'  is  set  to \"scan\", then this element applies when the font is scanned to build the\nfontconfig database.\n"
                },
                {
                    "name": "<TEST QUAL= ANY\" NAME=\"PROPERTY\" TARGET=\"DEFAULT\" COMPARE=\"EQ\">\"",
                    "content": "This element contains a single value which is compared with the  target  ('pattern',  'font',\n'scan'  or  'default') property \"property\" (substitute any of the property names seen above).\n'compare' can be one of \"eq\", \"noteq\", \"less\", \"lesseq\", \"more\", \"moreeq\",  \"contains\"  or\n\"notcontains\".  'qual' may either be the default, \"any\", in which case the match succeeds if\nany value associated with the property matches the test value, or \"all\", in which case all of\nthe  values  associated with the property must match the test value.  'ignore-blanks' takes a\nboolean value. if 'ignore-blanks' is set \"true\", any blanks in the string will be ignored  on\nits  comparison. this takes effects only when compare=\"eq\" or compare=\"noteq\".  When used in\na <match target=\"font\"> element, the target= attribute in the <test> element selects  between\nmatching  the  original  pattern  or  the font.  \"default\" selects whichever target the outer\n<match> element has selected.\n"
                },
                {
                    "name": "<EDIT NAME= PROPERTY\" MODE=\"ASSIGN\" BINDING=\"WEAK\">\"",
                    "content": "This element contains a list of expression elements (any of the value or operator  elements).\nThe  expression  elements  are evaluated at run-time and modify the property \"property\".  The\nmodification depends on whether \"property\" was matched by one of the associated  <test>  ele‐\nments,  if so, the modification may affect the first matched value.  Any values inserted into\nthe property are given the indicated binding (\"strong\", \"weak\" or \"same\") with \"same\" binding\nusing the value from the matched pattern element.  'mode' is one of:\n\nMode                    With Match              Without Match\n---------------------------------------------------------------------\n\"assign\"                Replace matching value  Replace all values\n\"assignreplace\"        Replace all values      Replace all values\n\"prepend\"               Insert before matching  Insert at head of list\n\"prependfirst\"         Insert at head of list  Insert at head of list\n\"append\"                Append after matching   Append at end of list\n\"appendlast\"           Append at end of list   Append at end of list\n\"delete\"                Delete matching value   Delete all values\n\"deleteall\"            Delete all values       Delete all values\n\n"
                },
                {
                    "name": "<INT>, <DOUBLE>, <STRING>, <BOOL>",
                    "content": "These  elements  hold a single value of the indicated type.  <bool> elements hold either true\nor false.  An important limitation exists in the parsing of floating point numbers  --  font‐\nconfig  requires that the mantissa start with a digit, not a decimal point, so insert a lead‐\ning zero for purely fractional values (e.g. use 0.5 instead of .5 and -0.5 instead of -.5).\n"
                },
                {
                    "name": "<MATRIX>",
                    "content": "This element holds four numerical expressions of an affine transformation.  At their simplest\nthese will be four <double> elements but they can also be more involved expressions.\n"
                },
                {
                    "name": "<RANGE>",
                    "content": "This element holds the two <int> elements of a range representation.\n"
                },
                {
                    "name": "<CHARSET>",
                    "content": "This element holds at least one <int> element of an Unicode code point or more.\n"
                },
                {
                    "name": "<LANGSET>",
                    "content": "This element holds at least one <string> element of a RFC-3066-style languages or more.\n"
                },
                {
                    "name": "<NAME>",
                    "content": "Holds  a  property  name.  Evaluates to the first value from the property of the pattern.  If\nthe 'target' attribute is not present, it will default to 'default', in which case the  prop‐\nerty  is returned from the font pattern during a target=\"font\" match, and to the pattern dur‐\ning a target=\"pattern\" match.  The attribute can also take the values 'font' or 'pattern'  to\nexplicitly  choose which pattern to use.  It is an error to use a target of 'font' in a match\nthat has target=\"pattern\".\n"
                },
                {
                    "name": "<CONST>",
                    "content": "Holds the name of a constant; these are always integers and serve as symbolic names for  com‐\nmon font values:\n\nConstant        Property        Value\n-------------------------------------\nthin            weight          0\nextralight      weight          40\nultralight      weight          40\nlight           weight          50\ndemilight       weight          55\nsemilight       weight          55\nbook            weight          75\nregular         weight          80\nnormal          weight          80\nmedium          weight          100\ndemibold        weight          180\nsemibold        weight          180\nbold            weight          200\nextrabold       weight          205\nblack           weight          210\nheavy           weight          210\nroman           slant           0\nitalic          slant           100\noblique         slant           110\nultracondensed  width           50\nextracondensed  width           63\ncondensed       width           75\nsemicondensed   width           87\nnormal          width           100\nsemiexpanded    width           113\nexpanded        width           125\nextraexpanded   width           150\nultraexpanded   width           200\nproportional    spacing         0\ndual            spacing         90\nmono            spacing         100\ncharcell        spacing         110\nunknown         rgba            0\nrgb             rgba            1\nbgr             rgba            2\nvrgb            rgba            3\nvbgr            rgba            4\nnone            rgba            5\nlcdnone         lcdfilter       0\nlcddefault      lcdfilter       1\nlcdlight        lcdfilter       2\nlcdlegacy       lcdfilter       3\nhintnone        hintstyle       0\nhintslight      hintstyle       1\nhintmedium      hintstyle       2\nhintfull        hintstyle       3\n\n"
                },
                {
                    "name": "<OR>, <AND>, <PLUS>, <MINUS>, <TIMES>, <DIVIDE>",
                    "content": "These  elements  perform  the specified operation on a list of expression elements.  <or> and\n<and> are boolean, not bitwise.\n\n<EQ>, <NOTEQ>, <LESS>, <LESSEQ>, <MORE>, <MOREEQ>, <CONTAINS>, <NOTCONTAINS\nThese elements compare two values, producing a boolean result.\n"
                },
                {
                    "name": "<NOT>",
                    "content": "Inverts the boolean sense of its one expression element\n"
                },
                {
                    "name": "<IF>",
                    "content": "This element takes three expression elements; if the value of the first is true, it  produces\nthe value of the second, otherwise it produces the value of the third.\n"
                },
                {
                    "name": "<ALIAS>",
                    "content": "Alias  elements provide a shorthand notation for the set of common match operations needed to\nsubstitute one font family for another.  They contain a <family> element followed by optional\n<prefer>, <accept> and <default> elements.  Fonts matching the <family> element are edited to\nprepend the list of <prefer>ed families before the matching <family>, append the <accept>able\nfamilies after the matching <family> and append the <default> families to the end of the fam‐\nily list.\n"
                },
                {
                    "name": "<FAMILY>",
                    "content": "Holds a single font family name\n"
                },
                {
                    "name": "<PREFER>, <ACCEPT>, <DEFAULT>",
                    "content": "These hold a list of <family> elements to be used by the <alias> element.\n"
                }
            ]
        },
        "EXAMPLE CONFIGURATION FILE": {
            "content": "SYSTEM CONFIGURATION FILE\nThis is an example of a system-wide configuration file\n\n<?xml version=\"1.0\"?>\n<!DOCTYPE fontconfig SYSTEM \"fonts.dtd\">\n<!-- /etc/fonts/fonts.conf file to configure system font access -->\n<fontconfig>\n<!--\nFind fonts in these directories\n-->\n<dir>/usr/share/fonts</dir>\n<dir>/usr/X11R6/lib/X11/fonts</dir>\n\n<!--\nAccept deprecated 'mono' alias, replacing it with 'monospace'\n-->\n<match target=\"pattern\">\n<test qual=\"any\" name=\"family\"><string>mono</string></test>\n<edit name=\"family\" mode=\"assign\"><string>monospace</string></edit>\n</match>\n\n<!--\nNames not including any well known alias are given 'sans-serif'\n-->\n<match target=\"pattern\">\n<test qual=\"all\" name=\"family\" compare=\"noteq\"><string>sans-serif</string></test>\n<test qual=\"all\" name=\"family\" compare=\"noteq\"><string>serif</string></test>\n<test qual=\"all\" name=\"family\" compare=\"noteq\"><string>monospace</string></test>\n<edit name=\"family\" mode=\"appendlast\"><string>sans-serif</string></edit>\n</match>\n\n<!--\nLoad per-user customization file, but don't complain\nif it doesn't exist\n-->\n<include ignoremissing=\"yes\" prefix=\"xdg\">fontconfig/fonts.conf</include>\n\n<!--\nLoad local customization files, but don't complain\nif there aren't any\n-->\n<include ignoremissing=\"yes\">conf.d</include>\n<include ignoremissing=\"yes\">local.conf</include>\n\n<!--\nAlias well known font names to available TrueType fonts.\nThese substitute TrueType faces for similar Type1\nfaces to improve screen appearance.\n-->\n<alias>\n<family>Times</family>\n<prefer><family>Times New Roman</family></prefer>\n<default><family>serif</family></default>\n</alias>\n<alias>\n<family>Helvetica</family>\n<prefer><family>Arial</family></prefer>\n<default><family>sans</family></default>\n</alias>\n<alias>\n<family>Courier</family>\n<prefer><family>Courier New</family></prefer>\n<default><family>monospace</family></default>\n</alias>\n\n<!--\nProvide required aliases for standard names\nDo these after the users configuration file so that\nany aliases there are used preferentially\n-->\n<alias>\n<family>serif</family>\n<prefer><family>Times New Roman</family></prefer>\n</alias>\n<alias>\n<family>sans</family>\n<prefer><family>Arial</family></prefer>\n</alias>\n<alias>\n<family>monospace</family>\n<prefer><family>Andale Mono</family></prefer>\n</alias>\n\n<--\nThe example of the requirements of OR operator;\nIf the 'family' contains 'Courier New' OR 'Courier'\nadd 'monospace' as the alternative\n-->\n<match target=\"pattern\">\n<test name=\"family\" compare=\"eq\">\n<string>Courier New</string>\n</test>\n<edit name=\"family\" mode=\"prepend\">\n<string>monospace</string>\n</edit>\n</match>\n<match target=\"pattern\">\n<test name=\"family\" compare=\"eq\">\n<string>Courier</string>\n</test>\n<edit name=\"family\" mode=\"prepend\">\n<string>monospace</string>\n</edit>\n</match>\n\n</fontconfig>\n\n\nUSER CONFIGURATION FILE\nThis is an example of a per-user configuration file that lives  in  $XDGCONFIGHOME/fontcon‐\nfig/fonts.conf\n\n<?xml version=\"1.0\"?>\n<!DOCTYPE fontconfig SYSTEM \"fonts.dtd\">\n<!-- $XDGCONFIGHOME/fontconfig/fonts.conf for per-user font configuration -->\n<fontconfig>\n\n<!--\nPrivate font directory\n-->\n<dir prefix=\"xdg\">fonts</dir>\n\n<!--\nuse rgb sub-pixel ordering to improve glyph appearance on\nLCD screens.  Changes affecting rendering, but not matching\nshould always use target=\"font\".\n-->\n<match target=\"font\">\n<edit name=\"rgba\" mode=\"assign\"><const>rgb</const></edit>\n</match>\n<!--\nuse WenQuanYi Zen Hei font when serif is requested for Chinese\n-->\n<match>\n<!--\nIf you don't want to use WenQuanYi Zen Hei font for zh-tw etc,\nyou can use zh-cn instead of zh.\nPlease note, even if you set zh-cn, it still matches zh.\nif you don't like it, you can use compare=\"eq\"\ninstead of compare=\"contains\".\n-->\n<test name=\"lang\" compare=\"contains\">\n<string>zh</string>\n</test>\n<test name=\"family\">\n<string>serif</string>\n</test>\n<edit name=\"family\" mode=\"prepend\">\n<string>WenQuanYi Zen Hei</string>\n</edit>\n</match>\n<!--\nuse VL Gothic font when sans-serif is requested for Japanese\n-->\n<match>\n<test name=\"lang\" compare=\"contains\">\n<string>ja</string>\n</test>\n<test name=\"family\">\n<string>sans-serif</string>\n</test>\n<edit name=\"family\" mode=\"prepend\">\n<string>VL Gothic</string>\n</edit>\n</match>\n</fontconfig>\n\n",
            "subsections": []
        },
        "FILES": {
            "content": "fonts.conf contains configuration information for the fontconfig library consisting of direc‐\ntories to look at for font information as well as instructions on editing  program  specified\nfont patterns before attempting to match the available fonts.  It is in XML format.\n\nconf.d  is the conventional name for a directory of additional configuration files managed by\nexternal applications or the local administrator.  The filenames starting with decimal digits\nare  sorted  in lexicographic order and used as additional configuration files.  All of these\nfiles are in XML format.  The master fonts.conf file references this  directory  in  an  <in‐\nclude> directive.\n\nfonts.dtd is a DTD that describes the format of the configuration files.\n\n$XDGCONFIGHOME/fontconfig/conf.d  and  ~/.fonts.conf.d  is the conventional name for a per-\nuser directory of (typically auto-generated) configuration files, although the  actual  loca‐\ntion  is  specified in the global fonts.conf file. please note that ~/.fonts.conf.d is depre‐\ncated now. it will not be read by default in the future version.\n\n$XDGCONFIGHOME/fontconfig/fonts.conf and ~/.fonts.conf is  the  conventional  location  for\nper-user  font  configuration,  although  the  actual  location  is  specified  in the global\nfonts.conf file. please note that ~/.fonts.conf is deprecated now. it will not be read by de‐\nfault in the future version.\n\n$XDGCACHEHOME/fontconfig/*.cache-* and  ~/.fontconfig/*.cache-* is the conventional reposi‐\ntory of font information that isn't found in the per-directory caches.  This file is automat‐\nically  maintained by fontconfig. please note that ~/.fontconfig/*.cache-* is deprecated now.\nit will not be read by default in the future version.\n",
            "subsections": []
        },
        "ENVIRONMENT VARIABLES": {
            "content": "FONTCONFIGFILE is used to override the default configuration file.\n\nFONTCONFIGPATH is used to override the default configuration directory.\n\nFONTCONFIGSYSROOT is used to set a default sysroot directory.\n\nFCDEBUG is used to output the detailed debugging messages. see Debugging  Applications  sec‐\ntion for more details.\n\nFCDBGMATCHFILTER  is used to filter out the patterns. this takes a comma-separated list of\nobject names and effects only when FCDEBUG has MATCH2. see  Debugging  Applications  section\nfor more details.\n\nFCLANG  is  used  to  specify the default language as the weak binding in the query. if this\nisn't set, the default language will be determined from current locale.\n\nFONTCONFIGUSEMMAP is used to control the use of mmap(2) for the cache files  if  available.\nthis  take  a  boolean  value.  fontconfig  will  checks if the cache files are stored on the\nfilesystem that is safe to use mmap(2). explicitly setting  this  environment  variable  will\ncauses skipping this check and enforce to use or not use mmap(2) anyway.\n\nSOURCEDATEEPOCH  is used to ensure fc-cache(1) generates files in a deterministic manner in\norder to support reproducible builds. When set to a numeric representation of UNIX timestamp,\nfontconfig  will  prefer this value over using the modification timestamps of the input files\nin order to identify which cache files require regeneration. If SOURCEDATEEPOCH is not  set\n(or is newer than the mtime of the directory), the existing behaviour is unchanged.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "fc-cat(1),    fc-cache(1),    fc-list(1),    fc-match(1),    fc-query(1),   SOURCEDATEEPOCH\n<URL:https://reproducible-builds.org/specs/source-date-epoch/>.\n",
            "subsections": []
        },
        "VERSION": {
            "content": "Fontconfig version 2.13.1\n\n\n\n23 March 2022                              FONTS-CONF(5)",
            "subsections": []
        }
    },
    "summary": "fonts.conf - Font configuration files",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "fc-cat",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/fc-cat/1/json"
        },
        {
            "name": "fc-cache",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/fc-cache/1/json"
        },
        {
            "name": "fc-list",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/fc-list/1/json"
        },
        {
            "name": "fc-match",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/fc-match/1/json"
        },
        {
            "name": "fc-query",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/fc-query/1/json"
        }
    ]
}