MobileRead Forums - View Single Post

ixtab · 12-30-2011, 07:16 PM

So I made a few posts concerning the individual parts of the Kindle Touch. Finally, here is an overview about how they could all work together, and how all of that could be bundled in a single file:

Suppose we're interested in the german (de_DE) translation, which has not been installed on the Kindle yet. Then the bundle would contain:

- /opt/amazon/ebook/config/locales/de_DE.properties: file containing the description of the locale, and enabling it in the first place.
- /usr/share/locale/de : directory containing "low-level" strings, such as the ones displayed when connecting the Kindle. (USB mode, restarting etc.). This is what is referred to as "blanket" in previous posts.
- /opt/amazon/ebook/lib/locale-de_DE.jar: file containing localization of a major part of the UI, especially for actually reading ebooks. This is what is referred to as the "Java" part is previous posts, and what much of the discussion so far has been referring to.
- /var/local/locale/de-DE/: This is where the JavaScript-related parts referred to in my last message would go to. Because there is no "built-in" method for having the Kindle choose a correct version of these, I propose an upstart script which would automatically select the correct folder, use a "mount --bind" command to "override" the unlocalized strings with it. That script doesn't exist yet, but the effect should be along the lines of

Code:

mount --bind /var/local/locale/de-DE /usr/share/webkit-1.0/pillow/strings

Except for the WAF part (Web browser), and Text-to-speech (discussed in other threads), this should include all relevant parts of the system needed to provide a localization of the Kindle Touch.

12-30-2011, 07:16 PM	#48
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Bringing it all together So I made a few posts concerning the individual parts of the Kindle Touch. Finally, here is an overview about how they could all work together, and how all of that could be bundled in a single file: Suppose we're interested in the german (de_DE) translation, which has not been installed on the Kindle yet. Then the bundle would contain: - /opt/amazon/ebook/config/locales/de_DE.properties: file containing the description of the locale, and enabling it in the first place. - /usr/share/locale/de : directory containing "low-level" strings, such as the ones displayed when connecting the Kindle. (USB mode, restarting etc.). This is what is referred to as "blanket" in previous posts. - /opt/amazon/ebook/lib/locale-de_DE.jar: file containing localization of a major part of the UI, especially for actually reading ebooks. This is what is referred to as the "Java" part is previous posts, and what much of the discussion so far has been referring to. - /var/local/locale/de-DE/: This is where the JavaScript-related parts referred to in my last message would go to. Because there is no "built-in" method for having the Kindle choose a correct version of these, I propose an upstart script which would automatically select the correct folder, use a "mount --bind" command to "override" the unlocalized strings with it. That script doesn't exist yet, but the effect should be along the lines of Code: mount --bind /var/local/locale/de-DE /usr/share/webkit-1.0/pillow/strings Except for the WAF part (Web browser), and Text-to-speech (discussed in other threads), this should include all relevant parts of the system needed to provide a localization of the Kindle Touch.