Closed Bug 964175 Opened 6 years ago Closed 5 years ago
.2 .0: lightning incorrect|/incomplete Russian localization
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release) Build ID: 20140113121555 Steps to reproduce: I use Thunderbird-24.2.0 on Russian localized GNU/Linux OS. I.e.: $ locale LANG=ru_RU.utf8 … I've just started calendar (or tasks) from menu item (in Russian it's name is "События и задачи"). Actual results: In the left top of window I see this month calendar. In _alien_ format (week starts from Sunday). Expected results: In Russia week starts from Monday! So, for Russian locale I expect lightning to display calendar in completely localized format (i.e. with week, starts from Monday).
Component: Untriaged → General
Product: Thunderbird → Calendar
Version: 24 → unspecified
You can configure the week start day in Edit > Preferences > Calendar > Views.
(In reply to Stefan Sitter from comment #1) > You can configure the week start day in Edit > Preferences > Calendar > > Views. Thank you! Of course, it is so… But for years of using GNU/Linux desktop (preferring gtk applications) I've forgot, how it is to set/modify locale settings via GUI. Lightning starts with correct (Russian) locale automatically, depending on system's environment. And I expect it to get completely correct defaults, with no need for me to analyse settings and preforming minor (there is no general language settings in GUI) interface fixes.
Severity: normal → minor
I checked Lightning l10n and found preference calendar.week.start in lightning-l10n.js is set correct: ># the default day to start the week on >#0=Sunday 1=Monday 2=Tuesday 3=Wednesday 4=Thursday 5=Friday 6=Saturday >pref("calendar.week.start", 1); I confirm this bug, but I think it is no localization problem.
lightning-l10n.js has no affect, see Bug 395504.
Just now I've find this issue fixed in Thunderbird 31 ESR (31.6.0).
Marked as WORKSFORME per comment 5
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
(In reply to Alexander L. Slovesnik from comment #6) > Marked as WORKSFORME per comment 5 Why «WORKSFORME»?!? To my mind the correct resolution will be FIXED. But it's unavailable for me. I don't know how this fix relates with particular this bug report, but it's really FIXED.
(In reply to Ikonta from comment #7) > (In reply to Alexander L. Slovesnik from comment #6) > > Marked as WORKSFORME per comment 5 > > Why «WORKSFORME»?!? > To my mind the correct resolution will be FIXED. But it's unavailable for me. > I don't know how this fix relates with particular this bug report, but it's > really FIXED. OK.
Resolution: WORKSFORME → FIXED
You need to log in before you can comment on or make changes to this bug.