Quote:
Originally Posted by ixtab
Thanks for that!
I can't run the report.py by myself, wherever I try to run it, I keep getting
Code:
Traceback (most recent call last):
File "tool/report.py", line 5, in <module>
all_lngs.remove(source)
KeyError: 'en_US'
Since I'm a total noob with python (and honestly I hate its syntax), I don't even dare to try to figure out what I'm doing wrong. So, what am I doing wrong?  |
You didn't download source language it seems
Remember I said do "tx pull -a
-s"?
Or you're running it from the wrong place. You have to run it from the root folder where you did "tx init" and "tx pull".
Agreed that I should handled it better but, oh man, I'm lazy!
Maybe in next version...
Quote:
Originally Posted by ixtab
Thanks for that!
However, I took a look at the output, and it's pretty much what I expected. Most of the Strings I listed in the announcement are wrongly translated. (There are a few innocent ones, like "OK" or "International" as well). It's probably not a bad idea to generate an informative list of "do-not-translate" properties. However, it will unfortunately be of limited usefulness, because translators do not see the property names on Transifex, only the values. I think the report is very useful and helps to give pointers for manual fixing for "advanced" users.
|
I suppose the list would have some use, like "don't integrate this and that property into locale-*.jar" when compiling it. That would be more error-proof than current situation
Quote:
Originally Posted by ixtab
(Update) One more suggestion: leave out empty (=untranslated) strings from the report. As said, they are ok because the base version will be used.
|
I got the idea that
missing property is OK. Now you say that empty property is OK... I'm confused. Which one is fine, or they are both fine?
Quote:
Originally Posted by ixtab
Also, thanks for your offer of the 5.0.0 files, but I'd think that this might lead to even more trouble. I'll just stick with 5.0.1 for the time being. Maybe if I'm feeling adventurous someday, I just try to install 5.0.3.
|
No problem. Until I update my Kindle stands ready
btw, just thought about dd'ing it just in case...
Quote:
Originally Posted by ixtab
Does a failed update give any information (in the log or so) about *which* files it complained about?
|
Nope. I've attached parts of "showlog" on some previous pages - nothing really suspicious except that "Callback thing.
Looks like I'll have to figure it out experimentally.