[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"i-lucide:grip":3,"i-lucide:chevron-right":8,"i-lucide:moon":10,"i-lucide:sun":12,"i-lucide:languages":14,"i-lucide:chevron-down":16,"i-lucide:shield-check":18,"i-lucide:mail":20,"blog-body-latex-chinese-font-setup-en":22,"i-lucide:lightbulb":23,"i-lucide:graduation-cap":25,"i-lucide:pen-line":27,"i-lucide:star":29},{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":7},0,24,false,"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Ccircle cx=\"12\" cy=\"5\" r=\"1\"\u002F>\u003Ccircle cx=\"19\" cy=\"5\" r=\"1\"\u002F>\u003Ccircle cx=\"5\" cy=\"5\" r=\"1\"\u002F>\u003Ccircle cx=\"12\" cy=\"12\" r=\"1\"\u002F>\u003Ccircle cx=\"19\" cy=\"12\" r=\"1\"\u002F>\u003Ccircle cx=\"5\" cy=\"12\" r=\"1\"\u002F>\u003Ccircle cx=\"12\" cy=\"19\" r=\"1\"\u002F>\u003Ccircle cx=\"19\" cy=\"19\" r=\"1\"\u002F>\u003Ccircle cx=\"5\" cy=\"19\" r=\"1\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":9},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m9 18l6-6l-6-6\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":11},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M20.985 12.486a9 9 0 1 1-9.473-9.472c.405-.022.617.46.402.803a6 6 0 0 0 8.268 8.268c.344-.215.825-.004.803.401\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":13},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"4\"\u002F>\u003Cpath d=\"M12 2v2m0 16v2M4.93 4.93l1.41 1.41m11.32 11.32l1.41 1.41M2 12h2m16 0h2M6.34 17.66l-1.41 1.41M19.07 4.93l-1.41 1.41\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":15},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m5 8l6 6m-7 0l6-6l2-3M2 5h12M7 2h1m14 20l-5-10l-5 10m2-4h6\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":17},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"m6 9l6 6l6-6\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":19},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"M20 13c0 5-3.5 7.5-7.66 8.95a1 1 0 0 1-.67-.01C7.5 20.5 4 18 4 13V6a1 1 0 0 1 1-1c2 0 4.5-1.2 6.24-2.72a1.17 1.17 0 0 1 1.52 0C14.51 3.81 17 5 19 5a1 1 0 0 1 1 1z\"\u002F>\u003Cpath d=\"m9 12l2 2l4-4\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":21},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"m22 7l-8.991 5.727a2 2 0 0 1-2.009 0L2 7\"\u002F>\u003Crect width=\"20\" height=\"16\" x=\"2\" y=\"4\" rx=\"2\"\u002F>\u003C\u002Fg>","\u003Cblockquote>\n\u003Cp>CJK errors in LaTeX look wildly varied — blank output, garbled glyphs, \u003Ccode>font not found\u003C\u002Fcode>, \u003Ccode>ctexart.cls not found\u003C\u002Fcode> — but they usually trace back to one thing: \u003Cstrong>the wrong engine\u003C\u002Fstrong>. Understand how pdfLaTeX differs from XeLaTeX and most of them disappear on their own.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cimg src=\"\u002Fblog\u002Flatex-chinese-font-setup\u002Fcover.webp\" alt=\"pdfLaTeX's font box cannot hold thousands of Han characters; XeLaTeX reaches straight for system fonts\">\u003C\u002Fp>\n\u003Ch2>Why the same source works for someone else but not for you\u003C\u002Fh2>\n\u003Cp>Because you're compiling with different engines. This is the biggest knowledge gap in CJK LaTeX: \u003Cstrong>the same \u003Ccode>.tex\u003C\u002Fcode> file compiled with \u003Ccode>pdflatex\u003C\u002Fcode> and with \u003Ccode>xelatex\u003C\u002Fcode> takes two completely different font paths.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>pdfLaTeX inherits from 1980s TeX and uses the \u003Cstrong>8-bit font model\u003C\u002Fstrong>, where one font file supplies at most 256 glyphs. That's ample for the Latin alphabet, but common Chinese alone runs to several thousand characters and simply doesn't fit. The historical workaround (the CJK package) \u003Cstrong>split Han characters across dozens of 256-glyph subfonts\u003C\u002Fstrong> and stitched them back together. It worked, but configuration was fiddly, font switching was error-prone, and any font nobody had pre-processed was out of reach.\u003C\u002Fp>\n\u003Cp>XeLaTeX and LuaLaTeX are later rewrites with native Unicode support that can \u003Cstrong>call OpenType and TrueType fonts installed on the operating system directly\u003C\u002Fstrong>. To them Chinese is no different from English: a Unicode code point and a glyph. So the modern answer fits in one line: \u003Cstrong>compile with xelatex and load ctex.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch2>How the three engines handle Chinese\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Engine\u003C\u002Fth>\n\u003Cth>Font source\u003C\u002Fth>\n\u003Cth>CJK approach\u003C\u002Fth>\n\u003Cth>Still worth using?\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>pdfLaTeX\u003C\u002Ftd>\n\u003Ctd>TeX-specific 8-bit fonts (TFM\u002FType1)\u003C\u002Ftd>\n\u003Ctd>CJK \u002F CJKutf8, needs subfont splitting\u003C\u002Ftd>\n\u003Ctd>Not recommended, legacy templates only\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>XeLaTeX\u003C\u002Ftd>\n\u003Ctd>System OpenType\u002FTrueType\u003C\u002Ftd>\n\u003Ctd>xeCJK (what ctex uses by default)\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Recommended\u003C\u002Fstrong> — the most mature CJK ecosystem\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>LuaLaTeX\u003C\u002Ftd>\n\u003Ctd>System fonts, plus Lua scripting\u003C\u002Ftd>\n\u003Ctd>luatexja\u003C\u002Ftd>\n\u003Ctd>Viable; slower to compile, more programmable\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>If a template you found online insists on \u003Ccode>pdflatex\u003C\u002Fcode> and you need to add Chinese, the cheapest fix is usually not to rework the font configuration but to \u003Cstrong>compile the same document with xelatex instead\u003C\u002Fstrong>. Most ordinary templates run fine after the switch.\u003C\u002Fp>\n\u003Ch2>Changing the compile command\u003C\u002Fh2>\n\u003Cp>On the command line, just change the program:\u003C\u002Fp>\n\u003Cpre class=\"shiki shiki-themes github-light github-dark mac-code-block\" style=\"background-color:#fff;--shiki-dark-bg:#24292e;color:#24292e;--shiki-dark:#e1e4e8\" tabindex=\"0\">\u003Cspan class=\"mac-lang-badge\">bash\u003C\u002Fspan>\u003Ccode class=\"language-bash\">\u003Cspan class=\"line\">\u003Cspan style=\"color:#6F42C1;--shiki-dark:#B392F0\">xelatex\u003C\u002Fspan>\u003Cspan style=\"color:#032F62;--shiki-dark:#9ECBFF\"> main.tex\u003C\u002Fspan>\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>In an editor you have to change the default build chain, which is the step people most often miss:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>VS Code + LaTeX Workshop\u003C\u002Fstrong>: point \u003Ccode>latex-workshop.latex.recipe.default\u003C\u002Fcode> at a recipe that runs xelatex, or more simply put a magic comment on line one of the file: \u003Ccode>% !TEX program = xelatex\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>TeXstudio\u003C\u002Fstrong>: Options → Configure → Build, set "Default Compiler" to XeLaTeX.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>latexmk\u003C\u002Fstrong>: pass the flag, \u003Ccode>latexmk -xelatex main.tex\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Afterwards, delete the \u003Ccode>.aux\u003C\u002Fcode>, \u003Ccode>.fls\u003C\u002Fcode> and other intermediates left by pdfLaTeX. Stale caches from a different engine occasionally produce errors that make no sense.\u003C\u002Fp>\n\u003Ch2>What ctex's fontset actually selects\u003C\u002Fh2>\n\u003Cp>\u003Ccode>fontset\u003C\u002Fcode> picks \u003Cstrong>an entire mapping of Chinese font roles\u003C\u002Fstrong> — which concrete font on your machine plays Song, Hei, Kai and Fangsong. You write it like this:\u003C\u002Fp>\n\u003Cpre class=\"shiki shiki-themes github-light github-dark mac-code-block\" style=\"background-color:#fff;--shiki-dark-bg:#24292e;color:#24292e;--shiki-dark:#e1e4e8\" tabindex=\"0\">\u003Cspan class=\"mac-lang-badge\">latex\u003C\u002Fspan>\u003Ccode class=\"language-latex\">\u003Cspan class=\"line\">\u003Cspan style=\"color:#D73A49;--shiki-dark:#F97583\">\\documentclass\u003C\u002Fspan>\u003Cspan style=\"color:#24292E;--shiki-dark:#E1E4E8\">{\u003C\u002Fspan>\u003Cspan style=\"color:#005CC5;--shiki-dark:#79B8FF\">ctexart\u003C\u002Fspan>\u003Cspan style=\"color:#24292E;--shiki-dark:#E1E4E8\">}\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#D73A49;--shiki-dark:#F97583\">\\usepackage\u003C\u002Fspan>\u003Cspan style=\"color:#24292E;--shiki-dark:#E1E4E8\">[fontset=fandol]{\u003C\u002Fspan>\u003Cspan style=\"color:#005CC5;--shiki-dark:#79B8FF\">ctex\u003C\u002Fspan>\u003Cspan style=\"color:#24292E;--shiki-dark:#E1E4E8\">}\u003C\u002Fspan>\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The common values and what each one costs you:\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>fontset\u003C\u002Fth>\n\u003Cth>Fonts used\u003C\u002Fth>\n\u003Cth>Requires\u003C\u002Fth>\n\u003Cth>Best for\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>windows\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>SimSun \u002F SimHei \u002F KaiTi and friends\u003C\u002Ftd>\n\u003Ctd>Windows, with those fonts installed\u003C\u002Ftd>\n\u003Ctd>Compiling only on your own Windows box\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>mac\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>STSong family \u002F PingFang\u003C\u002Ftd>\n\u003Ctd>macOS\u003C\u002Ftd>\n\u003Ctd>Compiling only on a Mac\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>ubuntu\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>WenQuanYi and other open fonts\u003C\u002Ftd>\n\u003Ctd>The matching font packages installed\u003C\u002Ftd>\n\u003Ctd>Linux desktops\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>fandol\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Fandol open-source fonts\u003C\u002Ftd>\n\u003Ctd>Ships with TeX Live, no system fonts needed\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Cross-machine, submissions, CI\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>none\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>No preset at all\u003C\u002Ftd>\n\u003Ctd>You specify everything via fontspec\u003C\u002Ftd>\n\u003Ctd>Journal templates that mandate fonts\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>Omit \u003Ccode>fontset\u003C\u002Fcode> and ctex tries to detect the operating system. Convenient on your own machine — and exactly why \u003Cstrong>"it compiles here but breaks on my co-author's laptop"\u003C\u002Fstrong> happens so often.\u003C\u002Fp>\n\u003Ch2>What font not found really means\u003C\u002Fh2>\n\u003Cp>fontspec resolves fonts by \u003Cstrong>the name the operating system knows\u003C\u002Fstrong>, not by a file inside the TeX tree. When you write \u003Ccode>fontset=windows\u003C\u002Fcode>, ctex is effectively asking the OS "do you have a font called SimSun?" Windows does; a Linux server or a GitHub Actions runner does not, so the build fails.\u003C\u002Fp>\n\u003Cp>These errors typically show up as the engine complaining that it can't resolve a font name, or that a font file doesn't exist. The diagnostic is straightforward: \u003Cstrong>check whether the name it printed is a system font name.\u003C\u002Fstrong> If it is, the problem is that this machine doesn't have it — not that your LaTeX is wrong.\u003C\u002Fp>\n\u003Cp>Hence one practical rule: \u003Cstrong>anything you'll send to someone else, submit to a journal, or build in CI should use \u003Ccode>fontset=fandol\u003C\u002Fcode>.\u003C\u002Fstrong> Fandol is an open-source Chinese font distributed with TeX Live, so it depends on no system fonts and produces the same output on any machine. For local drafts, system fonts often look nicer and are perfectly fine.\u003C\u002Fp>\n\u003Ch2>ctexart.cls not found is a different problem\u003C\u002Fh2>\n\u003Cp>\u003Ccode>ctexart.cls not found\u003C\u002Fcode> has nothing to do with fonts — \u003Cstrong>your distribution is incomplete\u003C\u002Fstrong>. TeX Live installs by scheme: \u003Ccode>scheme-basic\u003C\u002Fcode> and \u003Ccode>scheme-small\u003C\u002Fcode> are compact but exclude ctex, while \u003Ccode>scheme-full\u003C\u002Fcode> includes everything. Plenty of people install a slim scheme to save disk and hit this the first time they write Chinese.\u003C\u002Fp>\n\u003Cp>Install the missing package:\u003C\u002Fp>\n\u003Cpre class=\"shiki shiki-themes github-light github-dark mac-code-block\" style=\"background-color:#fff;--shiki-dark-bg:#24292e;color:#24292e;--shiki-dark:#e1e4e8\" tabindex=\"0\">\u003Cspan class=\"mac-lang-badge\">bash\u003C\u002Fspan>\u003Ccode class=\"language-bash\">\u003Cspan class=\"line\">\u003Cspan style=\"color:#6F42C1;--shiki-dark:#B392F0\">tlmgr\u003C\u002Fspan>\u003Cspan style=\"color:#032F62;--shiki-dark:#9ECBFF\"> install\u003C\u002Fspan>\u003Cspan style=\"color:#032F62;--shiki-dark:#9ECBFF\"> ctex\u003C\u002Fspan>\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The same goes for \u003Ccode>xecjk\u003C\u002Fcode>, \u003Ccode>zhnumber\u003C\u002Fcode>, \u003Ccode>fandol\u003C\u002Fcode> and \u003Ccode>cjkpunct\u003C\u002Fcode>, the usual dependencies along the CJK chain. Worth noting that \u003Ccode>fontspec\u003C\u002Fcode> is a hard dependency of xeCJK; if even that is absent, your installation is trimmed hard enough that moving to a fuller scheme beats patching packages one by one.\u003C\u002Fp>\n\u003Cp>When you'd rather not manage that dependency chain locally, the browser can run it: the advanced mode of the \u003Ca href=\"\u002Flatex\u002Fedit\u002F\">online LaTeX editor\u003C\u002Fa> is XeLaTeX compiled to WebAssembly with ctex, xeCJK and the Fandol fonts already bundled, so a \u003Ccode>\\documentclass{ctexart}\u003C\u002Fcode> file compiles as soon as you drop it in — no scheme selection, no package hunting.\u003C\u002Fp>\n\u003Ch2>Boundaries: what switching engines won't fix\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Rare characters with no glyph.\u003C\u002Fstrong> Fandol covers common Han characters, roughly the GB 2312 range. Classical variants, unusual characters in personal names, and some traditional forms may have no glyph and render as blanks or boxes. For those you need a font with wider coverage, such as Source Han Serif, set explicitly via \u003Ccode>\\setCJKmainfont\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Journal templates that mandate fonts.\u003C\u002Fstrong> Many Chinese journal \u003Ccode>.cls\u003C\u002Fcode> files hard-code their own font configuration, and adding a ctex fontset on top can conflict. Follow the template's documentation rather than overriding it.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Fine spacing in mixed CJK\u002FLatin text.\u003C\u002Fstrong> xeCJK inserts a small gap between Chinese and Western characters by default, which is right most of the time but occasionally needs a \u003Ccode>\\xeCJKsetup\u003C\u002Fcode> tweak in formula-dense paragraphs. That's polish, not a blocker.\u003C\u002Fp>\n\u003Ch2>Summary\u003C\u002Fh2>\n\u003Cp>Debug CJK LaTeX in a fixed order: \u003Cstrong>confirm the engine is xelatex, confirm ctex is installed, and only then check whether the fontset is right.\u003C\u002Fstrong> Those three steps locate nearly every "my Chinese won't render" problem. Use \u003Ccode>fontset=fandol\u003C\u002Fcode> for anything leaving your machine, and you'll skip a lot of future arguing about whose laptop it compiles on.\u003C\u002Fp>\n",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":24},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M15 14c.2-1 .7-1.7 1.5-2.5c1-.9 1.5-2.2 1.5-3.5A6 6 0 0 0 6 8c0 1 .2 2.2 1.5 3.5c.7.7 1.3 1.5 1.5 2.5m0 4h6m-5 4h4\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":26},"\u003Cg fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\">\u003Cpath d=\"M21.42 10.922a1 1 0 0 0-.019-1.838L12.83 5.18a2 2 0 0 0-1.66 0L2.6 9.08a1 1 0 0 0 0 1.832l8.57 3.908a2 2 0 0 0 1.66 0zM22 10v6\"\u002F>\u003Cpath d=\"M6 12.5V16a6 3 0 0 0 12 0v-3.5\"\u002F>\u003C\u002Fg>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":28},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M13 21h8m.174-14.188a1 1 0 0 0-3.986-3.987L3.842 16.174a2 2 0 0 0-.5.83l-1.321 4.352a.5.5 0 0 0 .623.622l4.353-1.32a2 2 0 0 0 .83-.497z\"\u002F>",{"left":4,"top":4,"width":5,"height":5,"rotate":4,"vFlip":6,"hFlip":6,"body":30},"\u003Cpath fill=\"none\" stroke=\"currentColor\" stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M11.525 2.295a.53.53 0 0 1 .95 0l2.31 4.679a2.12 2.12 0 0 0 1.595 1.16l5.166.756a.53.53 0 0 1 .294.904l-3.736 3.638a2.12 2.12 0 0 0-.611 1.878l.882 5.14a.53.53 0 0 1-.771.56l-4.618-2.428a2.12 2.12 0 0 0-1.973 0L6.396 21.01a.53.53 0 0 1-.77-.56l.881-5.139a2.12 2.12 0 0 0-.611-1.879L2.16 9.795a.53.53 0 0 1 .294-.906l5.165-.755a2.12 2.12 0 0 0 1.597-1.16z\"\u002F>",1786455162090]