View Single Post
Old 09-14-2008, 03:31 PM   #252
JeffElkins
Guru
JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.JeffElkins is no ebook tyro.
 
JeffElkins's Avatar
 
Posts: 780
Karma: 1416
Join Date: Jan 2008
Device: Kobo Clara 2E/HD, Kindle PW
New release: 0.06

Localization javascript by porkupan:
Localize_Reader_En_Fr_Es_De_It_Ru_Pl_Uk_Cz_Nl_Hr_L t_Bg

Clock bug fix.

I'm thinking that this may be the last release I do to update localization. I posted in the Localization thread:

Quote:
Originally Posted by JeffElkins View Post
I've been mulling this over too.

I know how I'd do it in PRSCustomizer. I'd set up each phrase as a replaceable string: IOW "Settings" would be "$settings." If the localization requested was Bulgarian, I'd simply replace $settings with whatever word = Settings in Bulgarian. The translations would be stored in external text files, so adding localizations should be easy. This would require a main.xml with only one localization as a base.
I don't have the time right now to reduce main.xml to only one localization. However, main.xml just gets larger and larger with each localization added. I think the best path forward is to have localization as a selectable item from a dropdown box (you want Russian, you've got Russian) rather than have many, many languages included. This will also make adding languages much easier and keep main.xml at a reasonable size.

I'll have more time in about three-four weeks, if no one wants to work on a main.xml

Last edited by JeffElkins; 09-14-2008 at 04:52 PM.
JeffElkins is offline   Reply With Quote