Closed
Bug 421330
Opened 16 years ago
Closed 16 years ago
Startup error in Macedonian Sunbird 0.8; timezone guessing is broken
Categories
(Mozilla Localizations :: mk / Macedonian, defect)
Mozilla Localizations
mk / Macedonian
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: ssitter, Unassigned)
References
Details
Mozilla/5.0 (Windows; U; Windows NT 5.1; mk; rv:1.8.1.13pre) Gecko/20080305 Sunbird/0.8 Starting Sunbird 0.8 or Lightning 0.8 shows error during the timezone guessing: Грешка: Ја занемарувам локалната временска зона „Америка/Њу Јорк“. TypeError: tz has no properties Изворна датотека: chrome://calendar/content/calUtils.js Линија: 660 The error happens because the string "likelyTimezone" has been translated:: http://mxr.mozilla.org/l10n-mozilla1.8/source/mk/calendar/chrome/calendar/calendar.properties#149 but must be in English: http://mxr.mozilla.org/mozilla1.8/source/calendar/locales/en-US/chrome/calendar/calendar.properties#214 # LOCALIZATION NOTE (likelyTimezone): # Translators, please put the most likely timezone(s) where the people using # your locale will be. Use the Olson ZoneInfo timezone name *in English*,
Comment 1•16 years ago
|
||
Changed to Europe/Paris (GMT+1)... although Europe/Skopje would be more correct, is that possible?
Reporter | ||
Comment 2•16 years ago
|
||
You can specify any timezone/timezones that would be the "better guess" for a detected UTC offset. You just need to use the English names. If Europe/Skopje is better than Europe/Paris you should choose it. Please note that we already switched the tinderbox to release preparation mode. This means you will have to submit your changes to SUNBIRD_0_8_BRANCH as well to take effect. http://groups.google.com/group/mozilla.dev.l10n/msg/1d11a4a12be3062d
Reporter | ||
Comment 3•16 years ago
|
||
Verified fixed using Mozilla/5.0 (Windows; U; Windows NT 5.1; mk; rv:1.8.1.13pre) Gecko/2008030920 Sunbird/0.8. Startup error is gone.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•