A Unicode bug in PDFs, cracked in an afternoon instead of a week
Unicode characters were rendering wrong in PDFs. Claude Code raced through several approaches in an afternoon to find each one's limits, ending in a custom font fallback. Then a day of polish.
Done withClaude CodeSpotted· by HN user epiccoleman· Oct 15, 2026
Time saved
About a week of dev time
Result
Fixed with a custom font fallback
“iterate through several potential approaches and find the gaps and limitations within the space of an afternoon”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
Debugged PDF rendering issue with Unicode characters; iterated through multiple potential approaches with Claude’s help; implemented custom font fallback system.
How it went
Took about a day of tweaking/testing/cleaning after initial work; Claude’s rapid iteration through approaches was valuable.
Try it yourself with Claude Code
I'm getting Unicode character rendering issues in PDFs with [library]. The issue: [describe problem]. Suggest multiple approaches to solve this: font fallback systems, character encoding fixes, library alternatives. For each approach, show sample code. I'll iterate through them.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
Markdown files should just open, so they asked Claude Code for a viewer. It opens instantly: faster, they say, than any other macOS app, and faster than Bitwarden's Chrome extension shows its fill menu.
Migrating a password reset flow, Claude Code and Opus produced code on par with a mid level developer. It needed close supervision throughout, and cost roughly 2 months of Pro subscription for about half a day's work.
A URL shortener side project ran on AWS. Claude Code wrote the GitHub Actions workflows for the move and fixed each failure as it came up. The writer reports zero downtime.
A 7-app monorepo needed an 8 GB memory setting and 25 seconds to typecheck. Claude Code made the changes for the move to oxlint, oxfmt and tsgo, and the team validated each step.
Turning plan files into Claude Code workflows took 5-6 hours each. A script that converts them deterministically, and flags what can move out of the LLM, cut that to 20-30 minutes at about 20% of the tokens.
An inherited app on Azure, an error, and a hunt that could easily take 1-2 days by hand. With CLI access to Azure and the repo, Claude Code ran the config and network checks and found the root cause in about 45 minutes.