diff options
author | Joey Hess <joey@kitenet.net> | 2011-03-12 15:30:17 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-03-12 15:30:17 -0400 |
commit | 72d268401604fbac93ca4701ab53d32880483686 (patch) | |
tree | a1ab880d30ece5ed1720d6db13ab5d9c5c1ca560 /doc/bugs/problems_with_utf8_names.mdwn | |
parent | 9229d182d32570f6829ced655aa673ceddfe7693 (diff) |
Rethink filename encoding handling for display. Since filename encoding may or may not match locale settings, any attempt to decode filenames will fail for some files. So instead, do all output in binary mode.0.23
Diffstat (limited to 'doc/bugs/problems_with_utf8_names.mdwn')
-rw-r--r-- | doc/bugs/problems_with_utf8_names.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/problems_with_utf8_names.mdwn b/doc/bugs/problems_with_utf8_names.mdwn index efde1c9a3..d6dc6ca3c 100644 --- a/doc/bugs/problems_with_utf8_names.mdwn +++ b/doc/bugs/problems_with_utf8_names.mdwn @@ -63,6 +63,9 @@ It looks like the common latin1-to-UTF8 encoding. Functionality other than otupu > One other possible > issue would be that this could cause problems if git-annex were > translated. +> > On second thought, I switched to this. Any decoding of a filename +> > is going to make someone unhappy; the previous approach broke +> > non-utf8 filenames. ---- |