@JustAMan: cool
I'm not modifying the front page yet, for various reasons: first, we need to make sure that it is indeed working, so give yourself and other ru_RU users another day or two to test it. Second, I also didn't make an announcement that de is "complete" there, for the simple reason that: third, none of our translations can be considered 100% until we have the JS part in there as well. I see that eureka is making progress, but I'll wait until he says the tool is stable...
That said, I have updated the Java tool to include all the logic for handling blacklisted entries. See the big green chunks on
https://bitbucket.org/katey_hack/kin...t/7061dd1697f1 . It's working, now all we need to have is the data. Could you implement in your tool a "negated" mode, where it outputs (almost) the exact opposite of what it's doing now? I.e., it takes a reference translation, and then outputs all Strings which are identical between en_US and the translation.
Ideally, the output would look something like this:
Code:
// com.amazon.ebook.booklet.periodicals.blogs.ui.views.home.resources.BlogHomeWidgetResources#event.gesture.previous=east
set.add(new ResourceEntry("com.amazon.ebook.booklet.periodicals.blogs.ui.views.home.resources", "BlogHomeWidgetResources","event.gesture.previous"));
The first line is only for human verification of the value, the second line could be directly included in the code.
Any other format that can easily be transformed into this via some regex magic will do as well.
Спасибо!
