I can volunteer to correct some mistakes from the AI French translations, but I've never really used Github before, except to download and compile some softwares (I'm not a programmer).  I have my account though.

I have limited time, so I won't be able to do much, but I'll do what I can.  How do I proceed?

And since I don't own the game yet (I know, I know, I really should, but I don't have the time to play much ). If I ever need clarification/context for something, I ask here in the forum?

There's one grammar mistake I'm consistently spotting in AdvisorRecommendationText.XML, so, can someone give me a crash course on Github?  I fork the repository, then press "commit changes" with my modifications? 

Any other native French speakers around I can speak to when I'm unsure about a translation?  It's easier when they're Galciv players...

I've been trying to coordinate this a little from Discord, so yah any French speaker who wants to help, come join us in the French channel. The more people we have, the faster it'll get done.

The way this works with Github:

You can create your own personal branch from what's on Github now. Like for the French folder on github, check the file AbilityText.xml in the text folder. It will open it in a text editor on github. Now click the Crayon button at the top right, this will open the file in write mode on your own personal branch. Commit the changes and finish your pull requests after that to allow the collaborators (FrogGamer and Draver so far in the French case) to check the changes you're proposing. They alone (and Frogboy/Draginol of course and who ever he adds) can include those changes in the main branch. Other users can also check what you committed and makes comments/suggestions.

This way we can have multiple peoples working on this, with a couple of editors to pass over the changes before they get merge to the main branch, and hopefully be added to the next version of the Insider build.

Now if you wonder which file to look at, on https://github.com/Draginol/GC4_Localization/tree/main/French/Text everything that has "Added many other languages" as Last commit hasn't been verified yet. So that's a good place to start.

Again, in the Russian translation, you did not correct Bradley’s remark on the diplomacy screen at the end of the trade dialogue. Bradley responds at the end of the trade with abroikadabra *?:%;%;№%::?***((((!;;%%:: ??here is his answer at the end of the trade agreement dialogue.Please fix this in the next update of your game.

Hi! i´d like to help with spanish translation, mostly in menu´s screens has some mistakes, but i looked on github and man, i know nothing about programming, is there any other way to help?

Hello Rhaegon5997,

Draver has shared an excellent tutorial, however, I can imagine, that for a non-programmer it may still be overwhelming. For that I can recommend a relatively new feature from github - github desktop. It is way easier to handle, and should be much easier for a non programmer.

1) You will need an account on github

2) Once you download the github desktop, it will propose to "clone a repository"

2.1) switch to "url", and enter the link from Draginol's github: https://github.com/Draginol/GC4_Localization

2.2) You can change local path to what ever you feel comfortable with

3) it will download all the files locally to your computer, and you will see a rather blank screen

But no worries! That's how you want it to be.

4) In the middle of the screen you can see the "show in explorer" button, click on it, and it will open all the files locally on your computer

5) Now you can edit game files, with any text editor (I recommend notepad++, but you can literally use text editor)

5.1) Take care about syntax. Do not delete brackets or similar. Change only words

6) After you change the file locally, it will automatically show up in github desktop, and even more, show you what the changes are:

Here you can see, that I edited the file "additionalStrings_1.xml" to have "I changed something here...". It also indicates lines of code where I have changed something, which makes it easier, if you see a mistake after proofreading. 

7) After that, you can pretty much submit my clicking "commit to main" button at the left bottom in github desktop

-----

This may look like a long explanation, but will definitely be easier, than following a proper github guide on cloning repositories. As only skills required in my explanation are to able to create an account, download an app, and edit text.

And the best part, once you have set it up, you will only need to edit text from there on, without all the extra procedures.