Wedge

You can create a new folder in the repo, for instance 'portuguese' or 'portuguese-pt' (I think there are more Brazilians online than Portuguese so it might be worth putting the distinction, just like for English, although I don't really mind either way), copy the English files into it, and start translating them. You can then commit your stuff to your repo (right-click with TortoiseGit on your folder, click TortoiseGit > Commit, and in the commit window, make sure to check 'New branch', name it, then for the next commits you won't have to re-create that branch. Just stay on it for as long as you need.)
Push to your github repo when you want to share (it's okay if some files are only half-translated, but keep untranslated files away from your repo preferably.) Then create a pull request over there.

There are tons of tutorials available. Good luck learning what git is and what it does, because it's hard, even for a seasoned developer like me. Thankfully, as a committer you don't have to know *as many* things about git as I do. If you screw up, I consider it my job to try and ensure it doesn't happen again.

Anyway...! Translating Wedge is a long and annoying task, so I certainly won't put hurdles into your road to completion.

I called the folder portuguese-pt exacly for that reason.
I'm trying git in a vps to see if i can learn something about it and im already crazy on how complicated it is to just overwrite a file.
The admin.english.php is already translated but i need to go to school so later ill review it. I'll bump this topic as soon as i make some considerable progress.
I just need to watch the repo language to know if you commit a change to a file right?

Anything that works.Yeah...
You could simply install Github for Windows, it's not great but it doesn't need any dependencies. Or, install TortoiseGit, I think it comes with msysgit, you just need to leave the default settings at install, and then you should be able to do everything with menu commands.
Basically, you can use git like SVN, only the terminology changes (mostly these two: commit in svn = commit then push in git, update = pull in git), you don't really need to look into the rest, but you'll still have to learn how branching works (basically, when you checkout (switch) to another branch, your repo folder actually refreshes to show the contents of that branch, so you can't switch to another branch if you have uncommitted stuff in your current branch, because git can't keep track of these files later.)Most of the important things in Wedge are in index.english.php, I mean I did my best to only have 'generic' strings in that place. Admin in Portuguese seems less urgent to me than index in portuguese, because a forum can pass up as 'fully translated' if only the index is done.Yeah, it gets (unfortunately) a bit complicated here...
You have to right click the folder in TortoiseGit, Settings, Git > Remote, enter 'upstream' (or 'official', or whatever) in the Remote input box, then "https://github.com/Wedge/languages.git" (without quotes) in the URL box, then click on Add New/Save. Click OK.
Now, when you want to get the official updates to the files, you'll have to right-click your folder, TortoiseGit > Pull, then choose upstream/official in the Remote select box, and confirm. Your repo's master branch will be updated with my changes. You can then merge these changes (not rebase them) into your portuguese branch, and then update your Portuguese files accordingly.
In the (likely) case that we get duplicate merges when you do pull requests, I'll either rebase them myself to fix the stuff, or, quite probably, simply ignore them. I like keeping the Wedge history clean, but the languages folder history..? Well, I can't be anal about everything, I suppose.

Anyway, I should probably make a FAQ out of this... Hi Farjo :P

:)

Me reading this thread reminded me of:

So started the translation almost 2 months ago, didn't expect to take so much time but school got in and i had to hold this.
I'm using the files in a local install, some errors here and there but i manage to fix them, still only 3 files to end the translation and around 20 to review before i submit them to the repo.
I don't know if that is the right way to install a language but i just copy the files to the language folder over /core/languages/, is there a way to install them so the structure stays like in the repo language?

You mean that you can create inside the language folder an folder "portugese-pt" from where the files can be loaded? I also wondered if that works, would be nice and a more clean way. Otherwise there are so much files in the language folder which is very chaotic.

Sounds fair enough to commit :)