{ "mode": "man", "parameter": "locale", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/locale/5/json", "generated": "2026-05-30T07:09:34Z", "sections": { "NAME": { "content": "locale - describes a locale definition file\n", "subsections": [] }, "DESCRIPTION": { "content": "The locale definition file contains all the information that the localedef(1) command needs\nto convert it into the binary locale database.\n\nThe definition files consist of sections which each describe a locale category in detail.\nSee locale(7) for additional details for these categories.\n", "subsections": [ { "name": "Syntax", "content": "The locale definition file starts with a header that may consist of the following keywords:\n\nescapechar\nis followed by a character that should be used as the escape-character for the rest of\nthe file to mark characters that should be interpreted in a special way. It defaults\nto the backslash (\\).\n\ncommentchar\nis followed by a character that will be used as the comment-character for the rest of\nthe file. It defaults to the number sign (#).\n\nThe locale definition has one part for each locale category. Each part can be copied from\nanother existing locale or can be defined from scratch. If the category should be copied,\nthe only valid keyword in the definition is copy followed by the name of the locale in double\nquotes which should be copied. The exceptions for this rule are LCCOLLATE and LCCTYPE\nwhere a copy statement can be followed by locale-specific rules and selected overrides.\n\nWhen defining a locale or a category from scratch, an existing system- provided locale defi‐\nnition file should be used as a reference to follow common glibc conventions.\n" }, { "name": "Locale category sections", "content": "The following category sections are defined by POSIX:\n\n* LCCTYPE\n\n* LCCOLLATE\n\n* LCMESSAGES\n\n* LCMONETARY\n\n* LCNUMERIC\n\n* LCTIME\n\nIn addition, since version 2.2, the GNU C library supports the following nonstandard cate‐\ngories:\n\n* LCADDRESS\n\n* LCIDENTIFICATION\n\n* LCMEASUREMENT\n\n* LCNAME\n\n* LCPAPER\n\n* LCTELEPHONE\n\nSee locale(7) for a more detailed description of each category.\n\nLCADDRESS\nThe definition starts with the string LCADDRESS in the first column.\n\nThe following keywords are allowed:\n\npostalfmt\nfollowed by a string containing field descriptors that define the format used for\npostal addresses in the locale. The following field descriptors are recognized:\n\n%n Person's name, possibly constructed with the LCNAME namefmt keyword (since\nglibc 2.24).\n\n%a Care of person, or organization.\n\n%f Firm name.\n\n%d Department name.\n\n%b Building name.\n\n%s Street or block (e.g., Japanese) name.\n\n%h House number or designation.\n\n%N Insert an end-of-line if the previous descriptor's value was not an empty string;\notherwise ignore.\n\n%t Insert a space if the previous descriptor's value was not an empty string; other‐\nwise ignore.\n\n%r Room number, door designation.\n\n%e Floor number.\n\n%C Country designation, from the countrypost keyword.\n\n%l Local township within town or city (since glibc 2.24).\n\n%z Zip number, postal code.\n\n%T Town, city.\n\n%S State, province, or prefecture.\n\n%c Country, as taken from data record.\n\nEach field descriptor may have an 'R' after the '%' to specify that the information is\ntaken from a Romanized version string of the entity.\n\ncountryname\nfollowed by the country name in the language of the current document (e.g., \"Deutsch‐\nland\" for the deDE locale).\n\ncountrypost\nfollowed by the abbreviation of the country (see CERTMAILCODES).\n\ncountryab2\nfollowed by the two-letter abbreviation of the country (ISO 3166).\n\ncountryab3\nfollowed by the three-letter abbreviation of the country (ISO 3166).\n\ncountrynum\nfollowed by the numeric country code (ISO 3166).\n\ncountrycar\nfollowed by the international license plate country code.\n\ncountryisbn\nfollowed by the ISBN code (for books).\n\nlangname\nfollowed by the language name in the language of the current document.\n\nlangab\nfollowed by the two-letter abbreviation of the language (ISO 639).\n\nlangterm\nfollowed by the three-letter abbreviation of the language (ISO 639-2/T).\n\nlanglib\nfollowed by the three-letter abbreviation of the language for library use (ISO\n639-2/B). Applications should in general prefer langterm over langlib.\n\nThe LCADDRESS definition ends with the string END LCADDRESS.\n\nLCCTYPE\nThe definition starts with the string LCCTYPE in the first column.\n\nThe following keywords are allowed:\n\nupper followed by a list of uppercase letters. The letters A through Z are included auto‐\nmatically. Characters also specified as cntrl, digit, punct, or space are not al‐\nlowed.\n\nlower followed by a list of lowercase letters. The letters a through z are included auto‐\nmatically. Characters also specified as cntrl, digit, punct, or space are not al‐\nlowed.\n\nalpha followed by a list of letters. All character specified as either upper or lower are\nautomatically included. Characters also specified as cntrl, digit, punct, or space\nare not allowed.\n\ndigit followed by the characters classified as numeric digits. Only the digits 0 through 9\nare allowed. They are included by default in this class.\n\nspace followed by a list of characters defined as white-space characters. Characters also\nspecified as upper, lower, alpha, digit, graph, or xdigit are not allowed. The char‐\nacters , , , , , and \nare automatically included.\n\ncntrl followed by a list of control characters. Characters also specified as upper, lower,\nalpha, digit, punct, graph, print, or xdigit are not allowed.\n\npunct followed by a list of punctuation characters. Characters also specified as upper,\nlower, alpha, digit, cntrl, xdigit, or the character are not allowed.\n\ngraph followed by a list of printable characters, not including the character. The\ncharacters defined as upper, lower, alpha, digit, xdigit, and punct are automatically\nincluded. Characters also specified as cntrl are not allowed.\n\nprint followed by a list of printable characters, including the character. The\ncharacters defined as upper, lower, alpha, digit, xdigit, punct, and the char‐\nacter are automatically included. Characters also specified as cntrl are not allowed.\n\nxdigit followed by a list of characters classified as hexadecimal digits. The decimal digits\nmust be included followed by one or more set of six characters in ascending order.\nThe following characters are included by default: 0 through 9, a through f, A through\nF.\n\nblank followed by a list of characters classified as blank. The characters and\n are automatically included.\n\ncharclass\nfollowed by a list of locale-specific character class names which are then to be de‐\nfined in the locale.\n\ntoupper\nfollowed by a list of mappings from lowercase to uppercase letters. Each mapping is a\npair of a lowercase and an uppercase letter separated with a , and enclosed in paren‐\ntheses.\n\ntolower\nfollowed by a list of mappings from uppercase to lowercase letters. If the keyword\ntolower is not present, the reverse of the toupper list is used.\n\nmap totitle\nfollowed by a list of mapping pairs of characters and letters to be used in titles\n(headings).\n\nclass followed by a locale-specific character class definition, starting with the class name\nfollowed by the characters belonging to the class.\n\ncharconv\nfollowed by a list of locale-specific character mapping names which are then to be de‐\nfined in the locale.\n\noutdigit\nfollowed by a list of alternate output digits for the locale.\n\nmap toinpunct\nfollowed by a list of mapping pairs of alternate digits and separators for input dig‐\nits for the locale.\n\nmap tooutpunct\nfollowed by a list of mapping pairs of alternate separators for output for the locale.\n\ntranslitstart\nmarks the start of the transliteration rules section. The section can contain the in‐\nclude keyword in the beginning followed by locale-specific rules and overrides. Any\nrule specified in the locale file will override any rule copied or included from other\nfiles. In case of duplicate rule definitions in the locale file, only the first rule\nis used.\n\nA transliteration rule consist of a character to be transliterated followed by a list\nof transliteration targets separated by semicolons. The first target which can be\npresented in the target character set is used, if none of them can be used the de‐\nfaultmissing character will be used instead.\n\ninclude\nin the transliteration rules section includes a transliteration rule file (and option‐\nally a repertoire map file).\n\ndefaultmissing\nin the transliteration rules section defines the default character to be used for\ntransliteration where none of the targets cannot be presented in the target character\nset.\n\ntranslitend\nmarks the end of the transliteration rules.\n\nThe LCCTYPE definition ends with the string END LCCTYPE.\n\nLCCOLLATE\nNote that glibc does not support all POSIX-defined options, only the options described below\nare supported (as of glibc 2.23).\n\nThe definition starts with the string LCCOLLATE in the first column.\n\nThe following keywords are allowed:\n\ncollweightmax\nfollowed by the number representing used collation levels. This keyword is recognized\nbut ignored by glibc.\n\ncollating-element\nfollowed by the definition of a collating-element symbol representing a multicharacter\ncollating element.\n\ncollating-symbol\nfollowed by the definition of a collating symbol that can be used in collation order\nstatements.\n\ndefine followed by string to be evaluated in an ifdef string / else / endif construct.\n\nreorder-after\nfollowed by a redefinition of a collation rule.\n\nreorder-end\nmarks the end of the redefinition of a collation rule.\n\nreorder-sections-after\nfollowed by a script name to reorder listed scripts after.\n\nreorder-sections-end\nmarks the end of the reordering of sections.\n\nscript followed by a declaration of a script.\n\nsymbol-equivalence\nfollowed by a collating-symbol to be equivalent to another defined collating-symbol.\n\nThe collation rule definition starts with a line:\n\norderstart\nfollowed by a list of keywords chosen from forward, backward, or position. The order\ndefinition consists of lines that describe the collation order and is terminated with\nthe keyword orderend.\n\nThe LCCOLLATE definition ends with the string END LCCOLLATE.\n\nLCIDENTIFICATION\nThe definition starts with the string LCIDENTIFICATION in the first column.\n\nThe following keywords are allowed:\n\ntitle followed by the title of the locale document (e.g., \"Maori language locale for New\nZealand\").\n\nsource followed by the name of the organization that maintains this document.\n\naddress\nfollowed by the address of the organization that maintains this document.\n\ncontact\nfollowed by the name of the contact person at the organization that maintains this\ndocument.\n\nemail followed by the email address of the person or organization that maintains this docu‐\nment.\n\ntel followed by the telephone number (in international format) of the organization that\nmaintains this document. As of glibc 2.24, this keyword is deprecated in favor of\nother contact methods.\n\nfax followed by the fax number (in international format) of the organization that main‐\ntains this document. As of glibc 2.24, this keyword is deprecated in favor of other\ncontact methods.\n\nlanguage\nfollowed by the name of the language to which this document applies.\n\nterritory\nfollowed by the name of the country/geographic extent to which this document applies.\n\naudience\nfollowed by a description of the audience for which this document is intended.\n\napplication\nfollowed by a description of any special application for which this document is in‐\ntended.\n\nabbreviation\nfollowed by the short name for provider of the source of this document.\n\nrevision\nfollowed by the revision number of this document.\n\ndate followed by the revision date of this document.\n\nIn addition, for each of the categories defined by the document, there should be a line\nstarting with the keyword category, followed by:\n\n* a string that identifies this locale category definition,\n\n* a semicolon, and\n\n* one of the LC* identifiers.\n\nThe LCIDENTIFICATION definition ends with the string END LCIDENTIFICATION.\n\nLCMESSAGES\nThe definition starts with the string LCMESSAGES in the first column.\n\nThe following keywords are allowed:\n\nyesexpr\nfollowed by a regular expression that describes possible yes-responses.\n\nnoexpr followed by a regular expression that describes possible no-responses.\n\nyesstr followed by the output string corresponding to \"yes\".\n\nnostr followed by the output string corresponding to \"no\".\n\nThe LCMESSAGES definition ends with the string END LCMESSAGES.\n\nLCMEASUREMENT\nThe definition starts with the string LCMEASUREMENT in the first column.\n\nThe following keywords are allowed:\n\nmeasurement\nfollowed by number identifying the standard used for measurement. The following val‐\nues are recognized:\n\n1 Metric.\n\n2 US customary measurements.\n\nThe LCMEASUREMENT definition ends with the string END LCMEASUREMENT.\n\nLCMONETARY\nThe definition starts with the string LCMONETARY in the first column.\n\nThe following keywords are allowed:\n\nintcurrsymbol\nfollowed by the international currency symbol. This must be a 4-character string con‐\ntaining the international currency symbol as defined by the ISO 4217 standard (three\ncharacters) followed by a separator.\n\ncurrencysymbol\nfollowed by the local currency symbol.\n\nmondecimalpoint\nfollowed by the single-character string that will be used as the decimal delimiter\nwhen formatting monetary quantities.\n\nmonthousandssep\nfollowed by the single-character string that will be used as a group separator when\nformatting monetary quantities.\n\nmongrouping\nfollowed by a sequence of integers separated by semicolons that describe the format‐\nting of monetary quantities. See grouping below for details.\n\npositivesign\nfollowed by a string that is used to indicate a positive sign for monetary quantities.\n\nnegativesign\nfollowed by a string that is used to indicate a negative sign for monetary quantities.\n\nintfracdigits\nfollowed by the number of fractional digits that should be used when formatting with\nthe intcurrsymbol.\n\nfracdigits\nfollowed by the number of fractional digits that should be used when formatting with\nthe currencysymbol.\n\npcsprecedes\nfollowed by an integer that indicates the placement of currencysymbol for a nonnega‐\ntive formatted monetary quantity:\n\n0 the symbol succeeds the value.\n\n1 the symbol precedes the value.\n\npsepbyspace\nfollowed by an integer that indicates the separation of currencysymbol, the sign\nstring, and the value for a nonnegative formatted monetary quantity. The following\nvalues are recognized:\n\n0 No space separates the currency symbol and the value.\n\n1 If the currency symbol and the sign string are adjacent, a space separates them\nfrom the value; otherwise a space separates the currency symbol and the value.\n\n2 If the currency symbol and the sign string are adjacent, a space separates them\nfrom the value; otherwise a space separates the sign string and the value.\n\nncsprecedes\nfollowed by an integer that indicates the placement of currencysymbol for a negative\nformatted monetary quantity. The same values are recognized as for pcsprecedes.\n\nnsepbyspace\nfollowed by an integer that indicates the separation of currencysymbol, the sign\nstring, and the value for a negative formatted monetary quantity. The same values are\nrecognized as for psepbyspace.\n\npsignposn\nfollowed by an integer that indicates where the positivesign should be placed for a\nnonnegative monetary quantity:\n\n0 Parentheses enclose the quantity and the currencysymbol or intcurrsymbol.\n\n1 The sign string precedes the quantity and the currencysymbol or the intcurrsym‐\nbol.\n\n2 The sign string succeeds the quantity and the currencysymbol or the intcurrsym‐\nbol.\n\n3 The sign string precedes the currencysymbol or the intcurrsymbol.\n\n4 The sign string succeeds the currencysymbol or the intcurrsymbol.\n\nnsignposn\nfollowed by an integer that indicates where the negativesign should be placed for a\nnegative monetary quantity. The same values are recognized as for psignposn.\n\nintpcsprecedes\nfollowed by an integer that indicates the placement of intcurrsymbol for a nonnega‐\ntive internationally formatted monetary quantity. The same values are recognized as\nfor pcsprecedes.\n\nintncsprecedes\nfollowed by an integer that indicates the placement of intcurrsymbol for a negative\ninternationally formatted monetary quantity. The same values are recognized as for\npcsprecedes.\n\nintpsepbyspace\nfollowed by an integer that indicates the separation of intcurrsymbol, the sign\nstring, and the value for a nonnegative internationally formatted monetary quantity.\nThe same values are recognized as for psepbyspace.\n\nintnsepbyspace\nfollowed by an integer that indicates the separation of intcurrsymbol, the sign\nstring, and the value for a negative internationally formatted monetary quantity. The\nsame values are recognized as for psepbyspace.\n\nintpsignposn\nfollowed by an integer that indicates where the positivesign should be placed for a\nnonnegative internationally formatted monetary quantity. The same values are recog‐\nnized as for psignposn.\n\nintnsignposn\nfollowed by an integer that indicates where the negativesign should be placed for a\nnegative internationally formatted monetary quantity. The same values are recognized\nas for psignposn.\n\nThe LCMONETARY definition ends with the string END LCMONETARY.\n\nLCNAME\nThe definition starts with the string LCNAME in the first column.\n\nVarious keywords are allowed, but only namefmt is mandatory. Other keywords are needed only\nif there is common convention to use the corresponding salutation in this locale. The al‐\nlowed keywords are as follows:\n\nnamefmt\nfollowed by a string containing field descriptors that define the format used for\nnames in the locale. The following field descriptors are recognized:\n\n%f Family name(s).\n\n%F Family names in uppercase.\n\n%g First given name.\n\n%G First given initial.\n\n%l First given name with Latin letters.\n\n%o Other shorter name.\n\n%m Additional given name(s).\n\n%M Initials for additional given name(s).\n\n%p Profession.\n\n%s Salutation, such as \"Doctor\".\n\n%S Abbreviated salutation, such as \"Mr.\" or \"Dr.\".\n\n%d Salutation, using the FDCC-sets conventions.\n\n%t If the preceding field descriptor resulted in an empty string, then the empty\nstring, otherwise a space character.\n\nnamegen\nfollowed by the general salutation for any gender.\n\nnamemr\nfollowed by the salutation for men.\n\nnamemrs\nfollowed by the salutation for married women.\n\nnamemiss\nfollowed by the salutation for unmarried women.\n\nnamems\nfollowed by the salutation valid for all women.\n\nThe LCNAME definition ends with the string END LCNAME.\n\nLCNUMERIC\nThe definition starts with the string LCNUMERIC in the first column.\n\nThe following keywords are allowed:\n\ndecimalpoint\nfollowed by the single-character string that will be used as the decimal delimiter\nwhen formatting numeric quantities.\n\nthousandssep\nfollowed by the single-character string that will be used as a group separator when\nformatting numeric quantities.\n\ngrouping\nfollowed by a sequence of integers separated by semicolons that describe the format‐\nting of numeric quantities.\n\nEach integer specifies the number of digits in a group. The first integer defines the\nsize of the group immediately to the left of the decimal delimiter. Subsequent inte‐\ngers define succeeding groups to the left of the previous group. If the last integer\nis not -1, then the size of the previous group (if any) is repeatedly used for the re‐\nmainder of the digits. If the last integer is -1, then no further grouping is per‐\nformed.\n\nThe LCNUMERIC definition ends with the string END LCNUMERIC.\n\nLCPAPER\nThe definition starts with the string LCPAPER in the first column.\n\nThe following keywords are allowed:\n\nheight followed by the height, in millimeters, of the standard paper format.\n\nwidth followed by the width, in millimeters, of the standard paper format.\n\nThe LCPAPER definition ends with the string END LCPAPER.\n\nLCTELEPHONE\nThe definition starts with the string LCTELEPHONE in the first column.\n\nThe following keywords are allowed:\n\ntelintfmt\nfollowed by a string that contains field descriptors that identify the format used to\ndial international numbers. The following field descriptors are recognized:\n\n%a Area code without nationwide prefix (the prefix is often \"00\").\n\n%A Area code including nationwide prefix.\n\n%l Local number (within area code).\n\n%e Extension (to local number).\n\n%c Country code.\n\n%C Alternate carrier service code used for dialing abroad.\n\n%t If the preceding field descriptor resulted in an empty string, then the empty\nstring, otherwise a space character.\n\nteldomfmt\nfollowed by a string that contains field descriptors that identify the format used to\ndial domestic numbers. The recognized field descriptors are the same as for\ntelintfmt.\n\nintselect\nfollowed by the prefix used to call international phone numbers.\n\nintprefix\nfollowed by the prefix used from other countries to dial this country.\n\nThe LCTELEPHONE definition ends with the string END LCTELEPHONE.\n\nLCTIME\nThe definition starts with the string LCTIME in the first column.\n\nThe following keywords are allowed:\n\nabday followed by a list of abbreviated names of the days of the week. The list starts with\nthe first day of the week as specified by week (Sunday by default). See NOTES.\n\nday followed by a list of names of the days of the week. The list starts with the first\nday of the week as specified by week (Sunday by default). See NOTES.\n\nabmon followed by a list of abbreviated month names.\n\nmon followed by a list of month names.\n\ndtfmt\nfollowed by the appropriate date and time format (for syntax, see strftime(3)).\n\ndfmt followed by the appropriate date format (for syntax, see strftime(3)).\n\ntfmt followed by the appropriate time format (for syntax, see strftime(3)).\n\nampm followed by the appropriate representation of the am and pm strings. This should be\nleft empty for locales not using AM/PM convention.\n\ntfmtampm\nfollowed by the appropriate time format (for syntax, see strftime(3)) when using 12h\nclock format. This should be left empty for locales not using AM/PM convention.\n\nera followed by semicolon-separated strings that define how years are counted and dis‐\nplayed for each era in the locale. Each string has the following format:\n\ndirection:offset:startdate:enddate:eraname:eraformat\n\nThe fields are to be defined as follows:\n\ndirection\nEither + or -. + means the years closer to startdate have lower numbers than\nyears closer to enddate. - means the opposite.\n\noffset\nThe number of the year closest to startdate in the era, corresponding to the %Ey\ndescriptor (see strptime(3)).\n\nstartdate\nThe start of the era in the form of yyyy/mm/dd. Years prior AD 1 are represented\nas negative numbers.\n\nenddate\nThe end of the era in the form of yyyy/mm/dd, or one of the two special values of\n-* or +*. -* means the ending date is the beginning of time. +* means the ending\ndate is the end of time.\n\neraname\nThe name of the era corresponding to the %EC descriptor (see strptime(3)).\n\neraformat\nThe format of the year in the era corresponding to the %EY descriptor (see strp‐‐\ntime(3)).\n\neradfmt\nfollowed by the format of the date in alternative era notation, corresponding to the\n%Ex descriptor (see strptime(3)).\n\neratfmt\nfollowed by the format of the time in alternative era notation, corresponding to the\n%EX descriptor (see strptime(3)).\n\neradtfmt\nfollowed by the format of the date and time in alternative era notation, corresponding\nto the %Ec descriptor (see strptime(3)).\n\naltdigits\nfollowed by the alternative digits used for date and time in the locale.\n\nweek followed by a list of three values separated by semicolons: The number of days in a\nweek (by default 7), a date of beginning of the week (by default corresponds to Sun‐\nday), and the minimal length of the first week in year (by default 4). Regarding the\nstart of the week, 19971130 shall be used for Sunday and 19971201 shall be used for\nMonday. See NOTES.\n\nfirstweekday (since glibc 2.2)\nfollowed by the number of the day from the day list to be shown as the first day of\nthe week in calendar applications. The default value of 1 corresponds to either Sun‐\nday or Monday depending on the value of the second week list item. See NOTES.\n\nfirstworkday (since glibc 2.2)\nfollowed by the number of the first working day from the day list. The default value\nis 2. See NOTES.\n\ncaldirection\nfollowed by a number value that indicates the direction for the display of calendar\ndates, as follows:\n\n1 Left-right from top.\n\n2 Top-down from left.\n\n3 Right-left from top.\n\ndatefmt\nfollowed by the appropriate date representation for date(1) (for syntax, see strf‐‐\ntime(3)).\n\nThe LCTIME definition ends with the string END LCTIME.\n" } ] }, "FILES": { "content": "/usr/lib/locale/locale-archive\nUsual default locale archive location.\n\n/usr/share/i18n/locales\nUsual default path for locale definition files.\n", "subsections": [] }, "CONFORMING TO": { "content": "POSIX.2.\n", "subsections": [] }, "NOTES": { "content": "The collective GNU C library community wisdom regarding abday, day, week, firstweekday, and\nfirstworkday states at https://sourceware.org/glibc/wiki/Locales the following:\n\n* The value of the second week list item specifies the base of the abday and day lists.\n\n* firstweekday specifies the offset of the first day-of-week in the abday and day lists.\n\n* For compatibility reasons, all glibc locales should set the value of the second week list\nitem to 19971130 (Sunday) and base the abday and day lists appropriately, and set\nfirstweekday and firstworkday to 1 or 2, depending on whether the week and work week ac‐\ntually starts on Sunday or Monday for the locale.\n", "subsections": [] }, "SEE ALSO": { "content": "iconv(1), locale(1), localedef(1), localeconv(3), newlocale(3), setlocale(3), strftime(3),\nstrptime(3), uselocale(3), charmap(5), charsets(7), locale(7), unicode(7), utf-8(7)\n", "subsections": [] }, "COLOPHON": { "content": "This page is part of release 5.10 of the Linux man-pages project. A description of the\nproject, information about reporting bugs, and the latest version of this page, can be found\nat https://www.kernel.org/doc/man-pages/.\n\n\n\nLinux 2020-11-01 LOCALE(5)", "subsections": [] } }, "summary": "locale - describes a locale definition file", "flags": [], "examples": [], "see_also": [ { "name": "iconv", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/iconv/1/json" }, { "name": "localedef", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/localedef/1/json" }, { "name": "localeconv", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/localeconv/3/json" }, { "name": "newlocale", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/newlocale/3/json" }, { "name": "setlocale", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/setlocale/3/json" }, { "name": "strftime", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/strftime/3/json" }, { "name": "strptime", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/strptime/3/json" }, { "name": "uselocale", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/uselocale/3/json" }, { "name": "charmap", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/charmap/5/json" }, { "name": "charsets", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/charsets/7/json" }, { "name": "unicode", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/unicode/7/json" }, { "name": "utf-8", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/utf-8/7/json" } ] }