Has anyone tried doing Locale.setDefault to circumvent this problem?
On Aug 5, 7:15 am, "{ Devdroid }" <webnet.andr...@gmail.com> wrote:
> On 3 August 2010 13:30, Mark Murphy <mmur...@commonsware.com> wrote:
>
> >> We got same problem on Desire, so it looks like device firmware issue.
>
> > Somebody with a Desire should create a sample project demonstrating
> > the error and open an issue on b.android.com -- not to fix the problem
> > (that's an HTC issue), but to get a new CTS test case added to prevent
> > this problem in the future. Plus, given the test project, we can try
> > other HTC devices and see if the problem exists on the EVO,
> > Incredible, etc.
>
> Code is is quite simple.
>
> Date date = ....
>
> SimpleDateFormat formatter = new SimpleDateFormat();
>
> formatter.applyLocalizedPattern( "EEEE" );
> DDDD = formatter.format( date );
>
> the issue is with EEEE, EEE, MMMM and MMM (in general all localised)
>
> But what I now spotted, that this code no longer works on 1.5
> emulator, even it worked yesterday. Quite impressive - we will
> investigate the culprit.
>
> Work around is simple, just instance SimpleDateFormat with specified
> locale (i.e. SimpleDateFomat("", Locale.xxxx) but this is not what
> shall be done in the first place. Anyone else facing this?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
