- From: Marcos Caceres <w3c@marcosc.com>
- Date: Tue, 12 Mar 2013 09:18:49 +0000
- To: Janusz Majnert <j.majnert@samsung.com>
- Cc: public-sysapps@w3.org
On Tuesday, 12 March 2013 at 09:00, Janusz Majnert wrote: > Hi, > If I understand correctly, in Firefox OS the localised strings are in > the main manifest file, while in Widgets P&C and Google's format, > separate files are used? In W3C widgets they are in the same file, but you are correct that in Google's format it is in a separate file. > If so, I think Firefox OS model has the > advantage that for hosted apps the user gets localised UI (app name, > author etc) before actually installing the app. This makes hosting the > app a bit easier. This advantage comes at a cost (for packaged apps). The Google format allows for large scale localisation of applications - it also provides an i18n API for working with localised data that neither W3C widgets nor API FxOS provides. This is not a bad thing, as JS libraries can be used to fill this gap - you just don't get this functionality out of the box, like you do with Google's Apps. While developing W3C widgets, at least one large organisation raised concerns about not being able to split the localisation tasks across multiple files, as it made it harder for them to distribute the work of localising content to their localisation centres around the world (as everything is in one file).
Received on Tuesday, 12 March 2013 09:19:21 UTC