Doug,
do you think we should create a new list and move this discussion
there? Or should we use one of the existing i18n lists?
If we do move this discussion off the webapps list, we may lose some
audience/expertise...
If nobody objects, we (Google) would like to take this discussion to
Hi,
we've updated the API proposal (at
http://docs.google.com/Doc?id=dhttrq5v_0c8k5vkdh).
We've covered most of the comments related to other APIs, including CommonJS.
Could you take another look? (you can leave comments in the document
or post them back to this thread)
Regards,
Nebojsa
Hi, Robin-
Robin Berjon wrote (on 4/27/10 12:21 PM):
On Apr 27, 2010, at 18:13 , Phillips, Addison wrote:
A project to implement this could go quite fast, I think, but would
require agreement by the major browser vendors and a place to do
the work. We could do this at W3C, but I think ECMA
On Tue, Apr 27, 2010 at 6:38 AM, Robin Berjon ro...@berjon.com wrote:
Hi,
On Apr 26, 2010, at 20:49 , Nebojša Ćirić wrote:
We have a first draft at
http://docs.google.com/Doc?id=dhttrq5v_0c8k5vkdh (it has view/edit
permissions).
That's interesting; personally I agree that this would be
; _?= 申政湜)
Cc: Phillips, Addison; marc...@opera.com; Nebojša Ćirić; public-
webapps WG; public-i18n-c...@w3.org
Subject: Re: Client side JavaScript i18n API
On Apr 27, 2010, at 00:11 , Jungshik Shin (신정식, 申政湜) wrote:
Yes, I agree. Now it's not just web sites but also local
apps/widgets
?q22jungshik_shin_=28=ec=8b=a0=ec=a0=95=ec=8b...@poing.nachbaur.com,
_?= 申政湜); marc...@opera.com; Nebojša Ćirić; public-webapps WG;
public-i18n-c...@w3.org
Subject: Re: Client side JavaScript i18n API
Referring to the process:
Trying to get effective and useful internationalization supported
On 26.4.2010 21.49, ext Nebojša Ćirić c...@chromium.org wrote:
We have a first draft at
http://docs.google.com/Doc?id=dhttrq5v_0c8k5vkdh (it has view/edit
permissions).
It's describes a small subset of final API we intend to implement.
We've picked date/time formatting and collation as must
Hi,
On Apr 26, 2010, at 20:49 , Nebojša Ćirić wrote:
We have a first draft at
http://docs.google.com/Doc?id=dhttrq5v_0c8k5vkdh (it has view/edit
permissions).
That's interesting; personally I agree that this would be very useful in the
browser. Small note: the API seems overly verbose at
On Apr 27, 2010, at 00:11 , Jungshik Shin (신정식, 申政湜) wrote:
Yes, I agree. Now it's not just web sites but also local
apps/widgets/browser extensions written in HTML/JS/CSS are affected.
As a side note it's interesting to note that you're taking widgets into
account, I didn't know you were
; Nebojša Ćirić; public-
webapps WG; public-i18n-c...@w3.org
Subject: Re: Client side JavaScript i18n API
On Apr 27, 2010, at 00:11 , Jungshik Shin (신정식, 申政湜) wrote:
Yes, I agree. Now it's not just web sites but also local
apps/widgets/browser extensions written in HTML/JS/CSS are
affected
Hi,
On Apr 27, 2010, at 18:13 , Phillips, Addison wrote:
A project to implement this could go quite fast, I think, but would require
agreement by the major browser vendors and a place to do the work. We could
do this at W3C, but I think ECMA should be involved from early on.
In general a
On Apr 26, 2010, at 11:38 , Marcos Caceres wrote:
2010/4/23 Nebojša Ćirić c...@chromium.org:
We would like to propose an API for locale-based collation,
date/number formatting, ... Does anybody else think this would benefit
the authors?
We would be happy to answer questions to what
.org
Subject: Re: Client side JavaScript i18n API
On Apr 26, 2010, at 11:38 , Marcos Caceres wrote:
2010/4/23 Nebojša Ćirić c...@chromium.org:
We would like to propose an API for locale-based collation,
date/number formatting, ... Does anybody else think this would
benefit
the authors
We have a first draft at
http://docs.google.com/Doc?id=dhttrq5v_0c8k5vkdh (it has view/edit
permissions).
It's describes a small subset of final API we intend to implement.
We've picked date/time formatting and collation as must have for the
first iteration.
We feel there are, at least, two open
14 matches
Mail list logo
