Mor1arty stops Mike from mangling non-English filenames

Upload a document named in Chinese, Japanese, or Korean and Mike used to scramble the name on the way in - Mor1arty fixed it.

intakei18n

When you uploaded a file, Mike read the filename using a character set that only understands Western European letters. Anything outside that - Chinese, Japanese, Korean, and many other scripts - came through as garbled nonsense, so a carefully named exhibit or contract landed in the system as gibberish. Mor1arty's patch re-reads the incoming filename correctly, so multibyte names survive intact.

It's a small, surgical change: English-only filenames behave exactly as before, and nothing else in the upload path moves. But for any team handling documents named in a non-Latin script, it's the difference between a clean intake and a folder full of unreadable file names.

So what Worth a look for anyone running Mike in a market where documents arrive with names in Chinese, Japanese, Korean, or other non-Western scripts.

View this fork on GitHub →

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

Commits in this thread

1 commit 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

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-481.md from inside the repo you want the changes in.

⬇ Download capture-thread-481.md