W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [widgets] Removed LocalizableString interface from Widgets API

From: timeless <timeless@gmail.com>
Date: Tue, 25 Jan 2011 17:55:06 +0200
Message-ID: <AANLkTimNRNmT=qx0EB4nfw32__xjhYVaT5ur3+TR6qAZ@mail.gmail.com>
To: Charles McCathieNevile <chaals@opera.com>
Cc: Marcos Caceres <marcosc@opera.com>, Robin Berjon <robin@berjon.com>, public-webapps WG <public-webapps@w3.org>
On Fri, 21 Jan 2011 19:32:57 +0100, timeless <timeless@gmail.com> wrote:
> a nokia maps application uses json for localization and could be
> easily ported to the widget format.

On Fri, Jan 21, 2011 at 9:09 PM, Charles McCathieNevile
<chaals@opera.com> wrote:
> Could you automatically port it?

The structure is:

html/mapplets/<component>/i18n/<locales> ~8k per locale per component
html/mapplets/<stuff> [2.5mb]
html/medos/i18n/<locales> ~64k per locale, ~1mb for however many locales total
html/medos/images/<stuff> ~680k
html/index.html ~948k
html/ [6.2mb inclusive]

the index.html file uses relative refs, so yeah, it'd probably be
possible for *someone* - *not* me to automatically port it. I really
don't have time to do this. It should be possible for anyone w/ an
n900 to look at /usr/share/nokia-maps and investigate it.

the fact that each component is using its own subdirectory thing is
moderately annoying, but fixing the include paths wouldn't be too
painful for an automated tool.

fwiw, my understanding is that nokia-maps works more or less the same
way on maps.ovi.com, which means someone feeling adventurous could
probably try to do it from there, but since i like my product, i'd
request someone be nice and buy an n900 instead of slurping ovi maps
;-).
Received on Tuesday, 25 January 2011 15:55:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT