Mor1arty fixes Mike's Chinese filename problem

A tiny upload patch that quietly matters for any firm handling non-English documents.

i18ninfrastructure

When you upload a file to Mike, the server reads the filename using an old text-encoding convention that mangles anything that isn't plain English letters. Chinese characters, accented names, Cyrillic, Arabic - all turn to garbage by the time the file is stored. Mor1arty, who appears to be running Mike against Chinese-language documents, has applied the standard fix: re-read the filename in the modern encoding the rest of the world uses, so the original name survives intact.

It's a ten-line change, low-risk, and a no-op for English-only users. But it points at a real gap in the upstream project - any deployment touching documents named in a non-Latin script has been silently losing that information. For a legal tool, where the filename is often the only human-readable handle on an exhibit, that's not a cosmetic issue.

So what Anyone running Mike against multilingual document sets - cross-border practices, immigration work, anything outside an English-only firm - should pull this in.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from Mor1arty/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
9a3e93bf fix: support uploading file who involves Chinese content Moriarty 2026-05-15 ↗ GitHub
533a4ed9 Merge pull request #1 from Mor1arty/feature/CN-file-support Mor1arty 2026-05-15 ↗ GitHub
fix: support uploading file who involves Chinese content

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-439.md from inside the repo you want the changes in.

⬇ Download capture-thread-439.md