Last modified: 2014-07-14 23:19:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69959, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 67959 - The "ago" mechanism is untranslatable due to sentence split
The "ago" mechanism is untranslatable due to sentence split
Status: NEW
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
1.24rc
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks: 30857 67960 67961 67962 67963 67964 67965
  Show dependency tree / graph
 
Reported: 2014-07-13 23:26 UTC by Nemo
Modified: 2014-07-14 23:19 UTC (History)
14 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nemo 2014-07-13 23:26:41 UTC 
[[MediaWiki:Ago]] and friends generate untranslatable strings, according to Shirayuki's assessment of MF-Warburg's requirements for German at <https://translatewiki.net/wiki/Thread:Support/About_MediaWiki:Moodbar-feedback-response-summary/en>

«
* 2 months
* 2 months ago
* 2 days
* 2 days ago

[should become]

* 2 Monate
* vor 2 Monaten
* 2 Tage
* vor 2 Tagen

(the problem is that the output currently is "antwortete [replied] vor 2 Tage").»

Previous discussion: https://translatewiki.net/wiki/Thread:Support/ago_%28%22$1_ago%22%29_cannot_work#{{msg-mw|ago}}_cannot_work_16901
Comment 1 Nemo 2014-07-14 09:29:19 UTC 
Thanks Andre for editing the summary. To clarify, I had left the report in General/Unknown because this "feature" was added by a team developing some extension for their own purposes and it's not yet clear if the problem should be solved in core. Hopefully, no core interface is using this mechanism yet and i18n of core is not affected.
Comment 2 Bawolff (Brian Wolff) 2014-07-14 23:19:57 UTC 
So basically this bug is requesting that these things be moved to using MWTimestamp::getHumanTimestamp?
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links