Hehe, I think we scared everybody else away from this thread.
Is there anything I can do while you're at the JS part? Since we're almost there (at least conceptually), I was thinking about starting to plan for a tool which would bundle up all localized resources. A couple of questions come to mind:
- Package type: I'm in favor of providing an update*.bin as installer/uninstaller. Any other thoughts?
- Should packages include or exclude the little hack to enable the "international" settings? Pro inclusion: 1-stop-installation. Pro exclusion: independent update of that file (in case it ever becomes necessary for new firmware) + strictly speaking, it contains (modified) amazon code.
- We will need one final element for each supported language, namely the .properties file that identifies the locale (also described in the previous link). We cannot do that through transifex. But since the file is so small, I guess we can arrange for some sort of "out-of-band" mechanism to create these files.
Concerning the last topic: I suggest to place these files in a 4th directory, along with the framework, locale, and (waf/pillow?) one. Maybe "manifest" would be a good name. That directory would contain only "<locale>.properties" files for each supported locale.