diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-02-02 10:31:56 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-02-02 10:31:56 -0400 |
| commit | 33fd49703cab632225b6ec36a797daef63c86012 (patch) | |
| tree | d4e4674f314f70ae64c3a3df96022db5ee83a6cc /doc/bugs/problems_with_utf8_names.mdwn | |
| parent | f2081ad056306c663ac89c95f379b39135e682e5 (diff) | |
update
Diffstat (limited to 'doc/bugs/problems_with_utf8_names.mdwn')
| -rw-r--r-- | doc/bugs/problems_with_utf8_names.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/problems_with_utf8_names.mdwn b/doc/bugs/problems_with_utf8_names.mdwn index 3c3fdd0ac..cb5917ef8 100644 --- a/doc/bugs/problems_with_utf8_names.mdwn +++ b/doc/bugs/problems_with_utf8_names.mdwn @@ -11,6 +11,14 @@ the encoding of `RawFilePath` is not specified), this means changing essentially all of git-annex. Even the filenames used for keys in `.git/annex/objects` need to use the new data type. --[[Joey]] +> Actually it may not be that bad. A `RawFilePath` contains only bytes, +> so it can be cast to a string, containing encoded characters. That +> string can then be 1) output in binary mode or 2) manipulated +> in ways that do not add characters larger than 255, and cast back to +> a `RawFilePath`. While not type-safe, such casts should at least +> help during bootstrapping, and might allow for a quick fix that only +> changes to `RawFilePath` at the edges. + **As a stopgap workaround**, I have made a branch `unicode-only`. This makes git-annex work with unicode filenames with ghc 7.4, but *only* unicode filenames. If you have filenames with some other encoding, you're |