Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Allow localizers extracting raw translations they’ve pushed during a cycle #569
I’ve been doing that manually for some time now ( Editing https://github.com/mozfr/transvision/blob/master/app/scripts/tmxmaker.py#L54 locally to only return the text, e.g. one string per line, without its ID). Doing so allows me to check all the strings with a grammar checker (mine is http://www.antidote.info/antidote for both French and English). This also works when localizers are using a simple spell checker.
Currently it’s a pain to check 30,000 strings with lots of false positive where I could only check what changed between two branches. I also don’t do it for each release because it’s time consuming. Helping automate this would help catching typos like http://hg.mozilla.org/l10n-central/fr/rev/6cc9480baf4b One could even think of running a Jenkins server with a spell checker.
The data I need are basically the green and orange strings exposed by Elmo on https://l10n.mozilla.org/source/diff/?from=661304c55fbc&to=d9c01cf0f9e9&repo=l10n-central%2Ffr but without string IDs.
What do you guys think?
I can see a use case for a view displaying the strings changed between two branches, like we do for Gaia, extending https://transvision.mozfr.org/channelcomparison/ with 'Added strings' and 'Removed strings'
On the other hand, I'm not completely sure of how many people would use a file with only these strings, especially in an automated way, given the number of false positives.
Definitely agree for English strings, that would be more consistent as currently we have to check https://transvision.mozfr.org/channelcomparison/?locale=en-US&chan1=central&chan2=aurora to have the same data and that’s less obvious.