Quote:
Originally Posted by ixtab
In summary this means that our current translation state ("5.0.0") will work perfectly well with all Kindle Touch versions, including 5.0.3. I do not see a need to create a new release/tag/version/whatever at this moment.
I'm actually in favor of including ("backporting") these resources into the "5.0.0" release: their presence will not do any harm to older firmwares, and we spare ourselves from needless branching/versioning and user confusion ("What? I have a device that says 'Kindle Touch', and I want it in my language. Which freaking package do I have to download?!").
Just my opinion though, so I didn't commit anything yet and I'm open to other proposals.
|
There is a bit of vagueness about what "release" is stands for.
I am fully supporting idea of having unified update bundle for all firmware versions (as long as it's possible).
And I have a mixed feelings (and a deep misgivings) about the idea to not separate resources from different firmware versions in Git repo and Transifex.net just because of introduced changes are small and could be easily backported. I'd like to see
src/5.0.0/framework/... as-is and create
src/5.0.3/framework/.../ReaderResources.properties
But your solution is the simplest working.
So the label "5.0.0" at Git repo and Transifex.net (as a sub-directory in repo, part of slug/name of resource at Transifex) will be turned into misleading. It will be not the 5.0.0 anymore. We have to:
- either delete this label, making src/{framework,locale,pillow,waf} as path to resources (and rely on kindness of Amazon, assuming it will not introduce any backwards-incompatible changes in future),
- or promote it to 5.0.3, making src/5.0.3/{framework,locale,pillow,waf} as path to resources.
What do you think?
Quote:
Originally Posted by JustAMan
eureka,
I can give your script a try on my KT.
|
It's on
js-tool branch at
tool/js_resources. There is a README there.