[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] character encoding problems
|
Yes, as Andrew indicates there are problems with using the prefs to fix
this.
I think the easiest way of fixing things is just not to use any offending
characters. That's currently how I'm solving things.
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
Andrew
Niefer/Ottawa/IBM
@IBMCA To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org cc
"CDT General developers list."
<cdt-dev@xxxxxxxxxxx>,
13/09/2006 11:36 cdt-dev-bounces@xxxxxxxxxxx
AM Subject
RE: [cdt-dev] character encoding
problems
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
Note that the headless build of CDT won't know about any encoding
preferences from the workspace or project preferences. For headless build
purposes, you can set the default encoding to use for a project, or set
custom encodings per file or folder in the project's build.properties file.
See the javacDefaultEncoding and javacCustomEncodings properties here:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.pde.doc.user/reference/pde_feature_generating_build.htm
-Andrew
"Leherbauer, Anton"
<Anton.Leherbauer@xxxxxxxxxxxxx>
To
Sent by: <wieant@xxxxxxxxx>, "CDT
cdt-dev-bounces@xxxxxxxxxxx General developers list."
<cdt-dev@xxxxxxxxxxx>
cc
09/13/2006 10:51 AM
Subject
RE: [cdt-dev] character
Please respond to encoding problems
"CDT General developers list."
<cdt-dev@xxxxxxxxxxx>
Changing the encoding of a CVS repository location
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc
.user/tasks/tasks-95a.htm
"The encoding does not affect the contents of file."
I don't think that the encoding problems were caused by CVS
checkin/-out.
I suppose, CVS handles all text files transparently as byte stream
without
the need to encode/decode.
Toni
> -----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.
>
>
> Hi,
>
> 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
> encoding?
>
> And what is the default Eclipse CVS repository encoding btw,
> I couldn't
> find it on the Using_Eclipse_and_CVS wiki page?
>
> Regards,
> Wieant
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
