backend Language

[Coursar]

Hello. When i translate backend language files, i can't found where replaced Modules & Mambots in toolbar. I download Italian language file, and there i see that Modules & Mambots not replaced.

[old attachment deleted by admin]

[datahell]

These words are not translated.

[Coursar]

Why ?

[datahell]

Because they are characteristic names that describe specific sub-applications. How would you translate mambot? Do you translate "Linux", "Microsoft", etc? As for the "module" you could most probably find a word to translate it but then people would get confused and they will not understand easily the meaning/role of your translation. It is much easier for them to see it as "module". The same for "component" and some other words you may find.

[Coursar]

ok -))

[kyron]

I agree that you should not translate Mambot. Also Component and Modul are common expressions.
However, in my opinion it´s worth thinking about getting ALL the stuff into the language-files for complete freedom for translation. Include the recommandation to NOT change these expression for the known reasons but make it possible. To get translations 'smooth' for example in the german language file, I would like to see 'Module' and 'Komponenten' in the menu-bar, what is quite the same. Also the translation of the component-names (mass-mail, contact, polls etc) could be done without any problems I can think off.
On the other hand, ELXIS is opensource, so you may change this by yourself. Easy enough.

regards

kyron

[Coursar]

but i think, if we translated components as компоненты, we must translate modules as модули.

[datahell]

In Greek -> Components : Συστατικά. Did you understood anything? Even the Greeks will be confused. Although, kyron is right. We will do expand the administration language in version 2007 anyway. More work will be done in XML files translation (used for setting up modules, mambots, bridges etc) with an implementation of a more flexible system and without loosing compatibility with previous version.