If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Absolute dates in download manager (about:downloads) are not localized (but in English)

NEW
Unassigned

Status

()

Core
Internationalization
5 years ago
5 years ago

People

(Reporter: aryx, Unassigned)

Tracking

Trunk
ARM
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Fennec native 14.0b1 build 3, Android 4.0.4 (stock), Google Nexus S

The download manager (about:downloads) uses unlocalized, English dates if it has to display an absolute date.

Steps to reproduce:
0. Launch a localized Firefox mobile.
1. Download something.
2. Go to the system settings, disabled retrieving date and time from the carrier network, increase by 2 days.
3. Go back to Firefox mobile's download manager and reload it.

Actual result:
A weekday will be displayed, written in English.

If you increase the date by more than a week, the month name will be English.
Yes, my Android is in German.

Comment 2

5 years ago
Thiyag, maybe this is a bug you'd like to look into.
This bug should be a duplicate of bug 702895. Even in web sites like addons.mozilla.org, the date (month) is in English. (I thought I had seen such a bug already filed, but am unable to find it.)
Sure, Margeret, I will take a look a this.

Aryx, I am not sure if we should dupe this bug with bug 702895, since this is native/downloads while that is xul/preferences, it might be better to get it fixed independently I would think?
It seems likely that something in Android or retrieving data from Android is broken.

Both the desktop release version and the android version use DownloadUtils.getReadableDates, but the latter one displays an English string.
bionic libc doesn't support localized string by setlocale() well.  nsDateTimeFormatUnix should use Java wrapper and use Java API.
Component: General → Internationalization
Product: Firefox for Android → Core
Version: Firefox 14 → Trunk
Duplicate of this bug: 810696
You need to log in before you can comment on or make changes to this bug.