summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-02-02 10:56:39 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-02-02 10:56:39 -0400
commitfc8a1d213b3683253923529918c84c91a75448fa (patch)
tree1e8148fca9313ba18340d6fb3c12b21eb7073089
parent39e887e8e623acd011a9ae40f06b8f16548c019d (diff)
update
-rw-r--r--doc/bugs/problems_with_utf8_names.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/bugs/problems_with_utf8_names.mdwn b/doc/bugs/problems_with_utf8_names.mdwn
index cb5917ef8..c9ca1e3b0 100644
--- a/doc/bugs/problems_with_utf8_names.mdwn
+++ b/doc/bugs/problems_with_utf8_names.mdwn
@@ -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
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
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