Closed
Bug 377235
Opened 17 years ago
Closed 17 years ago
reply_header_locale "en-US" not working at 2.0 RC1
Categories
(Thunderbird :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: masaki.katakai, Assigned: mscott)
Details
I started using Thunderbird 2 RC 1 for Windows. I downloaded Japanese version. The behavior has been changed around mailnews.reply_header_locale and mailnews.reply_header_type. user_pref("mailnews.reply_header_locale", "en-US"); user_pref("mailnews.reply_header_type", 2); I set the locale to "en-US", but the compose window inserts Japanese header, it should be English.
Comment 1•17 years ago
|
||
Are you saying it worked before? If not -> bug 211004.
Reporter | ||
Comment 2•17 years ago
|
||
I see, thank you for the info. I mean actually the behavior has been changed from Beta2. When I set these my prefs, user_pref("mailnews.reply_header_locale", "en-US"); user_pref("mailnews.reply_header_type", 2); It returns, Beta2: On ..., ... wrote: RC1: (...), ... <japanese> in Japanese locale. When I checked the properties files of Japanese, these strings have been localized at RC1. Is this correct? These keys are now localized at RC1. locale/ja/messenger/messengercompose/composeMsgs.properties: mailnews.reply_header_authorwrote = mailnews.reply_header_ondate = Should I need to change bug category to localization?
Comment 3•17 years ago
|
||
I think the mailnews.reply_header_locale is only supposed to affect the time/date format. With beta2, was is possible to get anything other than the en-US values? Like what happened if you set it to ja-JP or an empty string.
Reporter | ||
Comment 4•17 years ago
|
||
I see, Thank you very much, Magnus. OK, I should have filed this to localization category and the synopsis should be "header description has been changed from beta2". I'll change this to other category.
Reporter | ||
Comment 5•17 years ago
|
||
I filed a new bug in localization category bug 377690 and will close this as INVALID. Thank you very much for help.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•