[#JRA-4800] Hardcode unicode encoding

JIRA

Hardcode unicode encoding

Created: 06/Oct/04 12:30 AM Updated: 06/Dec/07 08:00 PM

Component/s:

Internationalisation

Affects Version/s:

3.0 Standard Beta

Fix Version/s:

3.13.x

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian], Jed Wesley-Smith [Atlassian], Jeff Turner [Atlassian] and Scott Farquhar [Atlassian]
Since last comment:	38 weeks, 1 day ago
Labels:

Description

« Hide

Currently JIRA's encoding (file.encoding system property) is set globally. This means that no matter what language a user picks in their profile preferences, that translation will be served in the default encoding, which may not be able to represent the chosen language.

We need to either store encoding along with locale in the user's preference, or else move to UTF-8 everywhere (there must be some point to unicode).

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 23/May/05 10:32 AM

Jeff - what do we need to do here?

We can't set the system encoding per user, but I think that we do use UTF-8 as the default now?

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 31/Jul/06 12:17 AM

I think was was confused when filing this bug. There are two encodings:

The system file.encoding, which is used by default when reading content from disk.
The JIRA "Character Encoding", found under General Configuration, which specifies what encoding JIRA's HTML pages are served as.

"Character Encoding" has been defaulted to utf-8 for ages. I don't think there is any legitimate reason for people to change it. Changing it to anything other than a Unicode encoding (utf-8, utf-16) causes broken characters when a different language is selected, which is what happened in ~~JRA-4759~~.

I think we should therefore remove the "Character Encoding" altogether from General Configuration, and put it in jira-application.properties, with a suitable warning in a comment against changes.

I've changed the subject to reflect this.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 05/Feb/07 11:15 PM

Need to be careful here, as in the past if users did edit this property through the user interface the value would be stored in the db.

Just moving this proeprty to the jira-applications.properties file will not work.

Maybe the solution is to write an Upgrade Task that would remove this property from the db, if its there.
Then write in JIRA's Upgrade Guide that if this proeprty was set to something other than UTF-8, then when upgrading jira-application.properties will need to be edited.

[ Permlink | « Hide ]

Jed Wesley-Smith [Atlassian] added a comment - 06/Dec/07 08:00 PM

The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.