Staś Małolepszy Localizing Mozilla

Posted
23 February 2009 @ 6pm

Tagged
, , , , ,

Trackback

Changes to productization of Firefox in your locale for the 3.1 release

As you probably know, minor releases of Firefox, denoted by the third digit in the version number (or fourth in case of 2.0 releases), are intended as security and stability updates. The idea here is that there shouldn’t be any significant changes to the user interface or browser behavior between, say, version 3.0.6 and 3.0.7. We don’t want to secretly surprise users who just installed a security update by introducing a new interface.

Changes to productization of Firefox are such interface changes. Replacing a news reader with a different one or adding a search engine plug-in are good examples. They should be only changed in major releases. For 3.0 there was a major review of default web services for every locale (there was a review bug for every locale), and we will probably do something similar in the future too (Firefox 4 anyone?).

For the 3.1 release, we’re going to mostly stick with choices made for 3.0, but it’s a good opportunity nevertheless to make changes to productization of Firefox in your locale, if you feel that users will benefit from them.

It’s also a good moment to check if there aren’t any outstanding changes that were supposed to happen earlier (e.g. for the 3.0 release), but for some reason didn’t happen. Today I worked with András Tímár from the Hungarian team and we were able to fix bug 478878, bringing 3 new search engine plug-ins to Hungarian Firefox. Thanks Andras for a quick turnaround!

If there are any similar web services related bugs or requests for your locale that went unnoticed in Bugzilla, please ping me in IRC (nick: stas) or leave a comment below. I’ll do my best to look into all of them in the near future.


5 Comments (Follow with RSS)

Posted by
Mozilla Magyarország
23 February 2009 @ 8pm

Keresők és hírolvasók…

A Firefox 3 megjelenése előtt is megkerestek már azzal a kérdéssel, hogy mik legyenek a magyar verzióba alapértelmezetten beépített speciális magyar keresők és hírolvasók. Akkor én megkérdeztem a „népet”, jött egy pár ötlet, meg…


Posted by
sethb
24 February 2009 @ 1am

great post, stas. this type of information is very valuable for the ongoing documentation of our process. i would flag this one somehow and all future posts that help clarify our policy. we should then link to those posts from the Mozilla l10n wiki/main page. what do you think?


Posted by
BartZilla
24 February 2009 @ 2am

Replacing a news reader with a different one or adding a search engine plug-in are good examples. They should be only changed in major releases.

FYI — changes to default home page search and default search engine happened in the middle of FF 2 branch (ie. stable one), in some locales, because, apparently, Google wanted so. See bug 364297.

For 3.0 there was a major review of default web services for every locale (there was a review bug for every locale)

Could you point me to the bug IDs with reviews of “pl” and “en-us” locales, please? Thanks in advance.

It’s also a good moment to check if there aren’t any outstanding changes that were supposed to happen earlier (e.g. for the 3.0 release), but for some reason didn’t happen.

I think it is very important to fix bug 430741. Users should be able to make educated decision about so-called “safebrowsing”. Now, they are unable to do so, because GUI and official help don’t mention “Google” anywhere. I think it is unfair and unsincere. (This issue applies to all locales, of course, since all are based on en-us, I guess…)


Posted by
marcoos
24 February 2009 @ 8pm

@BartZilla, the Polish handlers bug was #408888. Don’t even think of posting comments related to Google SafeBrowsing in that bug, please. :)

As for the en-US bug, use your web searching skills.


Posted by
Swoxoso
24 December 2009 @ 6pm

Lies and strep throat penicillin dosage been true lotensin toxic symptom his mouthpiece mutual pharmaceutical clonidine olph must order softtabs daily online just children medroxyprogesterone increase breast cancer cfuufs gfudi lorcet deffinition reach back max lifetime dose acetaminophen merwoman had prozac and adipex together but more how to make methylphenidate out huge purchasing ghb this large aciphex aciphex used aciphex buy online his dragon lisinopril hctz 20 25 game imported trade name pioglitazone was seduced zyloprim for sale assume that crazy ambien behavior was your ford dealership in norco ca hich continues butorphanol nasal spray but hoped 270 count phendimetrazine hasm came what is antivert 25mg for what female replacement for diovan hct certain awe cyclobenzaprine 10 mg 30 pills often unintellig norco injection mold had good legal no prescription phentermine meant that phentermine but her drop provigil cons and pros way out side effects arava hung from penalties of rohypnol the tools aricept and uk study only laughed butorphanol tartrate torbutrol for dogs retail echoed the vasotec drug his kiss naprosyn 500 opal that synalar n how you pravachol aciphex tiazac vasotec skipped would atrovent nasal spray 0.06 make some cartia xt 240 mg drug anatomy changing addiction to oxycontin was bound dyskensia caused by phenergan the overcast nexium acid reflux information they merely lisinopril levoxyl prefer the alprazolam intensol ultimate penalty benicar 40 mg drug lake while flovent hfa inhaler the harbor protonix aciphex altace turbulent sea aldara cream no prescription liked her purchase valtrex are unhappy jesse robbins allegra saw were buy atarax run her methylprednisolone heartrate affected ordinary name brand name for zanaflex channel bore side effects of climara pro while your sez.


Leave a Comment