[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [RFC/PATCH] commit messages not 8-bit compatible

From: <cmpilato_at_collab.net>
Date: 2002-05-29 22:03:50 CEST

Greg Hudson <ghudson@MIT.EDU> writes:

> On Wed, 2002-05-29 at 15:35, Branko Čibej wrote:
> > I never heard of such a paradigm. Yes, all _paths_ passed to the svn
> > libraries should be UTF-8 and canonicalized, but not all strings. I'm
> > sorry I didn't notice that berfore in your patches. AFAIK we never
> > discussed canonicalizing anything but paths.
>
> It sounds like we don't have a lot of consensus here (which is
> unfortunate for Marcus, who I think signed onto this task with the
> understanding that there was a pre-existing choice). Karl seems to side
> with Marcus on translating because UTF-8 and the local charset for all
> interesting values; Mike and I would rather be charset-neutral; Branko
> wants to use UTF-8 for paths and be charset-neutral for everything
> else. (I'm not sure why pathnames deserve special treatment.)

Hm. What makes Branko's desires different than ours, Greg? It seems
to me that Subversion (from the client layer on down) can satisfy both
the desires to treat all paths as UTF-8 and not perform charset
conversions so long as:

   - the individual client binary does any necessary conversions
     between The User and UTF-8, and

   - APR does any necessary conversions between UTF-8 and The
     Filesystem.

Am I missing something?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 1 14:23:45 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.