[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cdt-dev] character encoding problems
- From: "Leherbauer, Anton" <Anton.Leherbauer@xxxxxxxxxxxxx>
- Date: Wed, 13 Sep 2006 16:51:04 +0200
- Delivered-to: email@example.com
- Thread-index: AcbXNzQD6/aXc/nYTeiIcqvIksGHBQACZyhA
- Thread-topic: [cdt-dev] character encoding problems
Changing the encoding of a CVS repository location
"The encoding does not affect the contents of file."
I don't think that the encoding problems were caused by CVS
I suppose, CVS handles all text files transparently as byte stream
the need to encode/decode.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Wieant Nielander
> Sent: Wednesday, September 13, 2006 3:19 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] character encoding problems
> > 1. convert the files to valid UTF-8 and also mark
> > them as UTF-8 in the project preferences
> > 2. replace the offending characters with plain ASCII.
> > I'd prefer option 1 and I could also do the conversion
> > if nobody objects.
> > BTW, it is probably a JVM-dependent issue how
> > the builtin decoding methods handle encoding problems.
> > The Sun JVM on Windows replaces malformed input bytes
> > and unmappable characters by default (as e.g. in Charset#decode()),
> > instead of reporting errors.
> If I check the default CVS server encoding it appears to be
> Cp1252 on my
> windows machine and ISO-8859-1 on my linux machine, might
> this problem have
> been caused due to such a setting, e.g. file has been checked
> in on Windows
> using Cp1252 server encoding and checked out on PowerPC using
> UTF-8 server
> And what is the default Eclipse CVS repository encoding btw,
> I couldn't
> find it on the Using_Eclipse_and_CVS wiki page?
> cdt-dev mailing list