Flag translation as 'golden' vs 'need work'

Sounds like a feature that would be nice to have.

Some of my translators also suggested 'lock' golden translation, i.e. no longer accept suggestion on these strings. Not sure if it's a good idea, just toss it out here for discussion.

Well, possibly as an option, but definitively not an automatic locking. I'm translating a small language with very few translators, and it might be useful to use a "golden" flag to say "This string has been reviewed against our glossary and checked for spelling and grammar errors, and is OK", but that's a far cry from saying "This translation is perfect and can't be improved". Frankly, I don't think we'll any need for a "perfect string"-flag for my language in the forseeable future...

#260761: Block suggestions for strings looks like a partly-duplicate of this one, btw.

We will have a more convenient service than http://www.google.com/translate :)

subscribe

Marking as critical feature for live deployment of http://localize.drupal.org/

I think this would be a good option, but would definitely not set it up in an automated way. It might still be logical is there would be a level of permission which would still let people to submit stuff for such strings, so if you are rolling out a change in terminology used or something like that, it would still be possible to fix these translations. I'd assume the goal of this request is to solidify existing translations where alternates exist, but a decision was made.

Mostly - it should be a final decision... if it's overwritable by (co-)maintainers it's ok from my point of view. It would reduce the number of people dramatically and is therefore a good idea. I hope we do not have many discussions for such a final decision.

The "needs work" is also one of the *most* important missing flags, we need to be able to set for every single suggestion and approved string. It's the only chance to mark something in a way that all authors/approvers are up-to-date about the status of a string... we also need to be able to "comment" why it needs work. Maybe we can use ctools modal window to have something like the project_issue nodes as I think it would overload the current interface (other things could also go into such a window). I believe this "needs work" feature is basic functionality to coordinate a translation of a string.

I was personally very busy in re-reading many strings again and again without being able to remember why I haven't translated them or not approved a suggestion. We cannot remember thousands of strings and why we thought some need work or why we have been unable to translate them. Sometimes suggestions are really good, but small parts of a sentence need work. How have others managed this waste of time?

@hass i manages this waste of time :D moreover a lot of users have suggested translation for golden strings, throwing away our and their time :) If we decided to translate "Save" as "X" (translate in your native language) why someone should suggest "Y"? This is a discussion for the translation group.

+1 for needs work and golden/locked (golden is more meaningful i think). For now we could only add this flags and relative buttons. It's a little patch, i wait for Goba's opinion.

Here's a patch that adds the functionality of marking translations as stable (also allows filtering for them)

For now, it doesn't disallow editing stable translations in any way; it merely displays "(stable)" next to translations marked as stable.

Why do you think that users will try to add new suggestions to already translated strings when there will be more than 100000 untranslated strings? Locking a string does not seems useful to me, if you have enough adept people working on approval. You may spend more time with marking something golden then approving or rejecting suggestions sent to already translated strings.

@Pasqualle: I agree in that it isn't necessary to completely disallow the addition of new suggestions for stable strings. Stable strings are supposed to have a psychological effect: When one sees that the suggestion is already stable, that person is probably less likely to add their own translation and rather go another string. Our experience shows that just because there is already a translation (which isn't marked stable) doesn't prevent people from adding a dozen more suggestions even though the original translation is just fine.

Marked #628056: add a checkbox "needs improvement" or so as duplicate of this issue.

anyone still working on it ??

I suggest "Flag as anything". admins can define their own group filters (flag as golden, flag as need work, flag as typo error...etc. this is similar to project issue Status)

big/important thing is make it more easy to manage the content we have flagged. (that can easy to filter by flag, approve/decline by flag)

New feature to be implemented in 7.x branch