Well my point is that this would not work everywhere.
How can "store as bytes" not work (be implementable?) everywhere? I'm
missing something.
When stored/returned as bytes, certainly a filename might look like
garbage when presented to the user, depending on their locale, what the
filename is, what the command does, etc. Or it might fail completely if
the user's filesystem has its own requirements, like zfs or Windows,
just like plenty of filenames cannot be portably used now (case clashes
and so on). People have brought up all those things, but they seem like
red herrings to me. They are all for the user to decide and handle.
At least with bytes svn would not have a (seemingly gratuitous) UTF-8
(or any) requirement on filenames in its own repository. In my naivete,
it seems like being able to manipulate any filename, independent of
locale and encoding, would be a pretty desirable characteristic of any VC.
Blame it on Subversion's insisting on cross-platform
compatibility.
Requiring UTF-8 filenames is not
cross-platform/cross-locale/cross-whatever compatible either.
Or my question would never have arisen.
In any case, as I said, I certainly do not expect any change here. I'm
sure it's a fundamental decision, made for good reason, and will not
be altered. I guess I just don't understand it. So it goes :).
--thanks again, karl.
