From 0df23298c381aed8a6c083908ffeb041c6d860e0 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 24 May 2014 19:23:08 +0000 Subject: [PATCH] Added a comment --- ...ent_1_81a4647a9b51bed8c230a2a16990915d._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/Commiting_Files_Containing_Non_Ascii_Char_on_OS_X_/comment_1_81a4647a9b51bed8c230a2a16990915d._comment diff --git a/doc/bugs/Commiting_Files_Containing_Non_Ascii_Char_on_OS_X_/comment_1_81a4647a9b51bed8c230a2a16990915d._comment b/doc/bugs/Commiting_Files_Containing_Non_Ascii_Char_on_OS_X_/comment_1_81a4647a9b51bed8c230a2a16990915d._comment new file mode 100644 index 0000000000..e600657377 --- /dev/null +++ b/doc/bugs/Commiting_Files_Containing_Non_Ascii_Char_on_OS_X_/comment_1_81a4647a9b51bed8c230a2a16990915d._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.36" + subject="comment 1" + date="2014-05-24T19:23:08Z" + content=""" +I think you are going to need to provide more information: + +* Some actual file names that have the problem. \"non-ascii chars\" is a very wide description, you don't even say if you're using unicode or what. +* Some error messages or transcripts of what happens when you see the problem. +* What is your locale setting on OSX. + +I tried with some unicode filenames on OSX and they were committed without difficulty in the en_US.utf8 locale. +"""]]