Last modified: 2013-04-15 17:41:19 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 T49250, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47250 - translatewiki.net API: Attach suggestions to message
translatewiki.net API: Attach suggestions to message
Status: UNCONFIRMED
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-15 15:43 UTC by orsagi
Modified: 2013-04-15 17:41 UTC (History)
5 users (show)

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


Attachments

Description orsagi 2013-04-15 15:43:50 UTC
using action=query , list=messagecollection might be useful to be able to request the message suggestions attached to them by mcprop parameter.

the current way using action=translationaids is in-efficient in case of loading suggestions for many messages - since it requires HTTP request for each message, thus leads to great overheads.
Comment 1 Niklas Laxström 2013-04-15 15:45:48 UTC
This is by design. Fetching suggestions for list=messagecollection would be too slow.
Comment 2 orsagi 2013-04-15 17:26:04 UTC
It shouldn't be supplied by default, but upon explicit request of mcprop=suggestions or so.

it is way much slower to serve many "action=translationaids" request.
Comment 3 Siebrand Mazeland 2013-04-15 17:41:19 UTC
I think this will be way too expensive, optional or not. Imagine a batch of 100 messages, and suggestions from translation memory, two helper languages, and two machine translation engines. For the 100 messages, that's 3 external requests per message, 300 in total.

Leaving final verdict to Niklas, but especially becaus of the external dependencies, this is unwanted.

The way we solved this in the UI, is by preloading the next message's data. Doesn't really work for the proofreading use case you are working on. So there is most likely a waiting time when a user wants to edit a translation instead of approve it. If you have a list of translatable messages,  you can use the preload system.

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


Navigation
Links