This is my objection to basing it on the source encoding. My preference is to pick output encoding as UTF-8 with a simple means to change it. Source encoding is a different matter. Some source files should never be UTF-8 encoded and yet the output should not be encoded in the same encoding...
I vote A On Sun, Aug 3, 2008 at 11:29 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > If there is a good way to make it work, the source files sounds "best" as > it is reproducible and gives a default that should work in most instances. > However, I think there are some reports that would have multiple source > files, and they could be of mixed encodings, right? If that would be a > problem, then selecting UTF-8 might be better. > > - Brett > > > On 04/08/2008, at 6:20 AM, Hervé BOUTEMY wrote: > > Hi, >> >> While working on "Report Encoding Configuration" proposal [0], 2 options >> were >> discussed lately for default value [1]: >> >> a) use fixed UTF-8 encoding >> >> b) use same encoding as source files >> >> >> Both options seem viable: choosing between them will be a question of >> taste. >> Hence this poll: what is your preference? >> >> Regards, >> >> Hervé >> >> [0] >> http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration >> >> [1] >> >> http://www.nabble.com/Re%3A--VOTE--Release-Maven-Javadoc-Plugin-version-2.5-p18789937.html >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
