Scott Lamb <slamb@slamb.org> writes:
> I don't think perfection is possible - there are always going to be
> some paths you can't represent. In particular, Unix does not enforce
> any character set on filenames - they just can't contain null or
> '/'. So if you run Subversion in the UTF-8 locale, I think you will be
> unable to access an accented filename created by a program operating
> in a iso-8859-1 locale, since it would be an invalid UTF-8
> sequence. (And conversely, in the iso-8859-1 charset, it couldn't
> access some UTF-8
>
> files.) I don't think that problem can be solved, short of redesigning
> the Unix filesystem model to be charset-aware.
As I have already explained, making sure the repository contains files
whose names can be represented on the systems relevant to that project
should be left to project policy. If that particular repository is
never going to be checked out on a UNIX system with a iso-8859-1
locale, then there is no reason to impose that particular restriction
on that particular repository. Since svn can't know about the goals
and policies of the project, it should (ideally) leave the set of
filenames totally unconstrained. The constraints will instead come
from the OS where the files are created (since if you can't create the
file, you can't add it to the repository), and from project policy
(either informally, or enforced through commit hooks).
// Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 29 20:15:09 2002