Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of mikeywbrooks@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
Sender: mikeywbrooks@gmail.com
In-Reply-To: <CC5FEAD8.458E2%g.natili@gnstudio.com>
References: 
 <CAE6O_-as5Md35UWDV8nNr-c3+Wr6aVF9UbAs_SiosjVdnomepA@mail.gmail.com>
	<CC5FEAD8.458E2%g.natili@gnstudio.com>
Date: Mon, 27 Aug 2012 10:42:21 -0700
Message-ID: 
 <CAP7NMPrbgOQE8E-pOnz2RB4GCbuZ_+CnW8Oo0CV+-6y0JFu6NA@mail.gmail.com>
Subject: Re: Globalization Plugin
From: Michael Brooks <michael@michaelbrooks.ca>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e0cb4e38531602f70304c842d9a8

--e0cb4e38531602f70304c842d9a8
Content-Type: text/plain; charset=ISO-8859-1

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/Globalization/globalization.tests.js
BlackBerry:
https://github.com/phonegap/phonegap-plugins/blob/master/BlackBerry/Globalization/globalization.tests.js
iOS:
https://github.com/phonegap/phonegap-plugins/blob/master/iOS/Globalization/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.natili@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" <shazron@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 <fil@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 <brion@pobox.com> wrote:
> >>>> On Wed, Aug 22, 2012 at 11:40 AM, Michael Brooks
> >>>> <michael@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)
> >>
> >
>
>
>

--e0cb4e38531602f70304c842d9a8--