maven-site-plugin maven-site.vm contains wired encoding

The diagnosis OK, but the cure is bad. It basically depends on
the velocity settings what the output encoding will be. So, the
velocity properties should be adjusted to the required encoding, too.

I have added an outputEncoding parameter in the DoxiaMojo class.

I am not sure about Velocity settings.
If you have the following configuration:
<?xml version="1.0" encoding="utf-8"?>
...
<build>
<plugins>
<plugin>
<artifactId>maven-site-plugin</artifactId>
<configuration>
<outputEncoding>utf-8</outputEncoding>
</configuration>
</plugin>
</plugins>
</build>
...

the name "György" will be correctly displayed.

Could you try it with your POM? and give me your feedback.

It works this way at the moment, but I'm sure that it is because of some
widely used environmental settings. Velocity, which renders this script
has two runtime properties that guide the encodings (in velocity.properties
file):

#----------------------------------------------------------------------------

1. T E M P L A T E E N C O D I N G
   #----------------------------------------------------------------------------

input.encoding=ISO-8859-1
output.encoding=ISO-8859-1

The input.encoding is the encoding of the template files, the output
encoding is the encoding that velocity should use to render its output
stream.

The defaults are the above ones in the repository velocity-1.4.jar.

I'm confused, is this working completely?

You are not alone. No, at the moment it works with UTF-8, but not e.g. with ISO-8859-1.

I have a pom.xml. It is an UTF-8 xml file with accented characters. If I set the new outputEncoding
conf parameter, now I have a well rendered team list with UTF-8 output. But if I set outputEncoding
to ISO-8859-1, I'm given the same garbage az at the start.

The problem, I think, is with the above mentioned velocity properties (namely, output.encoding, the
input.encoding doesn't matter, as the maven-site.vm is pure ascii). The outputEncoding param is
rendered only into the output xhtml, regardless of the output.encoding velocity parameter (which
seems to be UTF-8 for some reason, I don't know, it is hard to find where it is set). So, before
merging the template this parameter should be set for velocity.

OK. I've tracked down the problem. The velocity propery is involved only when it
is the template engine that creates the output writer. In this case it is the DoxiaMojo
that crates the output writer using the java.io.FileWriter which uses the platform
default encoding (nowadays it is mostly UTF-8).

So, every place, where DoxiaMojo uses
new FileWriter(..)
this should be replaced by
new OutputStreamWriter(new FileOutputStream(...), outputEncoding)

FileWriter(...) -> OutputStreamWriter(FileOutputStream(...), outputEncoding)

Works for me. Tested with ISO-8859-1, UTF-8 outputEncoding and
without outputEncoding conf. param., which defaults to ISO-8859-1.

I think you did it the right way. Thanks a lot!

Moreover, with your proposal, we could now handle html entities in the site descriptor, for instance:
<menu name="name".../> where name contains html entities (ie &#xhexa)

I will fix it shortly.

Applied in SVN. Tx again.