Hi Gary,
2012/11/14 Gary Gregory <garydgreg...@gmail.com>
> I think you have to tell the compiler and javadoc plugin about the
> encoding.
>
> The thing I don't understand is that the encoding for the javadoc plugin
should default [1] to ${project.build.sourceEncoding} and
${project.reporting.outputEncoding} which are both set to UTF-8 in our pom.
I must be missing something...
Sébastien
[1]
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#What_are_the_values_of_encoding_docencoding_and_charset_parameters
Gary
>
> On Nov 14, 2012, at 3:31, "Sébastien Brisard" <sebastien.bris...@m4x.org>
> wrote:
>
> > Hi again,
> >
> > Correction
> >
> >>
> >> There is no problem with the current setup of our website (at least, the
> >> website generated locally has no problem).
> >>
> >> I was sure of the contrary, but it turns out that the generated Javadoc
> > does not display UTF-8 characters correctly, although the following
> > properties are set in the pom.xml
> > <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> >
> >
> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
> >
> > I will enquire. Meanwhile, you *can* use UTF-8 characters in the *.apt
> > files used for the website.
> > Sébastien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
