Hi All, Where are the Qunit tests? I would like to take a look and check if it's possible accordingly to my schedule raise my hand to be a volunteer for the porting to jasmine.
Giorgio On 8/26/12 2:30 AM, "Shazron" <shaz...@gmail.com> wrote: >That will get us there partially (xml:lang), we still need the >Globalization functions to determine currency, format and parse >numbers, dates etc. according to the user's locale. > >On Sat, Aug 25, 2012 at 3:52 PM, Filip Maj <f...@adobe.com> wrote: >> Want to point out that config.xml has a basic localization approach via >> xml:lang attribute. You can then point to specific content (such as >> starting pages) based on language. >> >> http://www.w3.org/TR/widgets/#the-xml:lang-attribute >> >> >> On 8/22/12 11:56 AM, "Brian LeRoux" <b...@brian.io> wrote: >> >>>Lunny just pointed out that there is standardization effort in ES6: >>> >>>http://wiki.ecmascript.org/doku.php?id=globalization:specification_draft >>>s >>> >>>Pretty intense. But I suppose thats what we'd gun for. Cordova Core >>>are polyfills. >>> >>>On Wed, Aug 22, 2012 at 11:48 AM, Brion Vibber <br...@pobox.com> wrote: >>>> On Wed, Aug 22, 2012 at 11:40 AM, Michael Brooks >>>> <mich...@michaelbrooks.ca>wrote: >>>> >>>>> 1. Follows a W3C standard... when there is a standard. >>>>> >>>>> I've done a brief scan, but can't find any W3C standards around >>>>> globalization / localization. Has anyone else found anything? >>>>> >>>> >>>> I don't think there really is much standardish, other than the current >>>> language being set in navigator.language and local date formats being >>>> output by Date. >>>> >>>> For our usage in Wikipedia's apps, just getting the current language >>>>code >>>> is all we use Globalization for -- navigator.language is hardcoded to >>>> English on Android, making it unusable. >>>> >>>> A more limited plugin that only fetches the locale language (and >>>>perhaps >>>> overrides navigator.language?) would do what we need and might not add >>>>much >>>> burden on other platforms, especially if they already implement >>>> navigator.language correctly. The other stuff is gravy if it's >>>>available >>>> though! >>>> >>>> -- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org) >> >
