[ 
http://jira.codehaus.org/browse/MCHANGES-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269558#action_269558
 ] 

Benson Margulies edited comment on MCHANGES-168 at 6/5/11 11:11 AM:
--------------------------------------------------------------------

r1131489 | bimargulies | 2011-06-04 16:33:22 -0400 (Sat, 04 Jun 2011) | 5 lines

[MCHANGES-168]: Fix non-Latin-script character handling.

The actual repair here was the change to maven-reporting-impl version 2.1. 
However, I then went off and set up a 
way to test JIRA functionality without actually talking to JIRA. That involved 
a bit of refactoring and mocking.

      was (Author: bmargulies):
    fixed in 1131489.
  
> Jira Report (jira-report.html) scrambles encoding of Jira Issues when their 
> summary is written in Non Latin Characters
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCHANGES-168
>                 URL: http://jira.codehaus.org/browse/MCHANGES-168
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: jira
>    Affects Versions: 2.1
>         Environment: mvn on Mac OS X 10.5.7
> Atlassian JIRA Enterprise Edition, Version: 3.13.2 on Ubuntu 8.04.2 
>            Reporter: Vangelis Ghiossis
>            Assignee: Benson Margulies
>             Fix For: 2.6
>
>         Attachments: Jira-Report-ScreenShot.jpg, jira-report.html, 
> jira-results.xml, pom.xml
>
>
> My Jira Issues have Summaries in Jira in non-Lating characters (in Greek in 
> our case). 
> The plugin works great up to the point that it creates the jira-report.html 
> (attached).
> The jira-results.xml seems to be in UTF-8 (also attached).
> If an XSL Stylesheet is used it does not seem to observe the rss data 
> encoding of Jira Issues which works, by the way, fine win Non-Latin 
> Characters with other rss clients.

-- 
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

        

Reply via email to