Currently the mostused sub group for MediaWiki core can't be supported, as it requires PHP arrays. It should be able to use the new JSON format for MediaWiki core.
Version: master
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=63416
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Nikerabbit | T65415 Support core-0-mostused with JSON file format | |||
| Resolved | Nikerabbit | T65416 Update list of most often used messages for MediaWiki core at Wikimedia |
Writing the new message group shouldn't take more than hour, but we also need updated data for it. Is there separate bug for that yet?
Gerard.meijssen wrote:
Hoi,
It is a requirement for new languages in the language policy. Consequently there IS an urgent need to have the most used messages available.
Thanks,
GerardM
(In reply to Gerard Meijssen from comment #5)
It is a requirement for new languages in the language policy. Consequently
there IS an urgent need to have the most used messages available.
Agreed. The 2011 list might be only 75 % correct now, but it's still vastly better than random guessing (currently 500/3057 = 16.4 % chance).
Niklas, can you remove bug 63416 from blockers?
Nemo, I think you are asking me to restore the old list, which is not what this bug is about.
Gerard has expressed interest to work on this bug so he can remove the blocker if he sees fit. I am referring to comment #2 here ;)
In my opinion the old list is *not* more useful than translating certain percent of all messages – translators will go for the simple (which should correlate with most used) messages anyway. That's why I do not see the reason to work on this until we have an updated list.
(In reply to Niklas Laxström from comment #7)
Nemo, I think you are asking me to restore the old list
Not on this bug. :)
(In reply to Niklas Laxström from comment #7)
simple (which should
correlate with most used) messages
I don't see any reason to believe this is true.
New list was deployed to translatewiki.net For practical purposes this is done, but I will file a follow up task to improve the code I wrote.