Closed Bug 616377 Opened 15 years ago Closed 14 years ago

[Meta] Handle locales on Android

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
All
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: alexp, Unassigned)

References

Details

Locale-related C functions like setlocale and localeconv on Android are not implemented. Need some workaround.
Depends on: 610151, 544414
Depends on: 616378
Can everyone who has any info provide a feedback on this subject please? Which important areas are affected by the unimplemented locale-related functions in C-library on Android? Thanks.
Time zone is not detected correctly in JS. Is there a bug about this?
Depends on: 606074
(In reply to comment #2) > Time zone is not detected correctly in JS. Is there a bug about this? Bug 606074 is linked here.
I think we should decide on how to fix the broken stuff on a case by case basis. Do we use the C locale library functions on other platforms? (I think we do on Linux, not sure about others.)
(In reply to comment #4) > I think we should decide on how to fix the broken stuff on a case by case > basis. Yes, I'd prefer this approach as well. After some research on the subject (specifically setlocale bug 616378) it looks like we'll need to implement string formatting functions, which depend on the locale (at least strftime). It is possible, as locale info and related functions in Java layer are usable, but it will be a performance hit calling those functions through Android bridge, so this should be used only when really needed. That's why asked for a feedback - to find specific cases, which need to be fixed. Right now we already know about a couple of issues in JS (bug 544414 and bug 606074).
We've been shipping multilocale Android builds for a while now. Still an issue?
Looks like all real bugs were fixed, so we can close this Meta-bug now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Due to comment #7, I'll mark this bug as verified fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.