Hello, first of all thank you for the straight development on this module! Even though I have to ask why you have choosen to implement a new module instead of improving flag_content?

I used extractor.php to build this pot file. I got 3 warnings but it's working fine. I did a de-informal translation, "new orthography". Hope it helps those who need it. Delete .txt ending to grab the zip archive.

CommentFileSizeAuthor
abuse-translation.zip_.txt3.71 KBmarcor

Comments

btmash’s picture

btmash commented
Status: Reviewed & tested by the community » Fixed

Hi MarcoR,

I've added your translation and pot file and should be available in the next release. Thank you very much.

While the flag_content module is very well written, I have been in the process of adding a much more extensive featureset and by the time I was finished, the code was far too different to allow for an easy merge with the flag_content module (I redesigned code originally written in 4.6 over to 5.0 as it had fulfilled a number of requirements we had regarding a flagging system). Moreover, the approach I wanted to take with this module differed from the approach being taken on the flag_content module (taking advantage of the forms api over usage of links in the administration of nodes) - both ways have their strong and weak points but I personally felt more comfortable with what I did on it. I hope no offense will be taken to there being 2 modules that tackle the same type of problem (I also aim to help the flag_content module go in the direction its maintainers wish for it to go in).

marcor’s picture

marcor commented

Thank you very much for your explaination and for your offer, too! Maybe this should go into documentation to advice people on selecting the module of their need.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)