On 19/01/2008, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > Hi, > > I have just submitted a patch to commons-parent, which introduces two > new properties: commons.encoding and commons.docEncoding. The former > is the encoding of Java source files, the second is the encoding of > generated Javadoc files. > > This change was caused by the problems with the copyright symbol in > the commons-fileupload distribution. >
Why not just use the © HTML tag? That should avoid any encoding issues. > I believe that noone will question the necessity to specify an > explicit encoding because the default encoding can't be used by > developer machines over all the world. The question remains, why I > choosed iso-8859-1 and not UTF-8, and in that point my choice is > surely questionable. > > UTF-8 would have been my personal preference, and I tried it first. > However, it simply didn't work to fix the above problem, and Firefox > still was displaying invalid characters. Hence iso-8859-1. > > Jochen > > P.S: I also upgraded the version of the maven-jar-plugin to 2.2, which > doesn't recreate jar files every time. > > -- > Look, that's why there's rules, understand? So that you think before > you break 'em. > > -- (Terry Pratchett, Thief of Time) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
