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

Re: Where to convert?

From: Marcus Comstedt <marcus_at_mc.pp.se>
Date: 2002-07-22 12:57:41 CEST

Ulrich Drepper <drepper@redhat.com> writes:

> Note that the last point is much more important for svn than for other
> projects using exclusively Unicode internally (such as some GUI
> toolkits). The latter normally don't have to deal with arbitrary texts,
> just texts which appear in menus and dialogs. There might be an editor
> widget but it's not the only play in town. Svn on the other hand is the
> one and only tool to use. Imagine somebody at a research library who's
> translating documents for which a new encoding had to be devised. It
> should not be impossible to use svn. If it would be the people who set
> up the system would have to rule out using svn from the beginning, even
> without accute problems, since problems might appear at some time.

I think you are misunderstanding something here. svn does not recode
_file contents_. The research library can use whatever character
encoding they like in their files and have them version controlled by

> - conversion of file data should be optional. The file/directory
> attributes which are already used can be extended to a flag specifying
> encoding of a file. The default might be UTF-8. If a directory has
> an attribute all contained files are encoded this way (unless
> overwritten). The encoding for files can be explicitly specified.

That would mean _adding_ the possibility to have files recoded, since
it's not done now. What already exists though is the possibility to
set a property on each file with its character encoding. This would
be for the benefit of external tools, since svn itself doesn't care
what encoding the file is in.

> There is one place where I don't see a problem with using UTF-8
> throughout if this is desirable and this are the places handling file
> names.

And that is where it's mainly used. The other places where it's
currently used are: user ids, URLs, property names, log messages and
error messages. _Not_ file contents.

> Please think about this and don't dimiss this just because this is not
> how it's done today and not because Apache doesn't need it.

How about dismissing it because it _is_ how it's done today? ;-)

  // Marcus

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 13:05:16 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.