Multi-language

[kplackowski]

Hello Petr,

Many thanks for multi-language
But why not in Polish ?

Do you consider the Polish version?

Regards

Krzysztof

[kitercuda]

I haven't yet contributor from Poland who is willing to translate it
The others are working now (there are a lot of strings)

[kplackowski]

OK, please send the table of phrases in English to me, I shall do my best.

Regards

Krzysztof

[Onuff]

And for rus)))
Rename

[kitercuda]

For rus rename?
I do not understand.

[kitercuda]

Here are 4 files. Menus and Preferences only (first phase of translation)

context_menu_strings.xml, arrays_strings.xml
- Strings should be as short as possible.
- translate only string between > and <. Do not make any other changes.
Example:
<string name="selectScreen">Select screen</string>
translate only Select screen

options_menu_strings.xml
- This refers to options_menu_strings.xml only:
There are 2 strings for one menu item. Android will choose which will use. It depend of available space.
Example:
<string name="aircraftmenu_n_additem">New aircraft</string>
<string name="aircraftmenu_c_additem">New</string>
n means normal length
c means condensed (if there is not so much space in the screen)

preferences_strings.xml
<string name="prefs_t_generalSettings">General settings</string>
<string name="prefs_s_generalSettings">Language, navigation data updates checking, backup and restore preferences</string>
_t_ means title - short
_s_ means summary (description) - can be longer

[Onuff]

For rus rename?
I do not understand.

Make the file with the translation that it was possible to change or add words.

[kitercuda]

Here is the first Russian file - Options menu. You can have a look.

[kplackowski]

And here is Polish language version. All files.

I have to admit I believed before it would be a piece of cake. I was wrong.

I encountered some problems:
a. English is much more compact then Polish. We use more words, longer words, so I had problems with keeping phrases short.
b. I decided not to translate some expressions, keeping link with acronyms on the screen, for instance Course - CRS, Hading – HDG, WPT. Meaning of acronyms would be unclear.
c. Polish grammar is much more complicated the English one. We have a lot of suffixes depending on inflection (declension and conjugation). This fact causes problems with translation of short phrases taken out of the context (I mean another elements displayed on the screen).
d. Necessity of maintaining consistency between translated phrases and texts on the buttons, descriptions of fields, etc.

So, take a look on my translation. If some strings would be too long – let me know, I will try to make its shorter.

Is this any chance to see a “prototype” of Polish version of FiF? Can I run Polish version on my tablet myself for instance by copying new language files somewhere on my device?
In my opinion it is highly advisable to test new language version before publishing (see my comments c. and d.)

Regards

Krzysztof

[kitercuda]

Hi, thanks a lot I will have a look...

a. This is probem of all languages
b. Good decision
c. I have the same problems with Czech language. It is possible to solve, but too complicated - wasting a time.
d. I can send you beta version for trying...