Updated How to translate (markdown)
parent
ded6f66f46
commit
921fc57d1a
@ -14,15 +14,15 @@ Anyway, the following text will assume that you have chosen Ubuntu or Kubuntu or
|
|||||||
|
|
||||||
2. If not already done, create a github account.
|
2. If not already done, create a github account.
|
||||||
3. [Generate a new ssh key](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/). Here you only need to follow the "Generating a new SSH key" steps.
|
3. [Generate a new ssh key](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/). Here you only need to follow the "Generating a new SSH key" steps.
|
||||||
3. [Add a new ssh key to your github account](https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/).
|
4. [Add a new ssh key to your github account](https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/).
|
||||||
4. [Create a GPG key](https://help.github.com/articles/generating-a-new-gpg-key/) and [add it to your GitHub account](https://help.github.com/articles/adding-a-new-gpg-key-to-your-github-account).
|
5. [Create a GPG key](https://help.github.com/articles/generating-a-new-gpg-key/) and [add it to your GitHub account](https://help.github.com/articles/adding-a-new-gpg-key-to-your-github-account).
|
||||||
5. Enable gpg signed commits by typing `git config --global commit.gpgsign true` in your command line.
|
6. Enable gpg signed commits by typing `git config --global commit.gpgsign true` in your command line.
|
||||||
6. Go to [this github project page](https://github.com/pampanic/pam_panic/wiki/How-to-translate) and fork this project. (Click on **Fork** in the upper right.)
|
7. Go to [this github project page](https://github.com/pampanic/pam_panic/wiki/How-to-translate) and fork this project. (Click on **Fork** in the upper right.)
|
||||||
> **Forking:** You are about to create an own version of a project. It will copy its content to your account under a new project, and github will note that this fork exist. After you pressed the Fork button you will be in your **own** project afterwards.
|
> **Forking:** You are about to create an own version of a project. It will copy its content to your account under a new project, and github will note that this fork exist. After you pressed the Fork button you will be in your **own** project afterwards.
|
||||||
|
|
||||||
7. [Clone your fork](https://help.github.com/articles/cloning-a-repository/) you just made from this project.
|
8. [Clone your fork](https://help.github.com/articles/cloning-a-repository/) you just made from this project.
|
||||||
|
|
||||||
8. _Optional:_ Get an editor for po files like `poedit` or use an online service for it.
|
9. _Optional:_ Get an editor for po files like `poedit` or use an online service for it.
|
||||||
**Installation on (K)Ubuntu:** `sudo apt-get install poedit`
|
**Installation on (K)Ubuntu:** `sudo apt-get install poedit`
|
||||||
|
|
||||||
Are you new to .po files? You might want to read about [The .po structure](https://github.com/pampanic/pam_panic/wiki/The-.po-structure).
|
Are you new to .po files? You might want to read about [The .po structure](https://github.com/pampanic/pam_panic/wiki/The-.po-structure).
|
||||||
|
Loading…
x
Reference in New Issue
Block a user