Cool features and localization
Thanks to Mozilla Labs awesome hackers, we can now enjoy restartless extensions Ã la Jetpack, and sure this is a cool feature.
One of the most recent extensions of this kind from the Prospector series, is Query Stats. I noticed there are some interface strings bundled in an innerHTML to be found in the bootstrap.js file
Now my question is: how are we supposed to localize such an addon?
Is it worth doing it?
Yes, I know: Jetpacks and restartless addons have a very limited number of interface strings or no interface string at all, and Prospector series are mostly experimental, targeting the power user (though I suppose the more mainstream they are, the more useful data they can bring), so i18n may not seem necessary.
I would simply object that restartless addons will probably have a growing success in addons developers community, which is good. But restartless addons with important interface will surface (to me even limited interface is important, but this is another question).
The right moment?
One little flaw in development makes things more difficult afterwards: localization issues almost always came second as an annoying appendix for real core dev. Localization rises technical issues that should be taken into account right from the beginning of the devlopment process, otherwise it makes things much more complicated (think of the smart and tremendous localization efforts on Ubiquity in the past).
Who can help?
So I would suggest it is due time to think about i18n (hey l20n welcome too!) for this new and promising generation of addons.
Fortunately, and that is why I really love the Mozilla community, there are always brilliant minds who are one step ahead in development and conceive projects that tend to answer questions even before anyone think of asking them 😉
-Please let us know.