From: Martin D. <mar...@no...> - 2005-01-31 08:26:00
|
> GeoTools2 module build report 20050130 > gt2:main cleaned > gt2:sample-data cleaned, compiled, tested, INSTALLED 0000 > > [...snip...] > /home/autorun/cvs/geotools/gt/module/main/src/org/geotools/units/UnitFormat.java:99: unclosed character literal > private static final char DOT_SYMBOL = '???'; // TODO: on devrait plut???t utiliser '\u22C5', mais ce symbole n'est pas affich??? correctement. I noticed that someone moved a lot of code into a 'legacy' module. I suspect that the remaining code as no more dependencies to org.geotools.units. If this is true, than org.geotools.units should be moved into 'legacy' too; it is replaced by 'javax.units' (from the units.jar file). It should allow main to compile as a quick fix (but 'legacy' will continue to fail). Problem #2: It seems that all characters over ASCII 127 has been replaced by some strange characters. They were clearly an encoding problem in some recent change commited. What make this much more problematic is that all character over ASCII 127 has been replaced by the same sequence of strange character. Concequently, it is not impossible to find the original character from the new sequence. We will have to write a script that compare against the previous version on the SVN and put back the right characters. 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. 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?) Martin. |