On Monday, May 4, 2015 at 7:59:22 AM UTC-4, Staś Małolepszy wrote: > Is this something that we already use in Gaia? I agree it would be very > helpful to have for many use-cases, for instance here: > > https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/settings/layout_item_view.js#L263-L291 > https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/locales/keyboard.en-US.properties#L79 > > Should we track this as a feature to add to l10n.js on current master? > That might be great to introduce indeed. It will require some work in the > Resolver, too.
So, that depends. On one hand, I can see us doing that, but on the other I think I'd like to focus on migrating people to the new API as soon as possible. My idea was to land l20n parser that matches current AST perfectly ASAP and encourage people to start using l20n file format with current l10n.js, and introduce the new features with the new API, basically encouraging to migrate to the new l10n.js to use them. I wouldn't be opposed to backport some new features to the current l10n.js, especially if we are some time away from being able to start using new API, but I'd like to first land it without them to minimize the risk of regressions on migration. zb. _______________________________________________ tools-l10n mailing list [email protected] https://lists.mozilla.org/listinfo/tools-l10n
