Mor1arty stops the uploader from scrambling non-English filenames

A small patch fixes a bug that quietly corrupted any uploaded file whose name used characters outside the basic English alphabet.

i18nintake

When a user uploads a document, the file-handling layer in many web apps reads the filename using an old text encoding that only understands plain English letters and numbers. Anything outside that range - accented European characters, Chinese, Arabic, and so on - gets garbled before the application ever stores or displays it. Mor1arty's change catches the mangled name, reconstructs the original characters, and hands the app the real filename. Plain English filenames are untouched, so nothing else changes.

It's a narrow fix - one file, a handful of lines - but it closes a gap that would bite any firm whose clients and matters don't live entirely in English.

So what Worth a look for anyone running a legal-AI tool for non-English-speaking clients, where a document called 估值报告.pdf shouldn't land in the system as gibberish.

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

⬇ Download capture-thread-447.md