On 2010-08-11 16:26:32 +0200, Vincent Lefevre wrote:
> On 2010-08-11 13:42:35 +0200, Stefan Sperling wrote:
> > On Wed, Aug 11, 2010 at 12:31:48AM +0200, Vincent Lefevre wrote:
> > > On 2010-08-10 20:59:00 +0200, Stefan Sperling wrote:
> > > > Right now, if the filename cannot be represented in the current locale,
> > > > you get this error: "svn: Can't convert string from 'UTF-8' to native encoding"
> > >
> > > which is bad and prevents users from writing POSIX-conforming scripts
> > > using svn, i.e. under the POSIX locale (except on systems where the
> > > POSIX locale uses UTF-8, but I don't know any).
> >
> > There's no reason your script could not configure a UTF-8 locale if that
> > is needed to represent filenames which exist in the repository.
>
> Configuring a UTF-8 locale can yield non-portable behavior.
> There's a good reason why various scripts do a "LC_ALL=C".
>
> Moreover there's no portable way to select a UTF-8 locale.
Actually, some UTF-8 locales may not give the expected behavior,
even with svn. For instance, one may want to parse the output of
"svn info", and using fr_FR.UTF-8 (if installed) gives localized
output (in French), which would make the parsing fail. And I think
that "Do not use svn for scripts, reimplement everything using
bindings." would not be a wise answer.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
Received on 2010-08-11 17:24:08 CEST