Last modified: 2012-01-07 04:58:36 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 T20047, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18047 - Make #time output month/day names in interface language
Make #time output month/day names in interface language
Status: RESOLVED WONTFIX
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: 2009-03-19 13:33 UTC by ChrisiPK
Modified: 2012-01-07 04:58 UTC (History)
2 users (show)

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


Attachments

Description ChrisiPK 2009-03-19 13:33:41 UTC
#time provides a way to format a date according to one's own wishes, but it uses the site language for output instead of the interface language. As link tables etc. don't seem to be a serious issue (e.g. on Bug 14404), I don't see why we should not deliver the localizable part in the user's interface language.
Comment 1 Niklas Laxström 2009-03-19 13:46:32 UTC
Link table coherence is an issue. Thus that we already have thing X doesn't mean that we want to add thing Y. This could be possible in (real) interface messages, but as I can see it it would change existing behaviour – that is not good. On the other hand we have already things which can change link table from parse to parse, for example the time related magic words.

A whole separate issue is whether mixing content and user interface elements it a good idea.
Comment 2 Ryan Kaldari 2012-01-07 04:58:36 UTC
Using the user's interface language would still cause lots of cache fragmentation. Marking WONTFIX.

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


Navigation
Links