No subject

Thu Feb 11 18:09:36 PST 2010

data needed for collation process". =C2=A0Given that this data is so h=
requiring all JS engines to include it for all locales ever invented<br>
doesn&#39;t sound good.<br></blockquote><div><br></div><div>I think it&#39;=
s more the combination of algorithm complexity and data size that prevents =
current implementation (closure, dojo) to offer collation. Also, most of th=
e locales have fairly small data set needed for the collation (couple of ki=
<div>The biggest tables are for CJK, but they can be pruned down (with loss=
 of features).</div><div><br></div><div>Android for example uses ICU in pru=
ned down form - it supports only subset of all ICU locales, and I think tha=
t&#39;s a usual approach for other features in smartphone industry (includi=
ng fonts).</div>
<div><br></div><div>Most of the browsers already have full access to the co=
llation data (IE through Windows API, Chrome through ICU...), so they would=
n&#39;t grow in size, if JS engine were to use that data.</div><div><br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex;">
How about a system where locales can be described in a JSON based<br>
format and loaded into the running JS implementation?<br></blockquote><div>=
<br></div><div>There are some projects underway that would host/expose CLDR=
 data as JSON objects, but I am afraid that would bring more problems to th=
e proposal:</div>
<div><br></div><div>1. We would need to agree on what goes into JSON (yet a=
nother standard?)</div><div>2. How would one use JSON data (rewrite parts o=
f ICU or Windows i18n calls to use JSON?)</div><div>3. Where to host JSON d=
ata, what if the user is offline?</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">
A positive thing about the proposal: =C2=A0It doesn&#39;t, if I have unders=
it correctly, have a concept of a context-global locale setting. =C2=A0 No<=
global state? =C2=A0I like this.<br></blockquote><div><br></div><div>Yes, i=
t doesn&#39;t have global locale. You are free to create as many locales pe=
r, say web page, and use them to sort, format and parse.</div><div><br></di=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
2010/6/9 Neboj=C5=A1a =C4=86iri=C4=87 &lt;<a href=3D"mailto:cira at
">cira at</a>&gt;:<br>
<div><div></div><div class=3D"h5">&gt; We would like to propose adding i18n=
 API to the EcmaScript standard (either<br>
&gt; as standard library or part of the language).<br>
&gt; Our current proposal is at=C2=A0EcmaScript i18n API=C2=A0(open to edit=
s). We will<br>
&gt; migrate the document to the proper strawman wiki page as soon as we ge=
&gt; access to it.<br>
&gt; We feel that our current proposal represents the minimum set of object=
s and<br>
&gt; methods needed, but we could=C2=A0certainly=C2=A0extend it to cover nu=
&gt; formatting/parsing and possibly calendar support. Our main goal was to=
&gt; with minimal proposal and get early feedback from the community.<br>
&gt; Please leave feedback to the proposed API either inside of the documen=
t or<br>
&gt; post back to the mailing list.<br>
&gt; --<br>
&gt; Neboj=C5=A1a =C4=86iri=C4=87<br>
&gt; i18n team,<br>
&gt; Google Inc.<br>
</div></div><div><div></div><div class=3D"h5">&gt; ________________________=
&gt; es-discuss mailing list<br>
&gt; <a href=3D"mailto:es-discuss at">es-discuss at</a><b=
&gt; <a href=3D"" target=3D"_bl=
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Neboj=C5=A1=
a =C4=86iri=C4=87<br>


More information about the es-discuss mailing list