El lun, 21-03-2005 a las 19:44 +0100, RaphaÃl Luta escribiÃ: (...)
> I guess most of these are just related to my name in the author tag, > no > ? I'll soon have to change name to avoid the issue ;) > Not needed. The problem is actually that .java source code is supposed to be read by the compiler in the machine encoding, unless the build system says otherwise. I could have changed the maven or ant scripts, but I think this is cleaner. It is not just your name, there were a few other instances. Also, the problem is worse with .properties files. Those are specified to be read in ISO-8859-1, no matter the native encoding. the javadocs talk about using explicitly native2ascii to encode them for people using non-latin encodings. http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html The problem with .properties is that ant's copy task tries to read them in native encoding and this brings again the sun.io.MalformedInputException. Unicode escaping should be completely transparent, even in javadocs: http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html#100850 xml files are self describing, and should give no problem. Regards -- Santiago Gala <[EMAIL PROTECTED]> High Sierra Technology, SLU
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente
