From eb924d1d0214ef453ab9e2ab86ead314bccb3f59 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 17 Jun 2016 09:33:09 -0400 Subject: comment --- .../comment_11_3839f018cbbd1043e645bf728162dea1._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/bytes_in_privData__63__/comment_11_3839f018cbbd1043e645bf728162dea1._comment diff --git a/doc/todo/bytes_in_privData__63__/comment_11_3839f018cbbd1043e645bf728162dea1._comment b/doc/todo/bytes_in_privData__63__/comment_11_3839f018cbbd1043e645bf728162dea1._comment new file mode 100644 index 00000000..93094e84 --- /dev/null +++ b/doc/todo/bytes_in_privData__63__/comment_11_3839f018cbbd1043e645bf728162dea1._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 11""" + date="2016-06-17T13:16:17Z" + content=""" +Hmm, the way Strings are used for PrivData takes advantage of ghc's +"filename encoding", which is supposed to allow arbitrary bytes to be +included in filenames; unicode surrogate characters are used to map +them to unicode. + +But, Property.File is using readFile, witeFile, and writeFileProtected, +which will bail on invalid unicode as the filename encoding is not used. +Your patch avoids that problem I see. +"""]] -- cgit v1.2.3