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

Re: Missing encoding property per repository location

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-06-10 22:14:59 CEST

news <news@sea.gmane.org> wrote on 06/10/2005 04:10:21 PM:

> >
> > One thing you might try is experimenting with just the Subversion
> > line and your shell settings to see when there is or is not a problem.

> > Also, if you are not using JavaHL within Subclipse, then switching to
> > *might* give better results. No matter what you do, I think your
> > will need to be set in the process that starts Eclipse.
> >
> currently I set the LANG before starting Eclipse what's ok for me.
> Nevertheless I can imagine that it may be a
> limitation for users working on different projects simultaneously with
> different encodings.

There is nothing specific to the Eclipse environment about that problem.
That is why you are better off explaining your general problem on the
Subversion users@ mailing list and ask how someone using the CLI deals
with these issues.

Now that I think about it, I think the locale stuff only matters for the
file and folder names themselves, not the contents. I believe Subversion
just treats the file contents as binary and does not change the file
content based on encoding. Again, the Subversion users@ list would be the
best place to ask.

Subclipse just uses the Subversion API/libraries. Subversion does all of
the reading/writing of your files. So the answers need to come from


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Jun 11 06:14:59 2005

This is an archived mail posted to the Subclipse Users mailing list.

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