comment and wontfix

This commit is contained in:
Joey Hess 2023-06-05 14:40:25 -04:00
parent 528882a6df
commit 07db8e234a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 35 additions and 0 deletions

View file

@ -34,3 +34,4 @@ LC_ALL=
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
yes, that worked in the past (I think) yes, that worked in the past (I think)
> [[wontfix|done]] --[[Joey]]

View file

@ -0,0 +1,34 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2023-06-05T18:10:23Z"
content="""
> That is what locales are for.
>
> Why not use them just correctly? It is just wrong to use utf8 characters in non-utf8 environments.
It's perfectly find to use unicode in filenames at any time. Files have the
name they have no matter how you configure your locale.
If git renamed unicode files when cloning a repository, just because the
current locale did not support unicode, it would be broken.
If git-annex metadata contains unicode and you enter a view, git-annex is
operating acceptably when it preserves that unicode in the viewed filename.
Maybe git-annex could try to transliterate unicode in viewed filenames
in some way to work better non-unicode locales. But the locale can change.
And git-annex needs to be able to reverse view filenames back to the
filename used on the viewed branch. So it's not practical to vary the view
filenames to fit the locale, because that would prevent that reversing
from working unless it had a way to determine that locale that was in use
when the view was generated.
git-annex has to replace the `/` character with *something* when generating
a viewed file from metadata that contains that character. It used to
use `%`, since that at least contains a slash, but I didn't think that was
very readable. The unicode slash character it uses is very readable for the
vast percentage of users who are not stuck with 1980's era displays.
Sorry, it's simply a tradeoff between you and everyone else.
"""]]