Last modified: 2010-08-05 18:29:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 24674 - Further internalization of #time
Further internalization of #time
Status: RESOLVED DUPLICATE of bug 19412
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-05 14:32 UTC by Pavel Selitskas [wizardist]
Modified: 2010-08-05 18:29 UTC (History)
2 users (show)

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


Attachments

Description Pavel Selitskas [wizardist] 2010-08-05 14:32:26 UTC
At this time #time already supports such cool things like genetive form of month name (for Slavic languages as well). Unfortunately this is a one-way i18n. I can pass 4.08.2010 and it will give me "4 жніўня" for {{#time:j xg|4.08.2010}}, but it won't work in reverse-mode, i. e. if I would pass {{#time:d-m|4 жніўня 2010}}, it won't give me '04-08' back.

As I understand, now time function is realized through PHP functions. Will be such method (i18n-input) implemented or is it real to be implemented?
Comment 1 Niklas Laxström 2010-08-05 14:35:42 UTC
There is no such function and making one is not going to be easy.
Comment 2 db [inactive,noenotif] 2010-08-05 18:29:52 UTC

*** This bug has been marked as a duplicate of bug 19412 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links