Last modified: 2014-11-20 09:14:15 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 18521 - System messages structure (tracking)
System messages structure (tracking)
Status: NEW
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n, tracking
Depends on: 2358 2453 10573 16111 16175 17148 22769 28920 31032 messages 41578 13000 14176 16026 17865 18522 19895 23239 24521 25608 26734 28557 29170 29357 29927 30729 35259
Blocks: tracking
  Show dependency treegraph
 
Reported: 2009-04-19 19:52 UTC by Happy-melon
Modified: 2014-11-20 09:14 UTC (History)
5 users (show)

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


Attachments

Description Happy-melon 2009-04-19 19:52:54 UTC
Tracking bug for the way we structure, name, organise, parse, render, etc, system messages ([[MediaWiki:...]] messages) *as part of the interface*.
Comment 1 Andrew Garrett 2009-07-29 16:39:00 UTC
Adding 'tracking' keyword.
Comment 2 Nemo 2012-07-26 20:52:30 UTC
Adding some blockers. I'm not adding the (dozens) of bugs requesting for errors/confirmation/other messages to be split, added or moved, which probably wouldn't even use a tracking bug as they're very separate issues and there's no need to address them together or consistently (besides, nobody would ever bother).
Comment 3 Andre Klapper 2014-07-08 16:40:32 UTC
What's the exact difference of this tracking bug compared to bug 38638? 
Specifying in the bug summary very welcome (verbs always welcome in a bug summary)
Comment 4 Nemo 2014-07-08 16:46:14 UTC
(In reply to Andre Klapper from comment #3)
> What's the exact difference of this tracking bug compared to bug 38638?

Per comment 0 and comment 2, this is about system messages as a whole, while bug 38638 is about individual messages having issues. We could also say this is about what is not called the "messages API", in a way.
Comment 5 Nemo 2014-07-08 16:47:36 UTC
(Though in practice this tracking bug doesn't seem to really be used.)
Comment 6 Happy-melon 2014-07-08 16:49:40 UTC
(In reply to Andre Klapper from comment #3)
> What's the exact difference of this tracking bug compared to bug 38638? 
> Specifying in the bug summary very welcome (verbs always welcome in a bug
> summary)

I haven't seen bug 38638 before, but I'd say probably the most useful distinction to make would be to say that that bug is to track where the *content* of messages needs to be improved (be that by rewording, documenting, adding {{PLURAL:...}} or {{GENDER:...}} support, etc), while this bug tracks the way MW *uses* and *generates* messages.  Eg bug 17148, which is essentially "sometimes MW sticks completely the wrong data into a message".

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


Navigation
Links