search

buxeasywork / django-rosetta

Automatically exported from code.google.com/p/django-rosetta
MIT License
0 stars 0 forks source link

entry_changed signal #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello,

I've added a signal to use for my own projects, please have a look and merge if 
you like.

http://github.com/canburak/django-rosetta/commit/7861db2408896413f92ebfa6bc69a8a
5f8068ede

Original issue reported on code.google.com by canbu...@gmail.com on 10 Oct 2010 at 3:54

GoogleCodeExporter commented 9 years ago 
Sending signals on entry change is a pretty good idea, I'm just not convinced 
by the arguments you send. Care to explain your choices?

Original comment by mbonetti on 10 Oct 2010 at 6:25

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I've just updated the parameters.

http://github.com/canburak/django-rosetta/blob/master/rosetta/signals.py
http://github.com/canburak/django-rosetta/blob/master/rosetta/views.py#L119

I am keeping track of actions of all my translators and also have approval 
process.

I pay them by words, so I have a log of changes for every action they take, via 
this signal.

Also, the junior translators' strings are automatically marked as fuzzy, where 
only senior ones have the permission to unfuzzy.

Please comment on the additional arguments which could be passed.

Original comment by canbu...@gmail.com on 11 Oct 2010 at 4:51

GoogleCodeExporter commented 9 years ago 
Done, fixed in r119. Thank you for the patch!

Original comment by mbonetti on 12 Feb 2011 at 3:12