Bug 461952
Summary: | SSM text breaks in some Asian languages | ||
---|---|---|---|
Product: | [Retired] Red Hat Network | Reporter: | Amanda Carter <acarter> |
Component: | RHN/Web Site | Assignee: | Grant Gainey <ggainey> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Network Quality Assurance <rhn-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | RHN Stable | CC: | dhughes, rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | us=47228, Rally US139 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-02 20:52:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 601825 |
Description
Amanda Carter
2008-09-11 16:30:26 UTC
I added a user story and got on backlog http://wwwapps.rdu.redhat.com:8080/xplanner/do/view/userstory?oid=47228 Some investigation - putting notes here so we don't lose them. The page is using Ajax to talk back to the server on checkbox-click. The server updates the SSM set, and also figures out the appropriate strings for the header and pagination based on the user's current locale setting. Those strings are passed back to the Ajax library in the browser as a response, in the X-JSON header. When that response leaves our code (and as far up the Tomcat stack as I could trace it), the strings are fine. By the time the response gets back to the browser, however, it's been mangled. The '??????' says to me that somewhere along the way, the string is going through a character-encoding that doesn't understand the APAC code set. Western European languages aren't affected (which may give us a hint as to where to look for the broken encoder) No ETA for a fix, just trying to get the state of the investigation written up. The culprit here is the underlying AJAX library. It put s the returned data (which is already localized) into a header. The character-encoding is ignored for headers - so by the time the response gets back to the browser, the header is attempting to render UTF-8 as Latin-1, and failing. commit b46a544a22600933cbb04f55980b3d1a3e01bd37 Verified on webdev. |