mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update

Browse source
This commit is contained in:
Joey Hess 2012-02-02 10:56:39 -04:00
parent 39e887e8e6
commit fc8a1d213b
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/bugs/problems_with_utf8_names.mdwn
View file

@ -3,6 +3,12 @@ This bug is reopened to track some new UTF-8 filename issues caused by GHC
encoding no longer works. Even unicode filenames fail to work when encoding no longer works. Even unicode filenames fail to work when
git-annex is built with 7.4. --[[Joey]] git-annex is built with 7.4. --[[Joey]]
> What's going on exactly? The new ghc, when presented with
> a String of raw bytes like "fo\194\161", and asked to do
> something like `getSymbolicLinkStatus`, encodes it
> as unicode, yielding "fo\303\202\302\241". Which is
> not the same as the original filename.
The new ghc requires a new data type, `RawFilePath` be used if you The new ghc requires a new data type, `RawFilePath` be used if you
don't want to impose utf-8 filenames on your users. I have a `newghc` branch don't want to impose utf-8 filenames on your users. I have a `newghc` branch
in git where I am trying to convert it to use `RawFilePath`. However, since in git where I am trying to convert it to use `RawFilePath`. However, since