On Fri, 21 Jan 2011 19:32:57 +0100, timeless 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
wrote:
> Could you automatically port it?
The structure is:
html/mapplets//i18n/
On Fri, 21 Jan 2011 19:32:57 +0100, timeless wrote:
note that you don't *need* to duplicate html files.
the format allows for one to have json based localizations.
a nokia maps application uses json for localization and could be
easily ported to the widget format.
Could you automatically po
note that you don't *need* to duplicate html files.
the format allows for one to have json based localizations.
a nokia maps application uses json for localization and could be
easily ported to the widget format.
i can't do it publicly because i don't own/manage the code.
On 1/21/11 11:48 AM, Robin Berjon wrote:
On Jan 19, 2011, at 19:39 , Marcos Caceres wrote:
On 1/17/11 1:56 PM, Robin Berjon wrote:
Nothing in P+C is super-hard to implement, but the l12n parts
account for most of the complexity,
I've only implemented the i18n stuff in Javascript, but I didn't
On Jan 20, 2011, at 22:10 , Marcos Caceres wrote:
> On 1/20/11 6:48 PM, Arthur Barstow wrote:
>> If people have "spare" time for the widgets specs, it seems like that
>> time would be better spent moving the existing specs forward.
>
> Agree. Just testing the waters to see if any other members wer
On Jan 19, 2011, at 19:39 , Marcos Caceres wrote:
> On 1/17/11 1:56 PM, Robin Berjon wrote:
>> Nothing in P+C is super-hard to implement, but the l12n parts account
>> for most of the complexity,
>
> I've only implemented the i18n stuff in Javascript, but I didn't find it
> particularly hard (rel
On 1/20/11 6:48 PM, Arthur Barstow wrote:
On Jan/20/2011 12:42 PM, ext Scott Wilson wrote:
On 19 Jan 2011, at 18:39, Marcos Caceres wrote:
On 1/17/11 1:56 PM, Robin Berjon wrote:
On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
But as I said, if we split the specs into pieces I'm happy!
I'
On Jan/20/2011 12:42 PM, ext Scott Wilson wrote:
On 19 Jan 2011, at 18:39, Marcos Caceres wrote:
On 1/17/11 1:56 PM, Robin Berjon wrote:
On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
But as I said, if we split the specs into pieces I'm happy!
I'm kind of agnostic on that one. Might be OK,
On 19 Jan 2011, at 18:39, Marcos Caceres wrote:
> On 1/17/11 1:56 PM, Robin Berjon wrote:
>> On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
>>> On 1/10/11 4:28 PM, Robin Berjon wrote:
>>> I would argue that it's not particularly complicated to implement,
>>> and we are seeing it used in Opera
On 1/17/11 1:56 PM, Robin Berjon wrote:
On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
On 1/10/11 4:28 PM, Robin Berjon wrote:
I would argue that it's not particularly complicated to implement,
and we are seeing it used in Opera extensions: we have extensions
in 15 languages as of today in ou
On Mon, 17 Jan 2011 13:56:43 +0100, Robin Berjon wrote:
On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
On 1/10/11 4:28 PM, Robin Berjon wrote:
On Jan 10, 2011, at 16:00 , Marcos Caceres wrote:
I would be happier if we could break up the Widget P&C spec into:
* Packaging (zip only require
On Jan 11, 2011, at 08:24 , Marcos Caceres wrote:
> On 1/10/11 4:28 PM, Robin Berjon wrote:
>> On Jan 10, 2011, at 16:00 , Marcos Caceres wrote:
>>> I would be happier if we could break up the Widget P&C spec into:
>>>
>>> * Packaging (zip only requirements) * XML Configuration for
>>> widgets * X
On 1/10/11 4:28 PM, Robin Berjon wrote:
On Jan 10, 2011, at 16:00 , Marcos Caceres wrote:
I would be happier if we could break up the Widget P&C spec into:
* Packaging (zip only requirements) * XML Configuration for
widgets * XML Localization and Folder-based Localization
I could live with th
On Jan 10, 2011, at 16:00 , Marcos Caceres wrote:
> I would be happier if we could break up the Widget P&C spec into:
>
> * Packaging (zip only requirements)
> * XML Configuration for widgets
> * XML Localization and Folder-based Localization
I could live with that. It's not that I'm against l
On 1/10/11 3:39 PM, Robin Berjon wrote:
On Jan 10, 2011, at 15:33 , Marcos Caceres wrote:
On 1/10/11 2:27 PM, Arthur Barstow wrote:
Hi Marcos - have you checked with the I18N Core WG? My recollection is
this functionality was added to the Widgets API spec based on their LC
comments.
I'll cont
On Jan 10, 2011, at 15:33 , Marcos Caceres wrote:
> On 1/10/11 2:27 PM, Arthur Barstow wrote:
>> Hi Marcos - have you checked with the I18N Core WG? My recollection is
>> this functionality was added to the Widgets API spec based on their LC
>> comments.
>
> I'll contact them soon for further disc
On 1/10/11 2:27 PM, Arthur Barstow wrote:
Hi Marcos - have you checked with the I18N Core WG? My recollection is
this functionality was added to the Widgets API spec based on their LC
comments.
I'll contact them soon for further discussion on use cases. If a strong
case is made for requiring t
Hi Marcos - have you checked with the I18N Core WG? My recollection is
this functionality was added to the Widgets API spec based on their LC
comments.
-Art Barstow
On Jan/5/2011 6:39 AM, ext Marcos Caceres wrote:
I have removed LocalizableString interface from the Widgets API
specification b
On 1/5/11 1:47 PM, Charles McCathieNevile wrote:
On Wed, 05 Jan 2011 12:39:05 +0100, Marcos Caceres
wrote:
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface was to allow a developer to i
On Wed, 05 Jan 2011 12:39:05 +0100, Marcos Caceres
wrote:
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface was to allow a developer to interrogate an
attribute of the widget object
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface was to allow a developer to interrogate an
attribute of the widget object to find out what language that attribute
may be written in (if
21 matches
Mail list logo
