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

Re: utf-8 sanity check.

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-07-11 23:40:56 CEST

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> Ben Collins-Sussman <sussman@collab.net> writes:
> > Use --locale:
> >
> > * to specify the charset of the log message being read by -F
> >
> > * to interpret working copy paths that will be read later on
> > (i.e. 'svn up', with no args)
> I'm not sure I understand the latter scenario... ?

I have a working copy full of directories and filenames that contain
high-ascii characters.

When you run status, or update, or commit, we not only walk over
entries in the entries file (as UTF-8 strings), but sometimes we stat
the files directly as well. Then the UTF-8 paths and filenames need
to be converted to native charset so we can call apr_file_*()
routines, no?

Keep in mind, I'm assuming that the charset of your working copy is
somehow different than your system locale. But that's no more
far-fetched than possibly writing a log message in a locale different
than your system locale.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 11 23:45:25 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.