Issue Details (XML | Word | Printable)

Key: JRA-8708
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dylan Etkin [Atlassian]
Reporter: sundaramss
Votes: 0
Watchers: 2
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Japanese Characters are not supported at JIRA 3.4.1 deployed in weblogic 8.1 SP3

Created: 04/Dec/05 11:40 PM   Updated: 30/Jul/06 07:37 PM   Resolved: 14/Dec/05 10:39 PM
Component/s: User Management
Affects Version/s: 3.4.1
Fix Version/s: 3.5

Time Tracking:
Not Specified

File Attachments: 1. Java Archive File atlassian-core-2.4.8.jar (87 kB) 14/Dec/05 10:33 PM - Dylan Etkin [Atlassian]

Environment:

Windows 2000


Participants: Anton Mazkovoi [Atlassian], Dylan Etkin [Atlassian], Neal Applebaum and sundaramss
Since last comment: 4 years, 8 weeks, 1 day ago
Labels:


 Description  « Hide

We deployed JIRA 3.41 on weblogic 8.1 SP3. We followed your instruction as given in the following URL
"http://www.atlassian.com/software/jira/docs/latest/servers/weblogic.html" including Character Encoding settings.

After user modifies the user locale as Japanese(Japan) in the Update User Preferences page, the japanese character in jira web page are displayed as "?" characters

Thanks
sundaram.s.s



Neal Applebaum added a comment - 05/Dec/05 08:54 AM

Hmmm.. I wonder if this issue is related to my problems in JRA-8371. I am running Weblogic as well (8.1 SP2) , and when I switch user preference locale to French, the accented characters as "?"


Anton Mazkovoi [Atlassian] added a comment - 05/Dec/05 07:06 PM

I think the problems are related. We will look into the problem.

Thanks,
Anton


Dylan Etkin [Atlassian] added a comment - 14/Dec/05 10:39 PM

I have changed this to be fixed for JIRA 3.5 but I have attached the jar that should fix this for JIRA 3.4.x as well. The problem was in the encoding filter and the way that it was interacting with sitemesh and weblogic. The trouble was that character set was being reset to the default ISO-8859-1 when the conent type was being set without specifying a charset in the content type string. We now explicitly preserve the original charset when setting the content type from the encoding filter. As a result of this, you no longer need to specify the block:

<weblogic-web-app>
            <jsp-descriptor>
              <jsp-param>
                <param-name>encoding</param-name>
                <param-value>UTF-8</param-value>
              </jsp-param>
              <jsp-param>
                <param-name>compilerSupportsEncoding</param-name>
                <param-value>false</param-value>
              </jsp-param>
            </jsp-descriptor>
          </weblogic-web-app>

in your weblogic.xml file.