[
http://jira.codehaus.org/browse/JBEHAVE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270259#comment-270259
]
Mariusz Smykula commented on JBEHAVE-533:
-----------------------------------------
I think this bug is related to Freemaker engine, which is ignoring
-Dfile.encoding=utf8 flag and still using cp1250 on Windows.
> Bad encoding in JBehave Raports with default configuration from jbehave
> archetype in Windows
> --------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-533
> URL: http://jira.codehaus.org/browse/JBEHAVE-533
> Project: JBehave
> Issue Type: Bug
> Environment: Windows
> Reporter: Mariusz Smykula
> Attachments: wrong-encoding-sample-prj.tar.gz,
> wrong-encoding-sample-prj.zip
>
>
> I have created project from archetype with command:
> {{mvn archetype:generate -DarchetypeGroupId=org.jbehave
> -DarchetypeArtifactId=jbehave-spring-archetype}}
> and edited my.story file (added some international chars)
> After this
> There is:
> ??A scenario with some pending steps
> ĹĂłĹĹĽĹĹĂłaĹÄĹ??
> Should be:
> ??Scenario: A scenario with some pending steps
> łóśżłśóaśęł?? <- here is proper
> encoded letters
> I have edited pom.xml and added:
> {{<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>}}
> {{<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>}}
> in properties section.
> The HTML and XML raport should be properly encoded after this. I think option
> -Dfile.encoding=UTF-8 should be not required for this. Maven project should
> have identical results on all platforms if properly configured.
--
This message is automatically generated by JIRA.
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