Yes it is... On 9/11/12 11:26 PM, "Filip Maj" <f...@adobe.com> wrote:
>A bunch of people from the list will be at PhoneGap Day EU, if that's what >you're talking about? > >On 9/11/12 2:15 PM, "Giorgio Natili" <g.nat...@gnstudio.com> wrote: > >>I want to move on... I need some advice, someone of you will be at the >>phonegap dev day next Friday? >> >>On 9/6/12 10:44 PM, "Giorgio Natili" <g.nat...@gnstudio.com> wrote: >> >>>Hi, >>> >>>I haven't forgot this e-mail... I will take a look during this weekend! >>> >>>Giorgio >>> >>>On 8/27/12 8:02 PM, "gtan...@gmail.com" <gtan...@gmail.com> wrote: >>> >>>>Feel free to ping me for any jasmine to qunit questions as I did most >>>>of >>>>the port of mobile-spec and cordova.js >>>>Sent on the TELUS Mobility network with BlackBerry >>>> >>>>-----Original Message----- >>>>From: Michael Brooks <mich...@michaelbrooks.ca> >>>>Sender: mikeywbro...@gmail.com >>>>Date: Mon, 27 Aug 2012 10:42:21 >>>>To: <callback-dev@incubator.apache.org> >>>>Reply-To: callback-dev@incubator.apache.org >>>>Subject: Re: Globalization Plugin >>>> >>>>Hi Giorgio, >>>> >>>>Thanks a bunch for volunteering to look at porting the QUnit tests to >>>>Jasmine! >>>> >>>>Android: >>>>https://github.com/phonegap/phonegap-plugins/blob/master/Android/Global >>>>i >>>>z >>>>a >>>>tion/globalization.tests.js >>>>BlackBerry: >>>>https://github.com/phonegap/phonegap-plugins/blob/master/BlackBerry/Glo >>>>b >>>>a >>>>l >>>>ization/globalization.tests.js >>>>iOS: >>>>https://github.com/phonegap/phonegap-plugins/blob/master/iOS/Globalizat >>>>i >>>>o >>>>n >>>>/globalization.tests.js >>>> >>>>In the end, we should have one set of JavaScript tests that is run >>>>against >>>>all three platforms (ala cordova-js and mobile-spec). >>>> >>>>Michael >>>> >>>>On Sun, Aug 26, 2012 at 6:05 AM, Giorgio Natili >>>><g.nat...@gnstudio.com>wrote: >>>> >>>>> 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_dra >>>>>f >>>>>t >>>>> >>>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) >>>>> >> >>>>> > >>>>> >>>>> >>>>> >> >> > >
