[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:01:39 CEST

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

> I've got following problem: if I start Eclipse (under Linux) with
> UTF-8 and perform a checkout or a replace
> files containing letters like , , contains strange unreadable
character at
> the place of , and . If I set
> LANG=de_DE.ISO-8859-1 before starting Eclipse, the files are correctly
> In both cases Eclipse shows as property of the file as well as of the
> default (retrieved from container)
> ISO-8859-1.
> I don't know if an option could be set when using the svn command line
but it
> seems to me that an information concerning
> the encoding is missing at the repository level like the one used by
> for CVS Repositories.

Subversion uses the locale settings like LANG to determine the encoding.
There are no Subversion options we can set from Subclipse that I am aware

I am cc:ing this to the Subversion users@ list in case anyone has other

One thing you might try is experimenting with just the Subversion command
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 that
*might* give better results. No matter what you do, I think your locale
will need to be set in the process that starts Eclipse.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 10 22:03:55 2005

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

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