Re: [Geotools-devel] GeoTools Build Report [ 2005/01/30 23:55 ]

[Martin D. <mar...@no...>]

Jody Garnett a =E9crit :
>> So I have two questions:
>> 1) What is the intented encoding for Geotools code? The old encoding
>>    was the platform-dependent one, which is LATIN-1 on my machine. It
>>    is clearly not a good solution, since it will lead to problem on
>>    any machine using a different encoding. I suggest to standardize
>>    to UTF-8.
>=20
>=20
> I have no guidence, I think we can use \uXXXX constructs for any unicod=
e=20
> symbols we need.

I agree to use \uXXXX constructs in code: that ways, we will be sure=20
that it compiles right no matter what is the user-compiler settings.

However, \uXXXX constructs is not convenient for comments. There still=20
some French comments aroung (I have not finished all translations), and=20
some comments use mathematical symbols as well. It is better to agree=20
ourself on an encoding. Peoples not complying to this encoding will have=20
a broken display, but since it will be in comments only, it should not=20
break the build.


>> 2) What was the revision number on which the encoding change were
>>    applied? I need that in order to reput back the right characters
>>    (or do you have any quick way to fix that?)
>=20
>=20
> I would go back through the history and find what revision caused the=20
> switch and cut & paste the changes forward.

We will need a script, because the replacement appears in hundred of plac=
es.

     Martin.