Since the release is imminent I would like to point out that we still have some issue with the GUI translations. This is pointed out somewhere in [1]. They are kept in the very big repo [2], which also contains the old documentation and stuff. The documentation itself has moved to ciampix' kicad-doc repo. (Can this be soon be moved under the KiCad organisation on github.)
I would like to seperate out the po files [2] sort of like I have done in [3]. It is a conversion of the kicad bzr doc repo, converted to git, where the internat folder is sperated into its own repo, such that is is not with the docs, and the size is about 38M reposize (13M tree size) compared to 1.6G. This preserves commit history, while seperating. I also intend to have the compiled mo files in the repo, and just update the cmake stuff to be able to build the mo files. I would like to have some feedback and maybe a go ahead form the main developers and the translators, about weather or not this is the way to go or not. So what do you think? One advantage of keeping the po files in another repository than the source is that accesscontrol is easier to manage. Often translators are not much involved in the coding part of it, and there might be less strict commit access granted here than on the normal source repo. This to keep this effort seperated from the developers, such that those who don't want to use their time on managing translation patches out of it. Regards Nick Østergaard [1] https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg12824.html [2] https://code.launchpad.net/~kicad-developers/kicad/doc [3] https://github.com/nickoe/kicad-internat-only _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp