Mark Derricutt wrote:
>From the look of it, my guess it's because of the encoding of the
.java files.
The code reads:
convertNonASCIIString("Çüéâäàåçêë"),
instead of using raw unicode references such as \uxxxxxx
When I check the file information on the source I've checked out of
CVS I see:
[EMAIL PROTECTED]:~/temp/wicket/wicket$ file
/home/amrk/temp/wicket/wicket/src/test/wicket/util/string/StringsTest.java
/home/amrk/temp/wicket/wicket/src/test/wicket/util/string/StringsTest.java:
ISO-8859 C program text
The OS sees the file as an ISO-8859 encoded file, which doesn't know
about those extended characters used in the test.
The string is Cp-1252 or ISO-8859-something, not utf-8. This line would
probably help at the project.properties file:
maven.compile.encoding=iso-8859-1
The error can be reproduced by using encoding utf-8. On windows default
is usually Cp-1252 and on OS/X MacRoman. The string at the source code
is valid on both. On most modern linux distributions (Ubuntu is not one
of those) default encoding is UTF-8 and so the test fails. It would
really be better to use UTF-8 everywhere..
--
Janne Hietamäki
Cemron Ltd
http://www.cemron.com/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
