Ticket #84 (accepted enhancement)

Opened 2 years ago

Last modified 13 months ago

Allow translation suggestions - to be later authorized

Reported by: looki Owned by: ofer
Priority: critical Milestone: 0.7 - Coming Major
Component: WordPress Plugin Version: 0.4.1
Keywords: Cc:

Description

I think the way Transposh make available to anyone modify the translation without any restriction is not good [I am not considering the roles, because there is some cases we need a community help to do the translations], and the simple use of roles is not good enough for the case, if one bad person go and modify something to the purpose to SPAM or for Pishing, it would be hard to the Admin fix all it, mainly because the Admin dont know all the languages available, and some times we dont have the man-power to do all the work alone.

So, a good solution is, make this tool as a “suggested” translation, the suggested translation will appear in the dashboard and one Admin will check it. I mean, a sugestion system much like the one used in Google Translator.

Change History

comment:1 Changed 2 years ago by ofer

  • Status changed from new to accepted

Thanks,

There will be a better workflow for translations in future versions, although I am not sure this cuts it. How can an admin approve a language he does not understand? We might need to introduce the role of translation.
Also - the removal of immediate approval removes most of the incentive for users to correct translations, just think how wikipedia would have looked if it was approval based.

comment:2 Changed 2 years ago by looki

Ok,

One admin can "accept" one translation done by someone taking the "proposed" translation and putting it on a translation engine [there are many on the web] to see what is the "meaning" of what was suggested, if, and only if, the translation "match" with the original text the admin can choose if he approve or not.

But, if you leave your system more open, anyone can post any translation and the admin looses the control, because what I said in the first paragraph cant be done in a "global" level. Also, the way I proposed can keep your system more simpler.

About the incentive to users, well, some blog owners dont care about it, as the same as most users also dont care about helping anyone. In the case of wikipedia, well, it is a totally different environment, and they have their own methods to protect excess of changes, and, as I remember about the first years of Wikipedia, it was a hell, and the lack of protection made a very bad "first impression" to most of people, and institutions like Universities dont accept Wikipedia as a source of information on any type of work.

comment:3 Changed 2 years ago by looki

Thank you very much,

I liked the suggest system you implemented in the frontend editor, but I saw a little buggy. Some times when I suggest the translation, in follow of the button click it clear what I wrote and give a translation, is it right? The right is not to give a translation suggestion to the translation engine in the place of receiving a new translation?
I think you could have both, a way to suggest a translation to the tranlation engine, and a way to receive a new translation from the translation engine. It would be a good thing.

comment:4 Changed 16 months ago by ofer

  • Milestone changed from Beta wordpress plugin (0.5) to 0.7

comment:5 Changed 13 months ago by ofer

  • Summary changed from Enhance front-end editor for translations. to Allow translation suggestions - to be later authorized
Note: See TracTickets for help on using tickets.