diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-02-10 14:45:35 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-02-10 14:45:35 -0400 |
| commit | 52fa424faef63690d5b44cc4b6fd11aa67f1e619 (patch) | |
| tree | c8c217dcfce2ea2cf7f864cf032a1d938945620a | |
| parent | 467af5ba8015105a61d3cb38cd7bfd178c95760b (diff) | |
update
| -rw-r--r-- | doc/bugs/problems_with_utf8_names.mdwn | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/bugs/problems_with_utf8_names.mdwn b/doc/bugs/problems_with_utf8_names.mdwn index 257f8dff2..58eb5ad1c 100644 --- a/doc/bugs/problems_with_utf8_names.mdwn +++ b/doc/bugs/problems_with_utf8_names.mdwn @@ -58,7 +58,8 @@ It looks like the common latin1-to-UTF8 encoding. Functionality other than otupu > filename would be displayed, which should work ok. git-annex does > not really need to pull apart filenames; they are almost entirely > opaque blobs. I guess that the `--exclude` option is the exception -> to that, but it is currently not unicode safe anyway. +> to that, but it is currently not unicode safe anyway. (Update: tried +> `--exclude` again, seems it is unicode clean..) > One other possible > issue would be that this could cause problems if git-annex were > translated. |