MobileRead Forums - View Single Post

ixtab · 02-10-2012, 05:13 AM

@flat_eric: di niente

@eureka:
I have all the code ready for full integration of the js resources tool (please don't change anything in the syntax or the output "directory layout" anymore from now, or if you do, then let me know beforehand).

I tested it with various locales in different states (de, pt_BR = fully localized, cs=semi-localized("pillow" actually using english base, but no waf), es=neither pillow nor waf).

All of these work smoothly on my device, of course reflecting the different translation states. The uninstallers should also be doing sensible things. (I had 6 different locales installed, uninstalled them all, and the device looked pristine again).

So, from my perspective, we're almost ready for "prime time"

I haven't pushed the changes to the repo yet (waiting for your OK to include the js tool in the chain), but could do so at any time.

I know there are still a few minor things to fix (like the "Off" button), but these changes can be easily integrated in the future, I guess.

The one thing where I disagree with you is to blacklist/disallow localization of bookmarks. As diba and I have stated (and I'm sure many others agree), it makes much more sense to allow for a localized bookmark set instead of keeping the default (en.wikipedia.org -> de.wikipedia.org; google.com -> google.de; bbc.co.uk -> spiegel.de, as examples). The default set of bookmarks should at least be somewhat useful to the user. Moreover, Google and Wikipedia are tightly integrated into the search function, and it just doesn't make sense to have everybody search the english wikipedia if they're looking for content in russian or portuguese.

Anyway... should I push the updates so that the waf/pillow parts get integrated in the distributions (and the daily snapshots)?

02-10-2012, 05:13 AM	#279
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	@flat_eric: di niente @eureka: I have all the code ready for full integration of the js resources tool (please don't change anything in the syntax or the output "directory layout" anymore from now, or if you do, then let me know beforehand). I tested it with various locales in different states (de, pt_BR = fully localized, cs=semi-localized("pillow" actually using english base, but no waf), es=neither pillow nor waf). All of these work smoothly on my device, of course reflecting the different translation states. The uninstallers should also be doing sensible things. (I had 6 different locales installed, uninstalled them all, and the device looked pristine again). So, from my perspective, we're almost ready for "prime time" I haven't pushed the changes to the repo yet (waiting for your OK to include the js tool in the chain), but could do so at any time. I know there are still a few minor things to fix (like the "Off" button), but these changes can be easily integrated in the future, I guess. The one thing where I disagree with you is to blacklist/disallow localization of bookmarks. As diba and I have stated (and I'm sure many others agree), it makes much more sense to allow for a localized bookmark set instead of keeping the default (en.wikipedia.org -> de.wikipedia.org; google.com -> google.de; bbc.co.uk -> spiegel.de, as examples). The default set of bookmarks should at least be somewhat useful to the user. Moreover, Google and Wikipedia are tightly integrated into the search function, and it just doesn't make sense to have everybody search the english wikipedia if they're looking for content in russian or portuguese. Anyway... should I push the updates so that the waf/pillow parts get integrated in the distributions (and the daily snapshots)?