After hearing out Zibi's talk on L20n just now I realized what I am looking for is an declarative ID for application names (clarify the word "magic" here.)
With Zibi's example on Intl DOM (or IntlHelper) and Axel's comment I agree this is not the scope of L20n.js/L10n.js/mozL10n, so we should be looking at implementing another helper library to wrap around mozApps API to get this feature. Is that correct? Thanks! Tim On Sat, Dec 5, 2015 at 2:56 AM, Tim Guan-tin Chien <[email protected]> wrote: > No, Gaia & 3rd-party app names will continue be built and present on the > manifest, there should be no IDs added to the properties files -- I simply > need l10n.js to resolve the strings from app manifest (as opposed to > properties files). > > That said, I can see ManifestHelper already getting localized app names > through |mozL10n.qps| -- so localized app names are backed by mozL10n > already. > > (I am just lobbying for a arguably more convenient way to display them, by > assigning these strings with fake l10nIds.) > > > > On Sat, Dec 5, 2015 at 3:38 PM, Francesco Lodolo [:flod] <[email protected]> > wrote: >> >> Note that this will require changes to the conversion process. As far as I >> can tell, we only extract 'name' and 'description' from manifests. >> >> Francesco >> >> Localized strings will continue to live in the manifest. >> >> I was thinking about about have l10n.js to map constructed IDs like >> |app-name-app---keyboard-gaiamobile-org| to localized value in the manifest. >> >> (Surely under the hood, it would use Apps API to get the localized value >> from the manifest) >> >> >> On Sat, Dec 5, 2015 at 2:03 AM, Kevin Grandon <[email protected]> wrote: >>> >>> Where would the strings be defined? In the manifest or in the existing >>> properties files? >>> >>> If the strings can be defined in the property files (either in the >>> respective apps, or in the shared/ folder, then perhaps you can sanitize and >>> use the origin as a l10n id? >>> >>> Best, >>> Kevin >>> >>> On Fri, Dec 4, 2015 at 8:33 AM, Tim Guan-tin Chien <[email protected]> >>> 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 >>>> >>>> _______________________________________________ >>>> dev-fxos mailing list >>>> [email protected] >>>> https://lists.mozilla.org/listinfo/dev-fxos >>>> >>> >> >> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> >> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> > _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
