Posted under General
The howto:translate page suggests checking posts with a translation bump but what is the proper way to communicate that the post or pool has been translated? Should you comment, send a direct message, or do nothing and hope they see it? In particular I'm trying to help out on finishing pools that might be missing a few pages with a bump that might be even a week old on posts that could be a month or more older.
Translation bumps are discouraged because the translation_request tag is for, well, translation requests. Translation bumps only clutter the comments and comment feed.
The correct way to handle posts that have been translated is to add the translated tag and remove translation_request when everything is done. That’s it. Users who want to see freshly translated posts can use order:note in searches.
Shouldn't howto:comment have a rule against translation bumps? They're spam that contributes nothing to a discussion. I've seen warnings issued in feedback for this, but comments like these still get made almost every day.
iridescent_slime said:
Shouldn't howto:comment have a rule against translation bumps?
Yes please.
I've seen warnings issued in feedback for this, but comments like these still get made almost every day.
When in Rome, do as the Romans do, and apparently the Romans are posting “translation bump” comments. :(
iridescent_slime said:
Shouldn't howto:comment have a rule against translation bumps?
I might die from protein deficiency and, having just entered statewide quarantine, I don't think I could afford the cleaning bill.
If they're discouraged then the translation guide probably shouldn't have an explicit link for searching comments with translation bumps.
- Go to an image in need of translation (look at translation_requests). You can also try searching the comments for people who bumped images for translation
But then again it says "Click on Add Translation" while the button says "Add Note". It also doesn't even mention topic #7805.
If there should be a rule against translation bumps, I would suggest to explicitly mention that forum thread as the proper outlet for it in howto:comment.
Just for fun though, I counted in the last 7 days there has been 10 comments asking for a translation and the last 10 posts of topic #7805 spans almost half a year.
I have to admit that I've done a bump or two a long time ago impulsively but while I now indeed want the abolishment of bumps as well, I'm pretty sure it might be some kind eternal punishment.
Imagine having to clean up (if decided) around tens of thousands of posts with translation bumps along with who knows how many hundreds of new posts that get in the site every day, just to then having to enforce the rule every single time. It doesn't help that bumping as pretty common thing not just here but in most other places. Just thinking about it makes my head hurt, ha. It's probably possible but yeah.
kittey said:
Translation bumps are discouraged because the translation_request tag is for translation requests.
The translation_request goes on almost every single post with untranslated text in it, regardless of whether there's any real interest in it being translated or not. It's a useful tag, just not in the way that's being described. At least with bumps people know that a non-zero number of people actually care and will see it if it gets tl'ed.
Banning translation bumps will only effect people who didn't read all of the site's rules before commenting. The people who do it regularly will just switch their comments to something only vaguely more substantive to the same effect. It seems pointless to even try to enforce a rule against translation bumps, imo.
Just for the record, in issue #4261 (see second comment) evazion stated that he plans to add some way to vote for translation requests, but who knows when it'll be done.
Ah so I gather the current situation is that translation_request means that a post should be translated for the community's sake, not necessarily that any given user wants to read it. Without an easy outlet for an individual to express beyond what the tag already does, people will use what's in front of them and comment. This leads translation bumps to be a common comment that would be impractical to explicitly ban and therefore persist until eternity.
I mean I don't want to encourage it by translating after a TL bump but I also wouldn't want to leave a partially translated pool untranslated that someone wanted to read recently...
A way to watch posts for translation would be nice. Assuming that most of the user favorite functionality is recyclable then maybe it could be done but then again real life always kicks plans in the face.
wiggly said:
A way to watch posts for translation would be nice. Assuming that most of the user favorite functionality is recyclable then maybe it could be done but then again real life always kicks plans in the face.
My solution to this was to create a favorite group I labelled "Untranslated" and periodically checking it by searching:
favgroup:[FAVGROUP_ID] ~translated ~check_translation
Incidentally, after learning some Japanese for unrelated reasons this favorite group became a to-do list.
No. Also, you can go to the issue that nonamethanks linked above (issue #4261) to follow the progress of that feature request.
As a side note, another way to watch posts for translations is by using the userscript EventListener (topic #14747).
