Fix typos. (#538)

This commit is contained in:
Caleb Mazalevskis 2018-02-09 08:18:07 +08:00 committed by Eugen Rochko
parent 688e467955
commit 14af52f9f0
1 changed files with 10 additions and 10 deletions

View File

@ -19,7 +19,7 @@ If you want to localize Mastodon into your language, here is how.
## Overview
There are two parts to Mastodon, the server and the web client. The translations for the web client are in [`app/javascript/mastodon/locales`](https://github.com/tootsuite/mastodon/tree/master/app/javascript/mastodon/locales). For the server-side, the translations live in [`config/locales`](https://github.com/tootsuite/mastodon/tree/master/config/locales) and are divided into different files. In addition, email templates for the server are found in [`app/views/user_mailer`](https://github.com/tootsuite/mastodon/tree/master/app/views/user_mailer). Here are all the files youll need to translate:
There are two parts to Mastodon, the server and the web client. The translations for the web client are in [`app/javascript/mastodon/locales`](https://github.com/tootsuite/mastodon/tree/master/app/javascript/mastodon/locales). For the server-side, the translations live in [`config/locales`](https://github.com/tootsuite/mastodon/tree/master/config/locales) and are divided into different files. In addition, email templates for the server are found in [`app/views/user_mailer`](https://github.com/tootsuite/mastodon/tree/master/app/views/user_mailer). Here are all the files you'll need to translate:
| Original file (English) | Location | Description |
|---|---|---|
@ -37,19 +37,19 @@ There are two parts to Mastodon, the server and the web client. The translations
### Obtain the Source Code
If you use Github, first fork the Mastodon repository to your account. Then
clone it to your local machine for further works.
clone it to your local machine for further work.
For details instructions, you may read our
For detailed instructions, you may read our
[Github cheatsheet](Translating-Github-Cheat-Sheet.md).
### Translating
1. Duplicate the files in their folder and replace `en` in the filenames by your languages standard two-letters code
([ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)). Or [RFC5646](https://tools.ietf.org/html/rfc5646)
1. Duplicate the files in their folder and replace `en` in the filenames with your language's standard two-letter
[ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) code. Or [RFC5646](https://tools.ietf.org/html/rfc5646)
language tags for regional languages.
For instance `simple_form.en.yml` becomes `simple_form.es.yml` in the Spanish translation, and
`simple_form.zh-HK.yml` in Traditional Chinese (HK) translation.
`simple_form.zh-HK.yml` in the Traditional Chinese (HK) translation.
2. Also replace the language code in the first lines of all the files, and the last line of the `.js` file.
@ -65,14 +65,14 @@ The locales are mentioned in several other files. To activate your translation,
|---|---|---|
| [`index.js`](https://github.com/tootsuite/mastodon/blob/master/app/javascript/mastodon/locales/index.js) | `app/javascript/mastodon/locales/index.js` | 2 lines to add |
|[`mastodon.js`](https://github.com/tootsuite/mastodon/blob/master/app/javascript/mastodon/containers/mastodon.js) | `app/javascript/mastodon/containers/mastodon.js` | 1 line to add + 1 list to complete |
| [`settings_helper.rb`](https://github.com/tootsuite/mastodon/blob/master/app/helpers/settings_helper.rb) | `app/helpers/settings_helper.rb` | 1 line to add + your languages name |
| [`settings_helper.rb`](https://github.com/tootsuite/mastodon/blob/master/app/helpers/settings_helper.rb) | `app/helpers/settings_helper.rb` | 1 line to add + your language's name |
| [`application.rb`](https://github.com/tootsuite/mastodon/blob/master/config/application.rb) | `config/application.rb` | 1 list to complete |
### Sending the translation
You can then push the files to git and submit a pull request.
For details instructions, you may read our
For detailed instructions, you may read our
[Github cheatsheet](Translating-Github-Cheat-Sheet.md).
## Testing the translation
@ -81,7 +81,7 @@ Once the pull request is accepted, wait for the code to be deployed on a Mastodo
## Updating the translation
Keep an eye on the original English files in `app/javascript/mastodon/locales` and `config/locales`. When they are updated, pass on the changes to your language files. For new strings, add the new lines to the same position and translate them. Once youre finished with the updates, you can submit a new pull request.
Keep an eye on the original English files in `app/javascript/mastodon/locales` and `config/locales`. When they are updated, pass on the changes to your language files. For new strings, add the new lines to the same position and translate them. Once you're finished with the updates, you can submit a new pull request.
## Appendix
@ -105,7 +105,7 @@ eat_apple:
In both examples you can see a `one` case and an `other` case described for the pluralized strings. The exact strings is chosen by how many a certain quantity is -- when there is exactly one of something, the sentence goes to the `one` case; otherwise it goes to the `other` case. This how plualization works for English (`en`) and a few other languages.
There are, however, many languages that don't operate in the one-other way. Polish as four plural forms, named `one`, `few`, `many`, and `other` respectively. Arabic has six. Chinese, Japanese, and Korean only have one form called `other`. If your language does not use one/other plural forms, be sure to check out the cardinal part of this [Unicode CIDR Plural Rules](http://www.unicode.org/cldr/charts/28/supplemental/language_plural_rules.html) chart. Also as a rule of thumb, always start translaing with the `other` case in the English files as they are better generalized than the `one` case.
There are, however, many languages that don't operate in the one-other way. Polish has four plural forms, named `one`, `few`, `many`, and `other` respectively. Arabic has six. Chinese, Japanese, and Korean only have one form called `other`. If your language does not use one/other plural forms, be sure to check out the cardinal part of this [Unicode CLDR Plural Rules](http://www.unicode.org/cldr/charts/28/supplemental/language_plural_rules.html) chart. Also as a rule of thumb, always start translaing with the `other` case in the English files as they are better generalized than the `one` case.
### Appendix B. Command Tools