Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localization #10

Open
gdude2002 opened this issue Apr 13, 2015 · 0 comments
Open

Localization #10

gdude2002 opened this issue Apr 13, 2015 · 0 comments
Labels

Comments

@gdude2002
Copy link
Member

This is a ticket to keep track of localization progress.

Done

To do

  • Brazilian Portuguese (Looking for translators!)
  • German (Looking for translators!)
  • Portuguese (Looking for translators!)
  • Spanish

Leave a comment if you want a translation in your language!

Some notes for translators

You'll be working with this base file, Messages.properties. Do not edit this file directly - Rather, copy it. You'll notice that there's a Messages_en.properties and a Messages_nl.properties file in the same directory - You'll want to copy Messages.properties to Messages_<your language>.properties, using the international language code.

For example, for someone translating to Spanish, they might copy Messages.properties to Messages_es.properties.

After that, open your new file. You'll see a bunch of different things.

  • Lines starting with a # - These are comments and are ignored by the plugin. Read them, they're there to help you out!
  • Lines not starting with a #, but containing an = - These are translations lines. Do not touch anything to the left of the = sign, these names (or keys) are used to identify a specific translation.
    • You'll want to edit the parts of these lines to the right of the =. By default, these are in English, and these are what you'll want to translate.
  • Lines ending with a \ - These simply run onto the next line, to avoid making lines too long.

Please bear in mind the following rules for translation. If you don't follow these, your pull request will be rejected and you may be asked to correct your translation.

  • Don't edit the colours or formatting. You may rearrange them so that they make sense in the grammar of your language, but the colours are meant to be what they are and should be consistent.
  • Don't rename plugins. ArchBlock should remain as ArchBlock, WatchBlock should still be WatchBlock, and so on. These are names of plugins, and as such are proper nouns and should remain as they are.
  • If there are some words that don't make sense in your language, ask! Some common ones are as follows.
    • Thread - This is a programming term. For translation, you may prefer Job or Work.
    • UUID - This doesn't translate, so you should keep it as UUID and treat it as a noun. Please make sure the capitalisation is correct.
  • Please make sure the capitalisation and punctuation you're using are correct. Your work should look professional, and respect the language that you care so much about.
  • Please also be careful not to use slang or borrowed English words where possible, and to use the formal version of words where appropriate - For example, vous instead of tu to mean you in French.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant