Skip to content
Browse files
information about translations
  • Loading branch information
jindrapetrik committed Feb 12, 2018
1 parent 43e19fb commit d2e4efcfe2f05a0cfa70364b7adf914f22ad8c85
Showing with 47 additions and 0 deletions.
  1. +3 −0
  2. +44 −0
@@ -9,3 +9,6 @@ Make sure library part (libsrc/ffdec_lib) does not depend on GUI and does not co

## Tests
Make sure existing tests pass.

## Translations to other languages
For information about localizations to other languages and how to contribute, see []( file
@@ -0,0 +1,44 @@
# Translations

## Available languages
FFDec contains these translations:
- English
- Catalan
- Czech
- Chinese
- Dutch
- French
- German
- Hungarian
- Italian
- Polish
- Portugese - Portugal
- Portugese - Brasilian
- Russian
- Spanish
- Swedish
- Ukrainian

## Preparing...
Translators are working on these new translations:
- No new translations planned now...

## New translation
If you would like to translate FFDec to your language, please follow these steps:

1. Check whether your language is not already present or in preparing state (see list on the top)
2. Find out your language code (See [table]( )
3. Create new issue in [issue tracker]( containing your new language name + code. (You should register first)
4. Download `Language pack for translators (zipped)` from latest (including nighlty) version on [releases page](
5. The archive contains all language files for newest version of FFDec. Each language in this pack has files with its own suffix which is standard language code.
6. Extract Language pack ZIP file
7. Copy each `.properties` file without `_xx` suffix (english), to new file which has your language code suffix (`_cs` is for czech, etc...)
8. Open `.properties` files with an editor. (`.properties` editor bundled with some Java IDE is better than standard text editor)
9. In order to `.properties` to work in FFDec, all nonascii characters should be replaced with unicode escapes (like `\u1234`). IDE editors like Netbeans do this automatically. If you have classic text editor, you can skip this phase, I will do it later myself.
10. Don't forget to place your name in `` file.
11. Attach translated files to that issue.
12. Goto [Issue #354] and look for new translated strings.
12. Subscribe to [Issue #354] to be notified about new strings in the future.
13. Wait for next release where your translation will be included.

[Issue #354]:

0 comments on commit d2e4efc

Please sign in to comment.