[
http://jira.codehaus.org/browse/MWEBSTART-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139214#action_139214
]
Markus Grieder commented on MWEBSTART-124:
------------------------------------------
I have the same issue. My proposal to fix the bug:
AbstractGenerator should set an encoding for reading and writing the
template/jnlp-file:
http://velocity.apache.org/engine/devel/developer-guide.html#template_encoding_for_internationalization
The encoding should be read from the template with a XML-Parser: utf-8 if no
encoding is specified.
> Encoding of generated jnlp file(s) always is the system file encoding
> ---------------------------------------------------------------------
>
> Key: MWEBSTART-124
> URL: http://jira.codehaus.org/browse/MWEBSTART-124
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Components: jnlp-download-servlet
> Affects Versions: 1.0-alpha-2
> Reporter: Marius Shekow
>
> When the jnlp files are generated from a .vm template which has <?xml
> version="1.0" encoding="UTF-8"?> (or any other encoding) specified, the
> generated jnlp file will still have the encoding which is typical for the
> operation system (on Windows XP: Cp1252)
> I think the behaviour should rather be that the encoding of the generated
> file equals to the encoding of the source template for the jnlp file (if
> specified, otherwise take the OS default encoding).
> As a result of this bug, the JnlpDownloadServlet from SUN destroyes the
> delivered JNLP file by encoding it in UTF-8, without correcting special
> characters like ä ö ü etc.
--
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 from this list, please visit:
http://xircles.codehaus.org/manage_email
