Le samedi 02 août 2008, Vincent Siveton a écrit : > >> -docencoding "If you omit this option but use -encoding, then the > >> encoding of the generated HTML files is determined by -encoding." > >> We need to reflect this logic and NOT using UTF-8 which is actually the > >> default. > > > > But using UTF-8 as the default was the whole intention of MJAVADOC-206. and the whole intention of MNG-3608 > > Yes but I think it is not the correct behaviour according the javadoc > tool documentation. > I fixed it in r681961 (crazy timing!) and I would like to close the > issue as won't fix. the "Default Value" section of "Report Encoding Configuration" proposal [0] treats this point. I tried a discussion both on dev and user list to work on this, but only Benjamin replied: as I expected from him, fixed UTF-8 default value was ok :) Which is perfectly fine for me (won't break anything).
The behaviour actually discussed is IMHO perfectly viable too: from a user perspective, there is a good chance input encoding can be used as output encoding too. It will be a little more difficult to code (like Benjamin already noticed, in the case a plugin does not parse sources, sources encoding is not actually available as a parameter) I'll add a paragraph in this section to explain the behaviour actually discussed. And we'll need to choose a global Maven plugins behaviour, not only for javadoc plugin. Hervé [0] http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
