Right. What I was suggesting was to try setting locale in order to
test the hypothesis that lack of a locale is causing the symptoms, vs,
eg, something broken in the date formatter logic. And it would
provide a circumvention for those who need one.
On Aug 6, 4:37 am, "{ Devdroid }" <webnet.andr...@gmail.com> wrote:
> On 5 August 2010 14:53, DanH <danhi...@ieee.org> wrote:
>
> > Has anyone tried doing Locale.setDefault to circumvent this problem?
>
> The problem is when you do not care what locale are set and simply
> want to use system-wide, not any particular one.
> Calling setDefault is same like passing locale to SimpleDateFormater
> constructor - you need to either specify locale or read system
> settings and pass that in hope it works. Since this is like blind fix
> it may or may not work but you still do not know what the culprit is.
--
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
