[ http://jira.codehaus.org/browse/MNG-722?page=comments#action_44326 ]
Incze Lajos commented on MNG-722: --------------------------------- 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): #---------------------------------------------------------------------------- # 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. > maven-site-plugin maven-site.vm contains wired encoding > ------------------------------------------------------- > > Key: MNG-722 > URL: http://jira.codehaus.org/browse/MNG-722 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Environment: all > Reporter: Incze Lajos > Assignee: Vincent Siveton > > > maven-site-plugin maven-site.vm contains wired encoding: > <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> > It probably needs a conf. parameter and changed to > <meta http-equiv="Content-Type" content="text/html; charset=$outputEncoding" > /> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
