I have some questions about add-on SDK's l10n support plan.
Are we going to release SDK 1.0 final without any l10n support?
Is there any update about common pool support?
After the SDK 1.0 release, we want to promote SDK for developers more.
Do you have any idea how we should talk about l10n support then?
Add-ons SDK 1.0 release is planed for June 8:
https://wiki.mozilla.org/Labs/Jetpack/SDK/1.0
Localization support with common-pool service is implemented in sdk 0.5
https://bugzilla.mozilla.org/show_bug.cgi?id=549315
but pulled away from initial beta:
https://bugzilla.mozilla.org/show_bug.cgi?id=612770
I couldn't find future plan.
AFAIK, only the way to support l10n is like this:
http://erikvold.com/blog/index.cfm/2011/2/18/restartless-firefox-addons-part-4-localization-l10n
https://github.com/erikvold/restartless-restart-ffext/blob/master/src/includes/l10n.js
# note: his script have an issue about ab-CD type dir support
# https://github.com/erikvold/restartless-restart-ffext/issues/36
If we cannot prepare common-pool nor l20n support in the near future,
should we add l10n support like this? This type of l10n support will
provide backward compatibility too and easy to migrate existing add-ons
from xul to jetpack I believe.
# should I file a bug?
Unfortunately, we're are going to release SDK 1.0 final without any l10n
support, as we were unable to get the l10n feature ready in time, and we
decided to ship 1.0 without it.
> Is there any update about common pool support?
Several of us (gandalf, Wil Clouser, fligtar, etc.) met recently and
hashed out a plan for integrating common pool into the SDK-based addon
development and distribution process. I'm going to create a feature page
<https://wiki.mozilla.org/Feature_Page_Structure> for it sometime in the
next two weeks.
> After the SDK 1.0 release, we want to promote SDK for developers more.
> Do you have any idea how we should talk about l10n support then?
We should be open with developers about the current status of l10n
support and our future plans, which is to prioritize the implementation
of common-pool-based l10n support. More information will be available in
a few weeks, once we've started the post-1.0 planning process.
-myk
Thanks sharing current status.
I'll see the feature page and post-1.0 plan when it's created.
I hope l10n support will be prioritized as P1. It's regression from XUL
and it's the API I've asked about mostly by Japanese developers.
If we cannot get support for common-pool nor l20n in the near future,
my suggestion is to support simple API to read properites (and dtd?)
file within the add-on.
# IMO it is useful API to migration from XUL easier
We'll tell developers to use l10n.jp of restartless-restart untill we
have build-in l10n support by addon-kit.