Community
Participate
Working Groups
When English strings are read from CVS, those with active translations that have changed automagically flag the corresponding translations as possibly_incorrect. The web UI should highlight files that contain possibly_incorrect translations, and perhaps put them at the top of the list of files, for rapid review Furthermore, the translations that are possibly_incorrect should be identified as such on the UI. select count(1) from translations where possibly_incorrect = 1 and is_active; +----------+ | count(1) | +----------+ | 5343 | +----------+
Created attachment 99134 [details] Screenshot Here's the idea -- highlight the files that contain potentially incorrect strings, and bring them to the top Then, when one picks the file, highlight the strings that need attention.
This is a great idea and needs to be added as soon as possible to help translators know what needs attention. We might also want to add a RSS feed for these changes (among others).
Increasing priority. Let's make this happen sooner than later.
I was thinking this might be a good first bug for Kit to work on? He has been gearing up to squash some bugs for Babel. This would be a good first bug to dive into since it is mostly a UI tweak. But it is up to Kit
Okay, I will try. But, just be patient with me :-)
cc'ing Antoine as he asked about this during the call. As of today: select count(1) from translations where is_active and possibly_incorrect ; +----------+ | count(1) | +----------+ | 10114 | +----------+
How would you put back a translation as correct ? Would you have to resubmit the translation, or just uncheck a checkbox ?
I'd say both options are needed. If only a space or comma has changed, then the translator simply needs to remove the possibly_incorrect flag.
Marking this as blocking the Adobe contribution. I'd also like to see the Recent Translations have a filter for the fuzzies. Reassigning to myself as I'll get this done today.
Created attachment 118294 [details] Patch v1 Here's a complete patch. It identifies fuzzy strings in the UI with a bang (!) image. I've tested it to be completely functional on my dev box, so I'll commit it to staging.
Works great on staging. Closing as fixed, this will be live soon.
