summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joey.kitenet.net/ <joey@web>2012-01-28 19:40:34 +0000
committerGravatar admin <admin@branchable.com>2012-01-28 19:40:34 +0000
commita75eff4a8eb937b07c15f817d329647e4a4391fe (patch)
treefed7d603b8bc09b23f515b2760a9b294a1e720c4
parent2a6be431d4cc4d8056f45f32e91b1b72a65fb107 (diff)
Added a comment
-rw-r--r--doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment b/doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment
new file mode 100644
index 000000000..dcfd59bce
--- /dev/null
+++ b/doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joey.kitenet.net/"
+ nickname="joey"
+ subject="comment 8"
+ date="2012-01-28T19:40:34Z"
+ content="""
+Lauri a scratch patch would be very helpful. Encoding stuff makes my head explode.
+
+However, I am very worried by haskell's changes WRT unicode and filenames. Based on user input, git-annex users like to use it on diverse sets of files, with diverse and ill-defined encodings. Faffing about with converting between encodings seems likely to speactacularly fail.
+"""]]