Russian translation

[CTPAHHuK]

Begin translate language files into russian
Translation will be aviable soon (week or two)

[datahell]

Thank you CTPAHHuK!
Will be very glad to send your translation to us to include it in the main Elxis distribution.

[CTPAHHuK]

No problem ! I send it after finish job
I also write small announce about Elxis CMS in Mambo russian support community site

[eliasan]

Thank you for both initiatives!

[ahold]

to CTPAHHuK

Отлично. ждем.

[nobody]

I want to make it too))
But how you change encoding?
I try to do this one, change

<?xml version="1.0" encoding="UTF-8" ?>  to
<?xml version="1.0" encoding="windows-1251" ?> in russian.xml and have no resault. Browser detect page as UTF-8 and its unreadable.

Its no problem to translate, but how to change encoding?
Tnx

[eliasan]

Hi,

I am not specialist in Russian language, although I think of Russians as "brothers".

What I am sure of, is that you do not have to change encoding to something special. UTF-8 encoding supports also Russian language.

[eliasan]

And just another note.

You may read the following article for more information:
https://www.elxis.org/index.php?option=com_content&task=view&id=48&Itemid=94&mylang=english

It gives detailed instructions on how to translate Elxis to your language.

[datahell]

In that article there is something wrong. You can not name your language files whatever you like (ie german2006.php). Otherway Elxis automatic locale setting will fail and it will be always english. You must follow Elxis guidelines. Open includes/Core/locale.php to see how you must name each language (ie. russian for Russian, not ru! ). Encoding should be utf-8. You dont have any problem with this for any language. Just make sure you save your language files as utf-8 and not ANSI (use notepad++ or PsPad -my favourite).

[sarexs]

Good afternoon  Eliasan . I ask you to inform where it is possible to send Russian package For Elxis--2006-3.
The package contains three folders (administrator, site, tools.), is executed in UTF-8. The main question,-
Who, as well as than can compensate my work on translation of language.
Regards, Dmitry Solomkin/Russia, Saratov/

[eliasan]

Hi sarexs,

This is great news!

You may send your translation at datahell@elxis.org.

As for your question, I think that the best place to ask it, is the Russian subforum.
Unfortunately right now, we have no way to validate it.

[datahell]

Congratulations sarexs! You translated even the tools, this is great. We can not validate your translation because we, unfortunately, do not speak Russian. If you think that contains translation errors we must find a way to validate your translation. Otherway we will add it for download as is.

[steelcat]

Hello! I try to translate this engine to RUSSIAN LANGUAGE and find problem. Time data in search component not depend from adjustments in language files. And many other modules works in the same way. I think to produce new pack of engine for russian users with translation of all modules.

[datahell]

Time adjustment for each language is located inside Gemini language files:

DEFINE('_GEM_DATE_FORMLC', "%A, %d %B %Y");
DEFINE('_GEM_DATE_FORMLC2', "%A, %d %B %Y %H:%M");

Change them to match russian time.

You display the date like this (current date):
mosCurrentDate(_GEM_DATE_FORMLC2);

Any date (you can also add offset):
$date = '2006-05-23 12:45:56';
mosFormatDate( $date, _GEM_DATE_FORMLC2);


You should run Elxis in a UNIX enviroment to see these changes as windows do NOT support utf-8 locale (ru_RU.utf8@euro). In a windows system locale is always set to English and so time appearence!

Elxis has been based to Mambo which did n't have multi-lingual enviroment. Maybe in some places we missed adding time support for all languages. Report this to us to fix it.

Send me what you have translated till now in Russian to see the problem (if exists).
datahell AT elxis DOT org

[steelcat]

The original search.html.php file exist this strings

<?php
      foreach ($rows as $row) {
         if ($row->created) {
            $created = mosFormatDate ($row->created, '%d %B, %Y');
         } else {
            $created = '';
         }
         ?>

If I change '%d %B, %Y' to _GEM_DATE_FORMLC2 or _GEM_DATE_FORMLC all works properly?
And I find some bugs. Registration with voice don't refresh after authorization code refreshing.
Problem number two.