time durations and I18N.
Justin Dolske
<video>, and am wondering if the format/value needs localized...
Traditional timestamps ("June 3rd", "2:31pm", "1/2/2003", etc) clearly
need localized strings/formats, but it's not clear to me if time
durations do. For example, consider when the user is watching a video
that's 4 minutes and 56 seconds long, and it's currently playing at the
1 minute and 23 seconds mark. This is typically shown as something like
"1:23" in one widget and "4:56" somewhere else, or together as "1:23 /
4:56". Localizable, or not?
I'm also pondering if it could be clearer to indicate the actual scale
of times... Is "1:23" under 2 minutes, or over an hour? That always bugs
me. There's no space for a string like "1 hour and 23 minutes", although
abbreviating the scale as "1m23s" and "1h23m" might work. But what
should that look like in non-english locales? Also, I happen to notice
that "hour, minute, second" is "stunde, minute, sekunde" in german, so
"1s23m" vs "1m23s" might still be slightly ambiguous (and "1s23m00s"
looks like a mess).
Justin
Anas Husseini
>
> (...)
together as "1:23 / 4:56". Localizable, or not?
Yes, it is localizable, at least for RTL languages (like Arabic, Hebrew,
Persian, etc). It should appear as "4:56 \ 1:23" as long as the remaining
context is localized.
I'm also pondering if it could be clearer to indicate the actual scale of
> times... Is "1:23" under 2 minutes, or over an hour? That always bugs me.
> There's no space for a string like "1 hour and 23 minutes", although
> abbreviating the scale as "1m23s" and "1h23m" might work. But what should
> that look like in non-english locales? Also, I happen to notice that "hour,
> minute, second" is "stunde, minute, sekunde" in german, so "1s23m" vs
> "1m23s" might still be slightly ambiguous (and "1s23m00s" looks like a
> mess).
>
> Justin
>
Why not using the long format "1:23:50" then? Alternatively, you can use
other abbreviations like: 1 50' (1 hour 50 minutes), 2' 30'' (2 minutes 30
seconds).
Regards
- Anas
--
Experience is something you don't get until just after you need it.
Axel Hecht
progress meter for RTL builds. What did we end up with?
I'd argue that the order of shown time and total time should match the
progress meter.
I'm not sure if hours vs minutes is much of a problem, though triple
number display would solve it easily.
Does this have an impact on a11y? Not sure if there's something to team
up between a11y and l10n.
Axel
Ehsan Akhgari
On Mon, Mar 16, 2009 at 1:38 PM, Axel Hecht <l1...@mozilla.com> wrote:
> I know that we already had a discussion about what to do with the progress
> meter for RTL builds. What did we end up with?
It was decided to keep the progress meter for RTL build from left to
right like the rest of the locales.
> I'd argue that the order of shown time and total time should match the
> progress meter.
Seems reasonable.
--
Ehsan
<http://ehsanakhgari.org/>
Anas Husseini
> It was decided to keep the progress meter for RTL build from left to
> right like the rest of the locales.
If that's so then no need for reversing the order for RTL languages.
> I'd argue that the order of shown time and total time should match the
> > progress meter.
>
>
> Seems reasonable.