Using precomposeunicode still reproduces the issue:
Repro steps:
1. Download https://www.dropbox.com/s/0q5pbpqpckwzj7b/gitstatusrepro.zip?dl=0
2. unzip gitstatusrepro.zip && cd gitstatusrepro
3. git reset --hard
4. git -c core.precomposeunicode=true status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
"d\314\207\316\271\314\223\314\200\342\225\223\316\265\357\256\257\360\222\221\217\342\227\213\342\225\223\320\243\314\213/"
nothing added to commit but untracked files present (use "git add" to track)
From: Torsten Bögershausen <redacted>
Thanks for the fast analyzes -
in short:
what does
git -c core.precomposeunicode=true status
say ?
The easiest thing may be to set
git config --global core.precomposeunicode true