Closed Bug 442469 Opened 16 years ago Closed 16 years ago

calendar.properties likelyTimezone=/mozilla.org/20050126_1/Europe/Madrid -> Europe/Madrid

Categories

(Mozilla Localizations :: es-ES / Spanish, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: gekacheka, Assigned: rpmdisguise-nave)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; is-IS; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: trunk

likelyTimezones should be an Olson ZoneInfo id.  Suggested change:

-likelyTimezone = /mozilla.org/20050126_1/Europe/Madrid
+likelyTimezone = Europe/Madrid

(for travelers it may be helpful to add additional cities such as in en-US)

Reproducible: Always





'likelyTimezone' is used on operating systems where Sunbird/Lightning cannot
figure out the identity of the timezone set on the operating system (such as in
MacOSX) and a likely timezone matches the current OS timezone offsets from UTC.
(When it can't find the OS timezone id and there is no match in
likelyTimezones, it will try all timezones in alphabetical order, and may find
a match like Africa/Cueta, so a user may need to set the timezone manually
(Tools/Options/Timezones).)

The guessed timezone is used as the default timezone for new events for new
users who have not set the timezone manually.  It is better to use the most
up-to-date version of the timezone, not a particular historical version of the
timezone, so please leave off the prefix "/mozilla.org/20050126_1/".
The file is up to date, but I only keep L10n updated in MOZILLA_1_8_BRANCH, since it is where Calendar products are being released from, and it is a bit easier for me to do it just on 1.8.

http://mxr.mozilla.org/l10n-mozilla1.8/source/es-ES/calendar/chrome/calendar/calendar.properties#123

I could try to keep also trunk updated, but I'd rather do it only if it is really needed. Is it needed?
Ok, good, sorry I didn't check the 1.8 branch.  As far as I know there is no impending release from trunk, but more people have started trying the trunk Lightning nightlies since the first Thunderbird 3 alpha was released, and keeping them in sync helps cut down on error reports.
Blocks: 450589
No longer blocks: 450589
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; is-IS; rv:1.9)
> Gecko/2008052906 Firefox/3.0
> Build Identifier: trunk
> 
> likelyTimezones should be an Olson ZoneInfo id.  Suggested change:
> 
> -likelyTimezone = /mozilla.org/20050126_1/Europe/Madrid
> +likelyTimezone = Europe/Madrid
> 
> (for travelers it may be helpful to add additional cities such as in en-US)
>


Now that main focus is in trunk (actually, at this moment in Gecko 1.9.1 branch), this is fixed:

http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/es-ES/file/db27d49f88e0/calendar/chrome/calendar/calendar.properties#l131

I've just created a new profile with a Sunbird 1.0pre nightly and it has proposed Europe/Madrid as default timezone, so it seems to work OK.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.