Hi Angel,
Localization is something we plan to do eventually. I created a
ticket for it at
http://kemia.lighthouseapp.com/projects/58696-kemia/tickets/75-interface-localization.
Feel free to create new tickets for any other things you think Kemia
needs.
It would be really great if you could share any translations you come
up with.
Git is a little different from centralized version-control such as CVS
or SVN--but definitely worth getting acquainted with. Hacking on the
compiled javascript is going to be difficult, if you want to get into
it, I suggest forking on github (as described below), making changes
and then re-compiling per the instructions in the README file.
Here is a guide to the Kemia development team workflow,
http://github.com/kemia/kemia/wiki/Contributor-Workflow-with-Github.
One of the benefits of forking to your own github repository is that
you can make changes and share them for discussion with the team even
if they are not ready to merge with the 'production' code. Just
'push' your local changes to your fork on github so everyone can see
it, as described under 'Interim Publish to Your Fork' (This would be a
good way to share your translations.)
To re-compile, the easiest way is to follow the steps in the kemia/
README using ant.
Regards,
Paul.