{ "mode": "man", "parameter": "TTF2TFM", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/TTF2TFM/1/json", "generated": "2026-10-26T16:26:27Z", "synopsis": "ttf2tfm ttffile[.ttf|.ttc] [-c caps-height-factor] [-e extension-factor] [-E encoding-id]\n[-f font-index] [-l] [-L ligature-file[.sfd]] [-n] [-N] [-O] [-p inencfile[.enc]]\n[-P platform-id] [-q] [-r old-glyphname new-glyphname] [-R replacement-file[.rpl]]\n[-s slant-factor] [-t outencfile[.enc]] [-T inoutencfile[.enc]] [-u]\n[-v vplfile[.vpl]] [-V scvplfile[.vpl]] [-w] [-x] [-y vertical-shift-factor]\n[tfmfile[.tfm]]\nttf2tfm --version | --help", "sections": { "NAME": { "content": "ttf2tfm - build TeX metric files from a TrueType font\n", "subsections": [] }, "SYNOPSIS": { "content": "ttf2tfm ttffile[.ttf|.ttc] [-c caps-height-factor] [-e extension-factor] [-E encoding-id]\n[-f font-index] [-l] [-L ligature-file[.sfd]] [-n] [-N] [-O] [-p inencfile[.enc]]\n[-P platform-id] [-q] [-r old-glyphname new-glyphname] [-R replacement-file[.rpl]]\n[-s slant-factor] [-t outencfile[.enc]] [-T inoutencfile[.enc]] [-u]\n[-v vplfile[.vpl]] [-V scvplfile[.vpl]] [-w] [-x] [-y vertical-shift-factor]\n[tfmfile[.tfm]]\nttf2tfm --version | --help\n", "subsections": [] }, "DESCRIPTION": { "content": "This program extracts the metric and kerning information of a TrueType font and converts it\ninto metric files usable by TeX (quite similar to afm2tfm which is part of the dvips package;\nplease consult its info files for more details on the various parameters (especially encoding\nfiles).\n\nSince a TrueType font often contains more than 256 glyphs, some means are necessary to map a\nsubset of the TrueType glyphs onto a TeX font. To do this, two mapping tables are needed:\nthe first (called `input' or `raw' encoding) maps the TrueType font to a raw TeX font (this\nmapping table is used by both ttf2tfm and ttf2pk), and the second (called `output' or `virtu‐\nal' encoding) maps the raw TeX font to another (virtual) TeX font, providing all kerning and\nligature information needed by TeX.\n\nThis two stage mapping has the advantage that one raw font can be accessed with various LaTeX\nencodings (e.g. T1 and OT1) via the virtual font mechanism, and just one PK file is neces‐\nsary.\n\nFor CJKV (Chinese/Japanese/Korean/old Vietnamese) fonts, a different mechanism is provided\n(see SUBFONT DEFINITION FILES below).\n", "subsections": [] }, "PARAMETERS": { "content": "Most of the command line switch names are the same as in afm2tfm for convenience. One or\nmore space characters between an option and its value is mandatory; options can't be concate‐\nnated. For historical reasons, the first parameter can not be a switch but must be the font\nname.\n", "subsections": [ { "name": "-c _", "content": "The height of small caps made with the -V switch. Default value of this real number\nis 0.8 times the height of uppercase glyphs.\n\nWill be ignored in subfont mode.\n", "flag": "-c" }, { "name": "-e _", "content": "The extension factor to stretch the characters horizontally. Default value of this\nreal number is 1.0; if less than 1.0, you get a condensed font.\n", "flag": "-e" }, { "name": "-E _", "content": "The TrueType encoding ID. Default value of this non-negative integer is 1.\n\nWill be ignored if -N is used.\n", "flag": "-E" }, { "name": "-f _", "content": "The font index in a TrueType Collection. Default is the first font (index 0). [True‐\nType collections are usually found in some CJK fonts; e.g. the first font index speci‐\nfies glyphs and metrics for horizontal writing, and the second font index does the\nsame for vertical writing. TrueType collections usually have the extension `.ttc'.]\n\nWill be ignored for ordinary TrueType fonts.\n", "flag": "-f" }, { "name": "-l", "content": "acter codes. Example: Character code 0xABCD maps to character position 123 in sub‐\nfont 45. Then a ligature in subfont 45 between position 0xAB and 0xCD pointing to\ncharacter 123 will be produced. The fonts of the Korean HLaTeX package use this fea‐\nture. Note that this option generates correct ligatures only for TrueType fonts where\nthe input cmap is identical to the output encoding. In case of HLaTeX, TTFs must have\nplatform ID 3 and encoding ID 5.\n\nWill be ignored if not in subfont mode.\n", "flag": "-l" }, { "name": "-L _", "content": "Same as -l, but character codes for ligatures are specified in ligature-file. For ex‐\nample, `-L KS-HLaTeX' generates correct ligatures for the Korean HLaTeX package re‐\ngardless of the platform and encoding ID of the used TrueType font (the file KS-HLa‐\nTeX.sfd is part of the ttf2pk package).\n\nLigature files have the same format and extension as SFD files. This option will be\nignored if not in subfont mode.\n", "flag": "-L" }, { "name": "-n", "content": "selected cmap are used.\n\nWill be ignored in subfont mode.\n", "flag": "-n" }, { "name": "-N -E -P", "content": "have no effect, causing a warning message.\n\nWill be ignored in subfont mode.\n", "flag": "-P" }, { "name": "-O", "content": "useful for symbol or CJK fonts where character names such as `A' are meaningless.\n", "flag": "-O" }, { "name": "-p _", "content": "The input encoding file name for the TTF→raw TeX mapping. This parameter has to be\nspecified in a map file (default: ttfonts.map) recorded in ttf2pk.cfg for successive\nttf2pk calls.\n\nWill be ignored in subfont mode.\n", "flag": "-p" }, { "name": "-P _", "content": "The TrueType platform ID. Default value of this non-negative integer is 3.\n\nWill be ignored if -N is used.\n", "flag": "-P" }, { "name": "-q", "content": "messages. For CJK fonts, the output can get quite large if you don't specify this\nswitch.\n", "flag": "-q" }, { "name": "-r _", "content": "Replaces old-glyphname with new-glyphname. This switch is useful if you want to give\nan unnamed glyph (i.e., a glyph which can be represented with `.gXXX' or `.cXXX' only)\na name or if you want to rename an already existing glyph name. You can't use the\n`.gXXX' or `.cXXX' glyph name constructs for new-glyphname; multiple occurrences of -r\nare possible.\n\nIf in subfont mode or if no encoding file is specified, this switch is ignored.\n", "flag": "-r" }, { "name": "-R _", "content": "Use this switch if you have many replacement pairs; they can be collected in a file\nwhich should have `.rpl' as extension. The syntax used in such replacement files is\nsimple: Each non-empty line must contain a pair `old-glyphname new-glyphname' separat‐\ned by whitespace (without the quotation marks). A percent sign starts a line comment;\nyou can continue a line on the next line with a backslash as the last character.\n\nIf in subfont mode or if no encoding file is specified, this switch is ignored.\n", "flag": "-R" }, { "name": "-s _", "content": "The obliqueness factor to slant the font, usually much smaller than 1. Default of\nthis real number is 0.0; if the value is larger than zero, the characters slope to the\nright, otherwise to the left.\n", "flag": "-s" }, { "name": "-t _", "content": "The output encoding file name for the virtual font(s). Only characters in the raw TeX\nfont are used.\n\nWill be ignored in subfont mode.\n", "flag": "-t" }, { "name": "-T _", "content": "This is equivalent to `-p inoutencfile -t inoutencfile'.\n\nWill be ignored in subfont mode.\n", "flag": "-T" }, { "name": "-u", "content": "fault, ttf2tfm tries to include all characters in the virtual font, even those not\npresent in the encoding for the virtual font (it puts them into otherwise-unused posi‐\ntions, rather arbitrarily).\n\nWill be ignored in subfont mode.\n", "flag": "-u" }, { "name": "-v _", "content": "Output a VPL file in addition to the TFM file. If no output encoding file is speci‐\nfied, ttf2tfm uses a default font encoding (cmtt10). Note: Be careful to use differ‐\nent names for the virtual font and the raw font!\n\nWill be ignored in subfont mode.\n", "flag": "-v" }, { "name": "-V _", "content": "Same as -v, but the virtual font generated is a pseudo small caps font obtained by\nscaling uppercase letters by 0.8 (resp. the value specified with -c) to typeset lower‐\ncase. This font handles accented letters and retains proper kerning.\n\nWill be ignored in subfont mode.\n", "flag": "-V" }, { "name": "-w", "content": "TrueType fonts in pdfTeX. ttf2tfm takes the TFM names and replaces the suffix with\n.enc; that is, for files foo01.tfm, foo02.tfm, ... it creates foo01.enc,\nfoo02.enc, ... at the same place.\n\nWill be ignored if not in subfont mode.\n", "flag": "-w" }, { "name": "-x -y", "content": "rotated glyphs are shifted down vertically by 0.25em.\n\nWill be ignored if not in subfont mode.\n", "flag": "-y" }, { "name": "-y _", "content": "Shift down rotated glyphs by the given amount (the unit is em).\n\nIgnored if not in subfont mode or glyphs are not rotated.\n", "flag": "-y" }, { "name": "--version", "content": "Shows the current version of ttf2tfm and the used file search library (e.g. kpath‐\nsea).\n\n--help Shows usage information.\n\nIf no TFM file name is given, the name of the TTF file is used, including the full path and\nreplacing the extension with `.tfm'.\n", "long": "--version" } ] }, "CMAPS": { "content": "Contrary to Type 1 PostScript fonts (but similar to the new CID PostScript font format), most\nTrueType fonts have more than one native mapping table, also called `cmap', which maps the\n(internal) TTF glyph indices to the (external) TTF character codes. Common examples are a\nmapping table to Unicode encoded character positions, and the standard Macintosh mapping.\n\nTo specify a TrueType mapping table, use the options -P and -E. With -P you specify the\nplatform ID; defined values are:\n\nplatform platform ID (pid)\n──────────────────────────────────\nApple Unicode 0\nMacintosh 1\nISO 2\nMicrosoft 3\n\nThe encoding ID depends on the platform. For pid=0, we ignore the -E parameter (setting it\nto zero) since the mapping table is always Unicode version 2.0. For pid=1, the following ta‐\nble lists the defined values:\n\nplatform ID = 1\nscript encoding ID (eid)\n──────────────────────────────────\nRoman 0\nJapanese 1\nChinese 2\nKorean 3\nArabic 4\nHebrew 5\nGreek 6\nRussian 7\nRoman Symbol 8\nDevanagari 9\nGurmukhi 10\nGujarati 11\nOriya 12\nBengali 13\nTamil 14\nTelugu 15\nKannada 16\nMalayalam 17\nSinhalese 18\nBurmese 19\nKhmer 20\nThai 21\nLaotian 22\nGeorgian 23\nArmenian 24\nMaldivian 25\nTibetan 26\nMongolian 27\nGeez 28\nSlavic 29\nVietnamese 30\nSindhi 31\nUninterpreted 32\n\nHere are the ISO encoding IDs:\n\nplatform ID = 2\nencoding encoding ID (eid)\nASCII 0\nISO 10646 1\nISO 8859-1 2\n\nAnd finally, the Microsoft encoding IDs:\n\nplatform ID = 3\nencoding encoding ID (eid)\nSymbol 0\nUnicode 2.0 1\nShift JIS 2\nGB 2312 (1980) 3\nBig 5 4\nKS X 1001 (Wansung) 5\nKS X 1001 (Johab) 6\nUCS-4 10\n\nThe program will abort if you specify an invalid platform/encoding ID pair. It will then\nshow the possible pid/eid pairs. Please note that most fonts have at most two or three\ncmaps, usually corresponding to the pid/eid pairs (1,0), (3,0), or (3,1) in case of Latin\nbased fonts. Valid Microsoft fonts should have a (3,1) mapping table, but some fonts exist\n(mostly Asian fonts) which have a (3,1) cmap not encoded in Unicode. The reason for this\nstrange behavior is the fact that some old MS Windows versions will reject fonts having a\nnon-(3,1) cmap (since all non-Unicode Microsoft encoding IDs are for Asian MS Windows ver‐\nsions).\n\nThe -P and -E options of ttf2tfm must be equally specified for ttf2pk; the corresponding pa‐\nrameters in a map file are `Pid' and `Eid', respectively.\n\nThe default pid/eid pair is (3,1).\n\nSimilarly, an -f option must be specified as `Fontindex' parameter in a map file.\n\nIf you use the -N switch, all cmaps are ignored, using only the PostScript names in the True‐\nType font. The corresponding option in a map file is `PS=Only'. If you use the -n switch,\nthe default glyph names built into ttf2tfm are replaced with the PS glyph names found in the\nfont. In many cases this is not what you want because the glyph names in the font are often\nincorrect or non-standard. The corresponding option in a map file is `PS=Yes'.\n\nSingle replacement glyph names specified with -r must be given directly as `old-glyphname\nnew-glyphname' in a map file; -R is equivalent to the `Replacement' option.\n", "subsections": [] }, "INPUT AND OUTPUT ENCODINGS": { "content": "You must specify the encoding vectors from the TrueType font to the raw TeX font and from the\nraw TeX font to the virtual TeX font exactly as with afm2tfm, but you have more possibilities\nto address the character codes. [With `encoding vector' a mapping table with 256 entries in\nform of a PostScript vector is meant; see the file T1-WGL4.enc of this package for an exam‐\nple.] With afm2tfm, you must access each glyph with its Adobe glyph name,\ne.g. `/quotedsingle' or `/Acircumflex'. This has been extended with ttf2tfm; now you can\n(and sometimes must) access the code points and/or glyphs directly, using the following syn‐\ntax for specifying the character position in decimal, octal, or hexadecimal notation:\n`/.c', `/.c0', or `/.c0x'. Examples:\n`/.c72', `/.c0646', `/.c0x48'. To access a glyph index directly, use the character `g' in‐\nstead of `c' in the just introduced notation. Example: `/.g0x32'. [Note: The `.cXXX' nota‐\ntion makes no sense if -N is used.]\n\nFor pid/eid pairs (1,0) and (3,1), both ttf2tfm and ttf2pk recognize built-in default Adobe\nglyph names; the former follows the names given in Appendix E of the book `Inside Macintosh',\nvolume 6, the latter uses the names given in the TrueType Specification (WGL4, a Unicode sub‐\nset). Note that Adobe names for a given glyph are often not unique and do sometimes differ,\ne.g., many PS fonts have the glyph `mu', whereas this glyph is called `mu1' in the WGL4 char‐\nacter set to distinguish it from the real Greek letter mu. Be also aware that OpenType (i.e.\nTrueType 2.0) fonts use an updated WGL4 table; we use the data from the latest published\nTrueType specification (1.66). You can find those mapping tables in the source code file\nttfenc.c.\n\nOn the other hand, the switches -n and -N makes ttf2tfm read in and use the PostScript names\nin the TrueType font itself (stored in the `post' table) instead of the default Adobe glyph\nnames.\n\nUse the -r switch to remap single glyph names and -R to specify a file containing replacement\nglyph name pairs.\n\nIf you don't select an input encoding, the first 256 glyphs of the TrueType font with a valid\nentry in the selected cmap will be mapped to the TeX raw font (without the -q option, ttf2tfm\nprints this mapping table to standard output), followed by all glyphs not yet addressed in\nthe selected cmap. However, some code points for the (1,0) pid/eid pair are omitted since\nthey do not represent glyphs useful for TeX: 0x00 (null), 0x08 (backspace), 0x09 (horizontal\ntabulation), 0x0d (carriage return), and 0x1d (group separator). The `invalid character'\nwith glyph index 0 will be omitted too.\n\nIf you select the -N switch, the first 256 glyphs of the TrueType font with a valid Post‐\nScript name will be used in case no input encoding is specified. Again, some glyphs are\nomitted: `.notdef', `.null', and `nonmarkingreturn'.\n\nIf you don't select an output encoding, ttf2tfm uses the same mapping table as afm2tfm would\nuse (you can find it in the source code file texenc.c); it corresponds to TeX typewriter\ntext. Unused positions (either caused by empty code points in the mapping table or missing\nglyphs in the TrueType font) will be filled (rather arbitrarily) with characters present in\nthe input encoding but not specified in the output encoding (without the -q option ttf2tfm\nprints the final output encoding to standard output). Use the -u option if you want only\nglyphs in the virtual font which are defined in the output encoding file, and nothing more.\n\nOne feature missing in afm2tfm has been added which is needed by LaTeX's T1 encoding: ttf2tfm\nwill construct the glyph `Germandbls' (by simply concatenating two `S' glyphs) even for nor‐\nmal fonts if possible. It appears in the glyph list as the last item, marked with an aster‐\nisk. Since this isn't a real glyph it will be available only in the virtual font.\n\nFor both input and output encoding, an empty code position is represented by the glyph name\n`/.notdef'.\n\nIn encoding files, you can use `\\' as the final character of a line to indicate that the in‐\nput is continued on the next line. The backslash and the following newline character will be\nremoved.\n", "subsections": [] }, "SUBFONT DEFINITION FILES": { "content": "CJKV (Chinese/Japanese/Korean/old Vietnamese) fonts usually contain several thousand glyphs;\nto use them with TeX it is necessary to split such large fonts into subfonts. Subfont defin‐\nition files (usually having the extension `.sfd') are a simple means to do this smoothly.\n\nA subfont file name usually consists of a prefix, a subfont infix, and a postfix (which is\nempty in most cases), e.g.\n\nntukai23 → prefix: ntukai, infix: 23, postfix: (empty)\n\nHere the syntax of a line in an SFD file, describing one subfont:\n\n \n\n\n :=\nanything except whitespace. It is best to use only alphanumerical characters.\n\n :=\nspace, formfeed, carriage return, horizontal and vertical tabs -- no newline charac‐\nters.\n\n :=\n |\n |\n \n\n :=\n\n\n :=\n `' \n\n :=\n `:'\n\n :=\nhexadecimal (prefix `0x'), decimal, or octal (prefix `0')\n\nA line can be continued on the next line with a backslash ending the line. The ranges must\nnot overlap; offsets have to be in the range 0-255.\n\nExample:\n\nThe line\n\n03 10: 0x2349 0x23450x2347\n\nassigns to the code positions 10, 11, 12, and 13 of the subfont having the infix `03' the\ncharacter codes 0x2349, 0x2345, 0x2346, and 0x2347 respectively.\n\nThe SFD files in the distribution are customized for the CJK package for LaTeX.\n\nYou have to embed the SFD file name into the TFM font name (at the place where the infix will\nappear) surrounded by two `@' signs, on the command line resp. a map file; both ttf2tfm and\nttf2pk switch then to subfont mode.\n\nIt is possible to use more than a single SFD file by separating them with commata and no\nwhitespace; for a given subfont, the first file is scanned for an entry, then the next file,\nand so on. Later entries override entries found earlier (possibly only partially). For ex‐\nample, the first SFD file sets up range 0x10-0xA0, and the next one modifies entries 0x12 and\n0x25. As can be easily seen, this algorithm allows for adding and replacing, but not for re‐\nmoving entries.\n\nSubfont mode disables the options -n, -N, -p, -r, -R, -t, -T, -u, -v, -V and -w for ttf2tfm;\nsimilarly, no `Encoding' or `Replacement' parameter is allowed in a map file. Single re‐\nplacement glyph names are ignored too.\n\nttf2tfm will create all subfont TFM files specified in the SFD files (provided the subfont\ncontains glyphs) in one run.\n\nExample:\n\nThe call\n\nttf2tfm ntukai.ttf ntukai@Big5,Big5-supp@\n\nwill use Big5.sfd and Big5-supp.sfd, producing all subfont files ntukai01.tfm,\nntukai02.tfm, etc.\n", "subsections": [] }, "RETURN VALUE": { "content": "ttf2tfm returns 0 on success and 1 on error; warning and error messages are written to stan‐\ndard error.\n", "subsections": [] }, "SOME NOTES ON FILE SEARCHING": { "content": "Both ttf2pk and ttf2tfm use either the kpathsea, emtexdir, or MiKTeX library for searching\nfiles (emtexdir will work only on operating systems which have an MS-DOSish background, i.e.\nMS-DOS, OS/2, Windows; MikTeX is specific to MS Windows).\n\nAs a last resort, both programs can be compiled without a search library; the searched files\nmust be then in the current directory or specified with a path. Default extensions will be\nappended also (with the exception that only `.ttf' is appended and not `.ttc').\n", "subsections": [ { "name": "kpathsea", "content": "The actual version of kpathsea is displayed on screen if you call either ttf2pk or ttf2tfm\nwith the --version command line switch.\n\nHere is a table of the file type and the corresponding kpathsea variables. TTF2PKINPUTS and\nTTF2TFMINPUTS are program specific environment variables introduced in kpathsea version 3.2:\n\n.ttf and .ttc TTFONTS\nttf2pk.cfg TTF2PKINPUTS\n.map TTF2PKINPUTS\n.enc TTF2PKINPUTS, TTF2TFMINPUTS\n.rpl TTF2PKINPUTS, TTF2TFMINPUTS\n.tfm TFMFONTS\n.sfd TTF2PKINPUTS, TTF2TFMINPUTS\n\n\nPlease consult the info files of kpathsea for details on these variables.\n\nYou should set the TEXMFCNF variable to the directory where your texmf.cnf configuration file\nresides.\n\nHere is the proper command to find out to which value a kpathsea variable is set (we use TT‐\nFONTS as an example). This is especially useful if a variable isn't set in texmf.cnf or in\nthe environment, thus pointing to the default value which is hard-coded into the kpathsea li‐\nbrary.\n\nkpsewhich -progname=ttf2tfm -expand-var='$TTFONTS'\n\nWe select the program name also since it is possible to specify variables which are searched\nonly for a certain program -- in our example it would be TTFONTS.ttf2tfm.\n\nA similar but not identical method is to say\n\nkpsewhich -progname=ttf2tfm -show-path='truetype fonts'\n\n[A full list of format types can be obtained by saying `kpsewhich --help' on the command line\nprompt.] This is exactly how ttf2tfm (and ttf2pk) searches for files; the disadvantage is\nthat all variables are expanded which can cause very long strings.\n" }, { "name": "emtexdir", "content": "Here the list of suffixes and their related environment variables to be set in autoexec.bat\n(resp. in config.sys for OS/2):\n\n.ttf and .ttc TTFONTS\nttf2pk.cfg TTFCFG\n.map TTFCFG\n.enc TTFCFG\n.rpl TTFCFG\n.tfm TEXTFM\n.sfd TTFCFG\n\nIf one of the variables isn't set, a warning message is emitted. The current directory will\nalways be searched. As usual, one exclamation mark appended to a directory path causes sub‐\ndirectories one level deep to be searched, two exclamation marks cause all subdirectories to\nbe searched. Example:\n\nTTFONTS=c:\\fonts\\truetype!!;d:\\myfonts\\truetype!\n\nConstructions like `c:\\fonts!!\\truetype' aren't possible.\n" }, { "name": "MiKTeX", "content": "Both ttf2tfm and ttf2pk have been fully integrated into MiKTeX. Please refer to the documen‐\ntation of MiKTeX for more details on file searching.\n" } ] }, "PROBLEMS": { "content": "Many vptovf implementations allow only 100 bytes for the TFM header (the limit is 1024 in the\nTFM file format itself): 8 bytes for checksum and design size, 40 bytes for the family name,\n20 bytes for the encoding, and 4 bytes for a face byte. There remain only 28 bytes for some\nadditional information which is used by ttf2tfm for an identification string (which is essen‐\ntially a copy of the command line), and this limit is always exceeded.\n\nThe optimal solution is to increase the value of maxheaderbytes in the file vptovf.web (and\nprobably pltotf.web too) to, say, 400 and recompile vptovf (and pltotf). Otherwise you'll\nget some (harmless) error messages like\n\nThis HEADER index is too big for my present table size\n\nwhich can be safely ignored.\n", "subsections": [] }, "SEE ALSO": { "content": "ttf2pk(1), afm2tfm(1), vptovf(1),\nthe info pages for dvips and kpathsea\n", "subsections": [] }, "AVAILABILITY": { "content": "ttf2tfm is part of the FreeType 1 package, a high quality TrueType rendering library.\n", "subsections": [] }, "AUTHORS": { "content": "Werner LEMBERG \nFrédéric LOYER \n\nFreeType2 version 27-Jun-2013 TTF2TFM(1)", "subsections": [] } }, "summary": "ttf2tfm - build TeX metric files from a TrueType font", "flags": [], "examples": [], "see_also": [ { "name": "ttf2pk", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/ttf2pk/1/json" }, { "name": "afm2tfm", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/afm2tfm/1/json" }, { "name": "vptovf", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/vptovf/1/json" } ] }