[mythtv-users] Watch Recordings doesn't list size of single recording
Roger Siddons
dizygotheca at ntlworld.com
Thu Dec 17 23:18:42 UTC 2015
On 17/12/15 01:56, Nicolas Riendeau wrote:
>
> I have a feeling that you are talking from a theming point of view and
> if so the situation is even worse than that...
>
Correct. Hika wanted to squeeze the duration into a smaller space.
> We use the Qt's translation framework and it cannot handle more than one
> plural per string so even if it was possible to use more than one
> variable (ie "%n" here) we would be unable to "translate" it as one
> string...
>
> I put "translate" in quotes here because even US English uses that to
> have proper handling of plurals
Exactly. Thus my speculation for 'translations' being the reason why it
is implemented as it is.
>
> But if we handle RTL like I have seen some software do there is a
> loooooot more work on the UI side needed to handle that...
>
I'm sure you're right!
>>
>> Given that the existing formats will remain, then adding window
>> attributes for the raw numbers would cover all eventualities.
>
> I am really bad at theming (which I think you are talking about), could
> you please explain what you mean by that?
>
As usual, choosing names is the hard part. But I would propose 3 new
attributes. For a 90 min recording;
durmin = "90"
durparthr = "1"
durpartmin = "30"
Then a themer could use templates to create variants of "1:30", "1h
30m", "1 hr 30 min", "90 min(s)" etc.
The only display it can't generate is "1 hour(s), 30 minute(s)", which
lentime already provides.
Note that the code in TVBrowseHelper (Live TV OSD ?) already formats
lentime as "1:30".
> I was thinking about something like adding short, medium, long, full
> date and time format (of course configurable on a per language basis).
> Each format producing a longer output than the preceding one. The user
> would choose her/his preferable format.
>
Sounds good, but in this case I think durations are separate to times.
More information about the mythtv-users
mailing list