Last modified: 2014-06-26 17:30:46 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 T65415, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63415 - Support core-0-mostused with JSON file format
Support core-0-mostused with JSON file format
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
: 64223 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-02 13:45 UTC by Siebrand Mazeland
Modified: 2014-06-26 17:30 UTC (History)
8 users (show)

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


Attachments

Description Siebrand Mazeland 2014-04-02 13:45:08 UTC
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.
Comment 1 Siebrand Mazeland 2014-04-22 06:30:23 UTC
*** Bug 64223 has been marked as a duplicate of this bug. ***
Comment 2 Siebrand Mazeland 2014-04-22 08:02:58 UTC
Please do not change Priority of you are not planning on Working on this issue.
Comment 3 Niklas Laxström 2014-04-22 08:11:28 UTC
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?
Comment 4 Niklas Laxström 2014-05-29 10:07:31 UTC
There isn't urgent need to fix this before 63416 is resolved.
Comment 5 Gerard Meijssen 2014-05-29 10:18:53 UTC
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
Comment 6 Nemo 2014-05-29 10:22:20 UTC
(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?
Comment 7 Niklas Laxström 2014-05-29 11:02:46 UTC
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.
Comment 8 Nemo 2014-05-29 11:12:06 UTC
(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.
Comment 9 Andre Klapper 2014-05-29 12:34:55 UTC
[Resetting normal priority according to developer]

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


Navigation
Links