On 12/4/15 3:33 PM, Tim Guan-tin Chien wrote:
Hi,
There is DOMApplication#getLocalizedValue() implemented in bug 1118946,
but when working on bug 1216896 I realized what we really need is magic
l10nIds for application names -- right now both System app and Settings
app contain non-trivial logic monitoring locale change and application
name/label updates -- I think it would be a lot easier if the
application logic only cares about l10nId and let mozL10n handle the
display and update like other locale strings.
Does that make sense? If so I could file a bug and maybe implement it.
Tim
l10nIds only make sense within an l10n context, so we'd need a magic
context. Given that app manifest localization is per app, I'd even make
that a context per app, and not a context for all apps.
Given the narrow use case, I don't think this should be in l10n.js,
really. Nothing against having that code path in shared/, obviously.
My suspicion is that we'll not win a lot by exposing this code behind a
mocked l10n API, tbh.
Axel
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
