01-27-2012, 05:00 PM | #181 | |
Groupie
Posts: 153
Karma: 113
Join Date: Jan 2012
Location: Russia
Device: Kindle Touch
|
Quote:
BTW, just finished generating reports on current transifex status... Much more comforting in terms of producing the same output as my previous tool report.zip UPD. Tool committed to my own fork and sent via pull request to yours repo. Last edited by JustAMan; 01-27-2012 at 05:31 PM. Reason: update |
|
01-27-2012, 06:43 PM | #182 |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
@JustAMan: thanks for the update. The newest version works for me, but it indeed seems to miss almost all of the properties that cause problems. There has been no relevant change in transifex, so it must be some problem with your tool (?).
@all: the Java tool (and therefore, binary package creation) has been updated slightly. Most importantly, system locales are not written to /usr/share/locale/<LOC_BASE> anymore, but to /usr/share/locale/<LOC_FULL> (e.g. "de" -> "de_DE"). As far as I have tested, this works with no problems, but for some of the previous packages, it requires a reinstallation (=uninstall package using old uninstaller, reinstall using new installer). The First post of this topic has been changed accordingly to make this clear. Last edited by ixtab; 01-27-2012 at 06:46 PM. |
Advert | |
|
01-27-2012, 06:56 PM | #183 | |
Groupie
Posts: 153
Karma: 113
Join Date: Jan 2012
Location: Russia
Device: Kindle Touch
|
Quote:
It solved my doubts as it pulled a lot of fresh stuff... BTW, it looks like I was able to fix russian localization, at least I got home screen working, .txt/.prc reader working, .pdf reader working, settings working. Diff for latest translation pulled from transifex: ru-fix.zip What should I do with that? What isn't there is I'm not able to select default dictionary for Russian the way I'm able to select one for English... Might not be the issue with localization itself, dunno. I cannot test other stuff I suppose is over-translated: that is periodical things, timezone selection and social stuff. Didn't check Amazon Store, too. Any ideas how to test those? Some stuff is translated wrong (probably people that did that translation didn't understand what they were translating or were using Google Translate ), some stuff isn't translated at all (e.g. dialog "turn on WiFi?" is in English, but it might be JS-generated, dunno again). Last edited by JustAMan; 01-27-2012 at 07:00 PM. Reason: added ru_RU fixing diff |
|
01-27-2012, 07:09 PM | #184 |
Groupie
Posts: 153
Karma: 113
Join Date: Jan 2012
Location: Russia
Device: Kindle Touch
|
Hey, just read first post again... You claim that update-base is necessary for the stuff to work, but I don't recall installing it... And my device is localized. Huh?
UPD. Made sure I didn't have that base package installed... Code:
[root@kindle root]# ls /usr/lib/locale/ -la drwxrwxr-x 2 root root 1024 Nov 3 22:58 . drwxr-xr-x 27 root root 16384 Nov 4 00:05 .. -rw-r--r-- 1 root root 8318256 Nov 3 22:58 locale-archive [root@kindle root]# Last edited by JustAMan; 01-27-2012 at 07:11 PM. |
01-27-2012, 07:24 PM | #185 |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
@JustAMan:
your /usr/lib/locale/ layout is indeed expected, as the Kindle *itself* already contains the ru_RU files. There is nothing weird at this point. I'm just trying to make sure that people who installed a previous version of their locale are actually uninstalling before installing it again... to summarize: the (system) ru_RU locale is *already contained* on the Kindle. Localization packages will not touch it currently. See "localedef --list-archive". |
Advert | |
|
01-27-2012, 07:29 PM | #186 |
Groupie
Posts: 153
Karma: 113
Join Date: Jan 2012
Location: Russia
Device: Kindle Touch
|
Okay, if you say everything is fine than everything is fine I'm complete noob in Linux locale stuff.
|
01-27-2012, 08:01 PM | #187 | |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
Quote:
WiFi dialog is Pillow-driven, so yes, it's JS part. Last edited by eureka; 01-27-2012 at 08:03 PM. Reason: some clarification |
|
01-27-2012, 08:03 PM | #188 |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
@JustAMan: I just made sure to have the most recent translations (in fact, I removed the entire directory and did a "tx pull -a -s"), then ran your report tool again. From what I can tell, the output of the tool is now *extremely* helpful. I'm pretty sure that if all of the reported messages weren't translated, the russian locale as a whole should work).
I think that before we go anywhere else, we (=you, or other ru_RU translators) should update the russian translation to reflect this newly gained knowledge, and test whether the updated translations work. Your tool will still be very useful once ru_RU is at a working 100%. Actually, it'll probably even be more useful than comparisons between "en" and "de": a few translated resources also happen to be the same between "en" and "de", even if that doesn't imply a "do-not-translate" situation, like "OK" or "International". Russian may serve as a better discriminator in these cases, because there is a lower chance of translated strings equalling the original. Last edited by ixtab; 01-27-2012 at 11:29 PM. Reason: Hopefully made it at least a little bit less confusing |
01-28-2012, 07:42 PM | #189 |
Groupie
Posts: 153
Karma: 113
Join Date: Jan 2012
Location: Russia
Device: Kindle Touch
|
ixtab,
I've pushed the fixes for ru_RU locale to Transifex & git repo. Might be worth publishing at the first page... And I thought about having a list of "do-not-take-from-translation" properties built in your locale*.jar building stuff. Is it possible? I think it might be easy enough to get from my checking tool, I mean, to make it produce such a list BTW, anyone has newspapers/blogs on their KTouch? I don't and I don't have ability to get some as I do not own credit card suitable for Amazon, and they won't let me subscribe even for free trial without that card... So I cannot test the locale for newspapers and blogs. I was able to test it for magazines, though. Last edited by JustAMan; 01-28-2012 at 07:44 PM. |
01-29-2012, 11:07 AM | #190 |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
@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")); Any other format that can easily be transformed into this via some regex magic will do as well. Спасибо! Last edited by ixtab; 01-29-2012 at 11:30 AM. Reason: typo |
01-29-2012, 11:32 AM | #191 | |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
Quote:
Note: tool takes two .properties to produce output JS file (for the case when some strings in localized .properties are empty or missing and they should be taken from original .properties). BTW, I've seen your addition at KT hacking wiki page about a displayed clock's 24-hour format and it's relation to current locale (i.e. to locale definition). Are you still not convinced to provide real locale definitions? |
|
01-29-2012, 11:37 AM | #192 | |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
That entry wasn't added by me, but I also noticed it, and it directly scared the shit out of me. However, I have immediately tested it with the polish locale, and even though the system locale is symlinked to en_US, the 24-hour clock is displayed So for the time being, I still don't see a need for it. If someday we realize that there is indeed a need to go for them, we can. Last edited by ixtab; 01-29-2012 at 11:39 AM. |
|
01-29-2012, 11:54 AM | #193 | |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
Quote:
Then it was a bit rude from my side. I've confused you with some IP address and was too lazy to check the info. Sorry for that |
|
01-29-2012, 12:12 PM | #194 | |
Groupie
Posts: 153
Karma: 113
Join Date: Jan 2012
Location: Russia
Device: Kindle Touch
|
@ixtab:
Done. That was easy This information was already gathered, so it just needed representation coded. I've pushed my changes to bitbucket. Give a try via "python checkit.py -a blacklist", however I recommend setting "ru_RU" as "model language" as it produces less blacklist entries than "de" (that is, add "-m ru_RU" to command line). It saves the blacklist report by default to "report/5.0.0/blacklist-model_language.txt". BTW you guys posted quite a few messages while I tried to report my progress Quote:
JSON is easy in Python, you know ("import json" and you're almost there ) Hmm... That's goes to ixtab I suppose My tool produces reports and stores them under specified version folder (only 5.0.0 currently - no other versions in src/ are present now). |
|
01-29-2012, 12:15 PM | #195 |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Once the blacklist is complete, I suggest to re-create all source files using the appropriate filter. This would allow for two things at the same time:
As to the system locale issue, I'm currently installing a VM with all existing utf8 locales. It's still installing, but I'll post here once I figured out the implications of trying to add the full system locale to each package. Two things are already sure for now:
So, any thoughts or suggestions? |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle 3 localization | JirkaS | Kindle Developer's Corner | 287 | 05-20-2018 11:08 AM |
[K3] Physical keyboard localization | Sir Alex | Kindle Developer's Corner | 112 | 05-20-2018 12:23 AM |
Kindle 4 (no touch) GUI Localization | Sir Alex | Kindle Developer's Corner | 43 | 09-13-2013 08:19 AM |
Keyboard localization (hack) | Sir Alex | Kindle Developer's Corner | 72 | 04-16-2013 04:05 PM |
Kindle 3, Nook Simple Touch, Kobo Touch and Libra Pro Touch | jbcohen | Which one should I buy? | 4 | 06-18-2011 08:58 PM |