[ 
http://mifosforge.jira.com/browse/MIFOS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66038#comment-66038
 ] 

Adam Monsen commented on MIFOS-4789:
------------------------------------

Ah, native2ascii! You know, I thought about this, but I [assumed that my fix to 
convert all properties to latin1 was on 
master|http://article.gmane.org/gmane.comp.version-control.git/168481], so I 
dismissed it, thinking, aw, that can't be it, the properties files are latin1 
because struts needs that and I committed a hack to work around that a month 
ago. Argh!

I did the fix in 2a1ed0436, but it appears to have been undone in 0f8132386. I 
re-did it in 249ddb25 and 59f62ae4.

As of head/master 59f62ae4, Chinese works for me in Tomcat 7. I can't get 
Chinese to work in Jetty 7, so maybe we still need your filter that forces the 
encoding.

Michael, will you try your filter with the latest head/master, Chinese, and 
Jetty 7?

> can't see Chinese: app server sends non-UTF-8 charset in response headers for 
> old ui (Struts/JSP)
> -------------------------------------------------------------------------------------------------
>
>                 Key: MIFOS-4789
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4789
>             Project: mifos
>          Issue Type: Bug
>          Components: Build and Testing, Internationalization, Localization
>    Affects Versions: Release G
>         Environment: Chinese head/master test server running 
> head-master-archive build #73. Multiple browsers/operating systems.
>            Reporter: Adam Monsen
>            Assignee: Sumit Shah
>            Priority: Critical
>              Labels: chinesetranslation, volunteer
>             Fix For: Release G - Iteration 2, Release G
>
>         Attachments: 
> 0001-FIXED-MIFOS-4789-can-t-see-Chinese-app-server-sends-.patch
>
>
> Jetty is incorrectly setting a non-UTF-8 character set for Struts/JSP pages. 
> I'm using Google Chrome's developer tools to view the response headers, but 
> other software (ie: firefox plugins) can also be used to view response 
> headers.
> h1. Expected
> {noformat}Content-Type:text/html;charset=UTF-8{noformat}
> SpringMVC/ftl pages work. For example: http://ci.mifos.org:8118/mifos/
> h1. Actual
> {noformat}Content-Type:text/html;charset=ISO-8859-1{noformat}
> For example: 
> http://ci.mifos.org:8118/mifos/custSearchAction.do?method=getHomePage
> h1. Workaround
> Manually set encoding to UTF-8 in browser.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to