[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBPYC2HQCXZQJQMDXEQFX4":3,"skill-same:01M6XBPYC2HQCXZQJQMDXEQFX4":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":13,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6XBPYC2HQCXZQJQMDXEQFX4","pandoc-unicode-workaround",null,"Handle LaTeX Unicode errors in pandoc PDF generation by normalizing special characters to ASCII","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fpandoc-unicode-workaround\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32],"pandoc","Unicode","pandoc unicode workaround","PDF","LaTeX","generation","ascii","pdf generation","errors","characters","2026-11-10 10:12:30",false,"---\nname: pandoc-unicode-workaround\ndescription: Handle LaTeX Unicode errors in pandoc PDF generation by normalizing special characters to ASCII\n---\n\n# Pandoc Unicode Workaround\n\nThis skill provides a workflow for generating PDFs from Markdown using pandoc when LaTeX compilation fails due to Unicode character errors.\n\n## When to Use\n\nUse this skill when:\n- `pandoc document.md -o document.pdf` fails with LaTeX\u002FUnicode errors\n- Error messages mention \"Unicode character\", \"LaTeX Error\", or specific characters like ✓, →, —, etc.\n- You need to produce PDF output but pandoc's default LaTeX engine cannot handle special characters\n\n## Step-by-Step Procedure\n\n### Step 1: Attempt Initial PDF Generation\n\n```bash\npandoc input.md -o output.pdf\n```\n\nIf this succeeds, you're done. If it fails with Unicode\u002FLaTeX errors, proceed to Step 2.\n\n### Step 2: Normalize Unicode Characters\n\nReplace problematic Unicode characters with ASCII equivalents. Common replacements:\n\n| Unicode Character | ASCII Replacement | Alternative |\n|-------------------|-------------------|-------------|\n| ✓ (checkmark)     | [Y] or [X]        | OK, ✓ removed |\n| ✗ or ✘ (cross)    | [N]               | FAIL |\n| → (arrow right)   | ->                | => |\n| ← (arrow left)    | \u003C-                | |\n| — (em dash)       | -- or -           | --- |\n| – (en dash)       | -                 | |\n| • (bullet)        | -                 | * |\n| © (copyright)     | (c)               | Copyright |\n| ® (registered)    | (R)               | |\n| ™ (trademark)     | (TM)              | |\n| … (ellipsis)      | ...               | |\n| \" (smart quotes)  | \" or '            | |\n\n### Step 3: Apply Replacements\n\nOption A - Manual edit:\nOpen the Markdown file and manually replace the characters using find\u002Freplace.\n\nOption B - Automated with sed (Linux\u002FMac):\n```bash\nsed -i 's\u002F✓\u002F[Y]\u002Fg' input.md\nsed -i 's\u002F✗\u002F[N]\u002Fg' input.md\nsed -i 's\u002F→\u002F->\u002Fg' input.md\nsed -i 's\u002F—\u002F--\u002Fg' input.md\n```\n\nOption C - Automated with Python:\n```python\nreplacements = {\n    '✓': '[Y]',\n    '✗': '[N]',\n    '→': '->',\n    '—': '--',\n    '–': '-',\n    '…': '...',\n    '\"': '\"',\n    '\"': '\"',\n}\n\nwith open('input.md', 'r', encoding='utf-8') as f:\n    content = f.read()\n\nfor orig, repl in replacements.items():\n    content = content.replace(orig, repl)\n\nwith open('input.md', 'w', encoding='utf-8') as f:\n    f.write(content)\n```\n\n### Step 4: Regenerate PDF\n\n```bash\npandoc input.md -o output.pdf\n```\n\n### Step 5: Verify Output\n\nCheck that the PDF was generated successfully and review the content to ensure character replacements are acceptable for your use case.\n\n## Alternative Approaches\n\nIf Unicode normalization is not acceptable:\n\n1. Use a different PDF engine:\n   ```bash\n   pandoc input.md -o output.pdf --pdf-engine=wkhtmltopdf\n   ```\n\n2. Use XeLaTeX (better Unicode support):\n   ```bash\n   pandoc input.md -o output.pdf --pdf-engine=xelatex\n   ```\n\n3. Add LaTeX packages for Unicode:\n   ```bash\n   pandoc input.md -o output.pdf -H header.tex\n   ```\n   Where header.tex contains:\n   ```latex\n   \\usepackage{fontspec}\n   \\usepackage{xunicode}\n   ```\n\n## Tips\n\n- Keep the original Markdown file before normalization if you need to preserve characters\n- Document which characters were replaced for future reference\n- Test with a small sample first if working with large documents\n- For Word documents (.docx), Unicode issues are less common; this pattern is primarily for PDF generation\n\n## Error Indicators\n\nCommon LaTeX Unicode errors to watch for:\n- ! LaTeX Error: Unicode character ... not set up for use with LaTeX\n- Package inputenc Error: Unicode character ... not set up\n- ! Missing character: There is no ... in font ...","# Pandoc Unicode Workaround\n\nThis skill provides a workflow for generating PDFs from Markdown using pandoc when LaTeX compilation fails due to Unicode character errors.\n\n## When to Use\n\nUse this skill when:\n- `pandoc document.md -o document.pdf` fails with LaTeX\u002FUnicode errors\n- Error messages mention \"Unicode character\", \"LaTeX Error\", or specific characters like ✓, →, —, etc.\n- You need to produce PDF output but pandoc's default LaTeX engine cannot handle special characters\n\n## Step-by-Step Procedure\n\n### Step 1: Attempt Initial PDF Generation\n\n```bash\npandoc input.md -o output.pdf\n```\n\nIf this succeeds, you're done. If it fails with Unicode\u002FLaTeX errors, proceed to Step 2.\n\n### Step 2: Normalize Unicode Characters\n\nReplace problematic Unicode characters with ASCII equivalents. Common replacements:\n\n| Unicode Character | ASCII Replacement | Alternative |\n|-------------------|-------------------|-------------|\n| ✓ (checkmark)     | [Y] or [X]        | OK, ✓ removed |\n| ✗ or ✘ (cross)    | [N]               | FAIL |\n| → (arrow right)   | ->                | => |\n| ← (arrow left)    | \u003C-                | |\n| — (em dash)       | -- or -           | --- |\n| – (en dash)       | -                 | |\n| • (bullet)        | -                 | * |\n| © (copyright)     | (c)               | Copyright |\n| ® (registered)    | (R)               | |\n| ™ (trademark)     | (TM)              | |\n| … (ellipsis)      | ...               | |\n| \" (smart quotes)  | \" or '            | |\n\n### Step 3: Apply Replacements\n\nOption A - Manual edit:\nOpen the Markdown file and manually replace the characters using find\u002Freplace.\n\nOption B - Automated with sed (Linux\u002FMac):\n```bash\nsed -i 's\u002F✓\u002F[Y]\u002Fg' input.md\nsed -i 's\u002F✗\u002F[N]\u002Fg' input.md\nsed -i 's\u002F→\u002F->\u002Fg' input.md\nsed -i 's\u002F—\u002F--\u002Fg' input.md\n```\n\nOption C - Automated with Python:\n```python\nreplacements = {\n    '✓': '[Y]',\n    '✗': '[N]',\n    '→': '->',\n    '—': '--',\n    '–': '-',\n    '…': '...',\n    '\"': '\"',\n    '\"': '\"',\n}\n\nwith open('input.md', 'r', encoding='utf-8') as f:\n    content = f.read()\n\nfor orig, repl in replacements.items():\n    content = content.replace(orig, repl)\n\nwith open('input.md', 'w', encoding='utf-8') as f:\n    f.write(content)\n```\n\n### Step 4: Regenerate PDF\n\n```bash\npandoc input.md -o output.pdf\n```\n\n### Step 5: Verify Output\n\nCheck that the PDF was generated successfully and review the content to ensure character replacements are acceptable for your use case.\n\n## Alternative Approaches\n\nIf Unicode normalization is not acceptable:\n\n1. Use a different PDF engine:\n   ```bash\n   pandoc input.md -o output.pdf --pdf-engine=wkhtmltopdf\n   ```\n\n2. Use XeLaTeX (better Unicode support):\n   ```bash\n   pandoc input.md -o output.pdf --pdf-engine=xelatex\n   ```\n\n3. Add LaTeX packages for Unicode:\n   ```bash\n   pandoc input.md -o output.pdf -H header.tex\n   ```\n   Where header.tex contains:\n   ```latex\n   \\usepackage{fontspec}\n   \\usepackage{xunicode}\n   ```\n\n## Tips\n\n- Keep the original Markdown file before normalization if you need to preserve characters\n- Document which characters were replaced for future reference\n- Test with a small sample first if working with large documents\n- For Word documents (.docx), Unicode issues are less common; this pattern is primarily for PDF generation\n\n## Error Indicators\n\nCommon LaTeX Unicode errors to watch for:\n- ! LaTeX Error: Unicode character ... not set up for use with LaTeX\n- Package inputenc Error: Unicode character ... not set up\n- ! Missing character: There is no ... in font ...",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fpandoc-unicode-workaround","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill pandoc-unicode-workaround",{"tool":50,"command":51},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill pandoc-unicode-workaround",{"tool":53,"command":54},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill pandoc-unicode-workaround","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fpandoc-unicode-workaround\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},".skill_id","OTHER","其他",39,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fpandoc-unicode-workaround\u002F.skill_id",[65,88,105,114,144,160],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":33},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[72,73,74,75,76,32,77,78,79,31,80,81,82,83,84,85,86,87],"check","write","write special chars ts check","typescript","filters","Existing","type-checking","for","script","output","type","files","only","template","file","python",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":33},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[95,96,73,86,97,87,98,99,100,101,102,85,103,104,32,79,80],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":33},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[112,73,32,113,80,99,85,86,87,79],"write special chars heredoc","shell",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":33},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[126,127,128,129,130,75,131,132,133,134,135,79,136,137,138,139,140,141,142,143],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":33},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[151,152,153,154,79,155,104,156,157,158,159],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":33},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[167,168,169,170,171,172,86,173,174,175],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]