Last modified: 2014-11-05 14:54:03 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 T58547, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56547 - #time: should not "guess" incomplete dates
#time: should not "guess" incomplete dates
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
gci2014
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-04 08:16 UTC by Bernhard Krabina
Modified: 2014-11-05 14:54 UTC (History)
0 users

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


Attachments

Description Bernhard Krabina 2013-11-04 08:16:29 UTC
Dealing with incomplete dates, the function "guesses" the rest of the date, which it should not do:

{{#time:j|April 2013}} returns the same result as {{#time:j|1 April}}. Both are 1 but in case of April 2013 it is an assumption. Depending what users are doing with the result things could take a wrong turn on there wiki's. The desired result should be something that can not be a day, like 0 so users can "catch" it.

As the behaviour might be dealt with in several wikis, I suggest to include a settings parameter, where users can swith the guessing on or off. So users who need the guessing can still activate it (or on the other hand users who need a correct handling of incomplete dates can deactivate it).
Comment 2 Andre Klapper 2014-11-05 14:54:03 UTC
Bernhard: Could you imagine being a mentor for this task in Google Code-in 2014?
See https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079264.html and https://www.mediawiki.org/wiki/Google_Code-in_2014 for more information.

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


Navigation
Links