devo10 and devo8 should have different lang files

If you use abbrevated form in english it will find the abbrevated translation from the same one language file...
I think it would be tedious work to maintain two sets...

Yeah, my goal is to have them all in one file, otherwise the translators will be unhappy.
But, if you want to have the same string translated differently for the devo8 and devo10 (hopefully this isn't actually needed) we can enhance the file-format to support that.

PB, can you repeat your message about suggested format of language file. Something like:

:Both devo8 and devo10
;devo8 only
|devo10 only

Can you implement such logic? I would like to refine russian translation for Devo10, and I need to change/shorten many text definitions, that I don't like to change at Devo8.

If I understood well, it was intended for separating the neccesary strings to different files (to reduce the final row count), not for defining multiple translations of the same string for the different transmitters, however that can be achieved too, if the given transmitter always looks for the specialized string first, anf if it doesn't find one, then read in the generic translation.

FDR wrote: If I understood well, it was intended for separating the neccesary strings to different files (to reduce the final row count), not for defining multiple translations of the same string for the different transmitters, however that can be achieved too, if the given transmitter always looks for the specialized string first, anf if it doesn't find one, then read in the generic translation.

No, we already do that.
This was to allow the same string to have different translations.

so I would have:
:string1
translation1
|string2
translation2(devo10)
;string2
translation2(devo8)


As I said previously, it is just to indicate the concept. The actual implementation will not be exactly like this.

I was planning to work on this yesterday but the downtime got in the way.
Vlad, can you file an enhancement request so we can track this feature?

PhracturedBlue wrote: No, we already do that.
This was to allow the same string to have different translations.

Cool, than I remembered it wrong...

What does it mean <: at latest language files?

<:english
<translation

At least 3 Cyrillic symbols at Devo10 looks unusual:

As it is:


As it have to be:


I think they have codes: 434, 447, 43A.

vlad_vy wrote: What does it mean <: at latest language files?

<:english
<translation

< means obsolete, i.e. not used anymore;
> means new entry...