Russian Translation

vlad_vy wrote: It's possible, but not easy.

Give me the source on English and I start
There is a program to emulate the firmware, to be viewed the intermediate result?

I tried to change the term "Fixed ID" with the string from the Russian language file. Eclipse told me that I have to save the file in UTF8 and the string now looks completely different.
But when compiling I get error messages:They come from some additional tools used after compiling.
In the emulator the string looked like the one found in the language file. No Cyrillic letters...

I hope you will have more luck.

I had these errors when I used _tr("Каналы") or _tr_noop("Каналы"); no problems when using only "Каналы".

Translating at compile time with a switch like "make TARGET=devo7e LANGUAGE=ru" is difficult because the C-files (and maybe header files) have to be changed in the source. This is not easily made in the actual working directory, if you want to have back the original files at the end...

The only way I see will be this way:
- make a complete copy of the working tree
- move to that intermediate tree
- translate the text in all files
- make the build
- move the resulting files to the original tree
- go back to the original tree
- remove the intermediate working tree
Looks quite complicated. Or am I missing something?

If the original files were changed you will get problems when pulling a new revision so this is no good option. Or: change the original files and revert the repository afterwards:
- translate the text in all files
- make the build
- revert the repo

Ok, if you interpret the strings in the source code (which are all in English) as pointer to a string in a special language, you might be right.
But localized software will always work with a translation file which is added to the code (at compile time or later) and in the software you can choose to use one language or another.
The code will still contain the pointers and will be identical for every language the user chooses at runtime.

The problem for deviation is that the runtime translating uses so many resources that it will (actually and without massive improvements) not run in Devo7e. There might be implementations where the overhead is less, but we don't have such. In deviation there is a hash table build for translating. If I enable language support I get:
The challenge is: how can we implement a translation routine which needs less resources?
Or do we have other ways?

We could work for every supported language with a long list ofreplace all _tr("Arrangement") with _tr(TXT_MENU_ARRANGE). In normal builds we would include a special language file with(or the pointers will be the English text and we include the English file) so the pointer will stay in the code and we can use translation in combination with the other language files at runtime. For Devo7e we can invent a compile switch to choose a special language file so the pointers are replaced with the localized string (and the _tr()-function does nothing, just as it is now for Devo7e).

The more the text grows the more I feel getting confused. I try to explain my idea in other words: if we have a mechanism which replaces the strings at compile time without having to change the source files we can easily offer localized deviation variants. There might exist other ways to do that besides the #define I offer but actually I can't imagine one.