After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 341753 - download estimation should be use "nn:mm" not "nn.mm"
download estimation should be use "nn:mm" not "nn.mm"
Status: RESOLVED DUPLICATE of bug 337936
Product: epiphany
Classification: Core
Component: Downloads
2.14.x
Other Linux
: Normal trivial
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
: 554245 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-14 15:13 UTC by Sebastien Bacher
Modified: 2008-09-29 03:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2006-05-14 15:13:47 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/epiphany-browser/+bug/43627

"In the download manager, the time remaining is showing, for example, 00.09 (to indicate 9 seconds left). This should be 00:09. My locale is set properly to en_US:

$ echo $LANG
en_US.UTF-8

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL="
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-07-20 08:34:10 UTC
This seems a bit ambiguos:

From embed/downloader-view.c:305

static char *
format_interval (gint64 interval)
{
    int hours, mins, secs;

    hours = (int) interval / 3600;
    interval -= hours * 3600;
    mins = (int) interval / 60;
    interval -= mins * 60;
    secs = (int) interval;

    if (hours > 0)
    {
        return g_strdup_printf (_("%u:%02u.%02u"), hours, mins, secs);
    }
    else
    {
        return g_strdup_printf (_("%02u.%02u"), mins, secs);
    }
}


As you can see there can be a misreading if 3 minutes are shown as 03:00 and 3 hours are shown as 03:00.

I think bug #337936 is related and could be a solution for this.
Comment 2 Christian Persch 2006-07-20 11:06:49 UTC
Maybe we shouldn't be so specific anyway. The value is only a guesstimate, so we could do as HIG recommends:
"About 1.5 hours"
"About 35 minutes"
"About 40 seconds"
?
Comment 3 Diego Escalante Urrelo (not reading bugmail) 2006-07-20 11:13:02 UTC
I think it's ok to use 'relative' times, but instead of 1.5 hours i would say 1 and a half or 1:30 (1 and a half sounds better to me).
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2006-08-11 16:37:21 UTC
bug #337936 has a patch for this, it also hacks the ui a bit.
Maybe this should be marked as duplicate.
Comment 5 Reinout van Schouwen 2006-08-12 13:43:01 UTC
I'll mark it as a dependency for now.
Comment 6 Christian Persch 2007-05-30 11:11:41 UTC

*** This bug has been marked as a duplicate of 337936 ***
Comment 7 Thomas Koster 2008-09-29 03:07:46 UTC
*** Bug 554245 has been marked as a duplicate of this bug. ***