orecchionebruno wrote:Creating a new repo, is what you mean for to be faster?
Hi Daniele,
Nope, that's not what I meant. I had in mind so called Pull Requests. You could watch this video tutorial on how to create a pull request:
https://www.youtube.com/watch?v=75_UrC2unv4General info about pull requests on Github is here:
https://help.github.com/articles/using-pull-requestsA typical workflow in this scenario is as follows:
1. Fork the main Goldendict repository to your account (there is a button Fork in the upper right corner). This needs to be done just once, and the repository you've created by forking the main Goldendict repository is your working repo, where you would put your changes.
2. Clone the forked repo (the one from your account) to your computer. There is a button for that when you open your repo on Github, in the browser: "Clone in Windows" or similar. This also needs to be done just once.
3. Create a branch of a master branch, name it appropriately, say "update-1" or "italian-1", etc.
4. Update the files in that branch as you wish. The ts files are in locale folder.
5. Commit the change, with good description.
6. Push your local branch to the remote branch in your repository on github.
7. Go to that branch on Github and press "Pull Request", fill out the form and submit it.
This might look overwhelming (and it is to the new GIT users!), but it gets easier after a while

If you're not very comfortable with GIT this could be *very* confusing and complicated. So feel free to just attach the files here on forum instead of pull requests.
It seems that pull requests make life a bit more complicated to the contributors (you) and a bit less complicated for maintainers (me). Since when I get the pull request notification, I could just press a single button "Merge Pull Request" and all your changes propagate to the main repository. Easy!

But downloading the ZIP file from the forum and updating files is also not that difficult for me.
So it's all up to you, whatever makes you more comfortable and makes you to submit good localization changes
