Per
https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Moodbar-feedback-response-summary/en
These messages are used on File description pages. See: TranscodeStatusTable.php
Version: master
Severity: normal
Description
Description
Details
Details
- Reference
- bz67960
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Use the relative time and duration formatting from core | mediawiki/extensions/TimedMediaHandler | master | +8 -54 |
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Invalid | None | T40638 [DO NOT USE] Interface messages needing rewording or documentation and other issues with existing messages [superseded by #Voice_&_Tone] | ||
| Open | TheDJ | T69960 Untranslatable timestamps in timedmedia-in-job-queue, timedmedia-started-transcode | ||
| Open | BUG REPORT | None | T69959 The "ago" mechanism is untranslatable due to sentence split | |
| · · · |
Event Timeline
Comment Actions
I think not yet... nobody ever looked into timestamps for real. Avoiding the "ago" mechanism is the first step.
Comment Actions
Change 977273 had a related patch set uploaded (by TheDJ; author: TheDJ):
[mediawiki/extensions/TimedMediaHandler@master] Use the relative time and duration formatting from core
Comment Actions
Change 977273 merged by jenkins-bot:
[mediawiki/extensions/TimedMediaHandler@master] Use the relative time and duration formatting from core
Comment Actions
I'm not entirely sure if this issue is fixed by using core's -ago construct. Do you know @Nikerabbit ?
Comment Actions
https://test.wikipedia.org/wiki/File:Folgers_local_copy.ogv
This has a state "Added to the job queue, x seconds, x minutes ago." TMH used to use it's own date formatter for this, but now switched to the MWTimestamps relative time formatter, and it's ability to generate the 'ago' format.
But ago constructs like this were pointed out as being problematic in 2013 https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Moodbar-feedback-response-summary/en
Which is why there is this cluster of tickets. I got rid of TMHs custom code for handling this, but I'm not sure if we ever made this construct usable in core, or if the whole construct is simply impossible to translate.
Comment Actions
I think this is better than nothing. It works for some languages, though for maximum flexibility some other languages would prefer separate messages for each context it is used. That would be quite excessive without additional support due to the number of messages needed to support just one context.