Ticket #91 (closed enhancement: wontfix)

Opened 2 years ago

Last modified 14 months ago

Regulation of priority for mass translation

Reported by: looki Owned by: ofer
Priority: minor Milestone: 0.5 - Beta wordpress plugin
Component: WordPress Plugin Version: 0.4.2
Keywords: Cc:

Description

In case of mass translation, there are interesting to have a regulation of how much priority the mass translations need to take. For example, if my server is very slow, it would be interesting to translate the "segments phrases" one by each 1 minute, 2 or more. I have in mind what I think is a good aproach of priority, take a look:

  • RealTime?: Segments get translated instantly when the user click to Publish
  • High: Each Segment get translated one by one for each 20 seconds
  • Medium High: Each Segment get translated one by one for each 40 seconds
  • Normal: Each Segment get translated one by one for each 80 seconds
  • Medium Low: Each Segment get translated one by one for each 160 seconds
  • Low: Each Segment get translated one by one for each 320 seconds
  • Idle: Segments get translated very slowly, something like 1200 seconds for each segment

In the case of some user access one page that was not translated, the background/mass translation need to get some more delay to dont overload the server

For this functionality, you could use the WP_cron, that is a function bultin on wordpress.

Change History

comment:1 Changed 2 years ago by ofer

  • Priority changed from major to minor

I am now finishing the mass translation interface, and I think this is probably an overkill,
however - what I did take from this bug is that newer posts will be translated before the older ones.

Also - I will add comment translation to the mass translation.

Last - WRT using cron for translation, please remember that your server does not do the translations, your clients do, so it can't really happen by cron.

comment:2 Changed 14 months ago by ofer

  • Status changed from new to closed
  • Resolution set to wontfix

I am closing this ticket for now, see my comments on #90, if there will be future demand for such a feature than I'll reconsider, however - thanks for the idea.

Note: See TracTickets for help on using tickets.