time.parse3339 or time.format3339 are using the current locale

Bug #1264499 reported by Stefan Hammer on 2013-12-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tomdroid
Fix Released
High
Unassigned

Bug Description

Unfortunately we are affected from this android bug:
https://code.google.com/p/android/issues/detail?id=54708

... which leads to constant crashing when arabic is set as locale.
The time string (3339) is alway formatted in arabic and cannot be parsed any more.

A workaround would be to change the loale before each timeparsing or formatting to US and change it back afterwards.

Changed in tomdroid:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Stefan Hammer (j-4)
milestone: none → 0.7.5
Changed in tomdroid:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers