Russian locale

[GoogleCodeExporter]

Thought it could be useful.

Original issue reported on code.google.com by iweb.inbox on 6 May 2010 at 9:21

Attachments:

• locale.russian.js

[GoogleCodeExporter]

Thanks for the translation!  I've added it to SVN trunk.

 Would you also be interested in translating some of the examples so that we could include Russian as another 
language choice for them?  We currently have English and German.

cc'ing Conrad as the example translations are his baby :)

Original comment by pagameba on 6 May 2010 at 12:01

• Changed state: Accepted

[GoogleCodeExporter]

Thank you very much! It would be great if you have some time and add 
dtranslations to
the examples :)

The localization file is located at trunk/www/reference/examples/js/locale.js 

I just tested your localization locally, added it to the top lang switcher and
changed all example pages to utf-8. It works great so far :) Unfortunately I
experienced some more bugs and will change from Mootools.Lang.get(...) to our
language object anywhere in the code. I hope I will get this in SVN this 
evening to
allow you playing around :)

Paul, you asked me for translating a 'whole' example page - which one(s) do you
prefere? You said something about split-and-polish the website.. How can we 
combine
these things to save time?

Cheers, Conrad

Original comment by conrad.b...@gmail.com on 6 May 2010 at 2:02

[GoogleCodeExporter]

just uploaded the localization update with russian support :)
Unfortunately some characters are shown as <?> symbols on my computers. I think 
only
in tooltips (Splitter, Panelset resizing for example), but I'm not sure, it 
might be
somewhere else as well. Maybe anyone knows how to avoid this?

Besides from this, It really rocks :)

Original comment by conrad.b...@gmail.com on 6 May 2010 at 9:20

[GoogleCodeExporter]

Mmm, to change characters <?> try to change charset in html code to utf-8:
from 
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

to
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

Original comment by iweb.inbox on 7 May 2010 at 5:48

[GoogleCodeExporter]

Hi again,

string with ru flag:
{label: {set:'Examples',key:'mainToolbar',value:'langRu'}, image:
'http://upload.wikimedia.org/wikipedia/commons/9/9d/Icons-flag-ru.png'}

and attached file with ru example strings.

I test localy, all seems to be ok.

Original comment by iweb.inbox on 7 May 2010 at 6:17

Attachments:

• locale.js

[GoogleCodeExporter]

Thank you :) I already replaced all metatags encodings to utf-8... only some 
*titles*
like in the splitter have a <?> symbol at 4th & 5th position of потяни 
any other text
not in a title seems to look normal. Check out the latest trunk, I added your
localization.

don't know what we can do here.. 

Original comment by conrad.b...@gmail.com on 7 May 2010 at 9:11

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Could you please give me an specific example with <?> characters?

I found miss typing in locale.js, here is new updated file... 

And some bugs:
in mootools there are 2 Russian locales. First in utf-8, second in win-1251.
So Jx needs also 2 locales (there problem with mootools form validation and
jx.russian.locale).
I uploaded 2 files (by default I think must be unicode version).

I tested those files in every example, all looks quite perfect, except context 
menu :)

In tests.js just add this:
if (lang == 'ru-RU')
    lang += '-unicode';
Jx.setLanguage(lang);

And in latest svn example code, notice tooltip "close this notice" showed only 
in
English.

Original comment by iweb.inbox on 7 May 2010 at 4:52

Attachments:

• locale.js
• locale.russian.unicode.js
• locale.russian.js

[GoogleCodeExporter]

I don't completely understand the bug you were pointing out and how (or why) 
these
two should be combined...(?) Could you explain that again?

I added your 2nd file to the trunk too -> and also added -unicode to the string
language switching. It seems for me that nothing has changed with the new file.

There is a screenshot of a splitter example where the title is not showing all
characters correctly. Imagine a mouse behind it :) 

When I tried to use your win-1251 encoded, *no* string was used at all 
(everything
was just the english fallback) - and for me (using netbeans with an utf-8 
configured
project) all Strings are just squares.. (thinking: but maybe this is the 
problem - my
utf-8 netbeans project pre-encodes everything perhaps?)

2 things left: 
- I added 1 localization to the progress bar, could you please translate it :)
  progressBar : {
    runButton : 'Start Progress Bar'
  },
- The notice tooltip is indeed still not changing its language, I also posted 
this in
the main localization issue 154 because I don't have an idea how this could be 
done
with the way notices are built right now.

Original comment by conrad.b...@gmail.com on 7 May 2010 at 7:16

Attachments:

• splitter-russian-title.png

[GoogleCodeExporter]

Hi, Conrad :)

In mootools there 2 locales for form validation "ru-RU" and "ru-RU-unicode" 
(they are
in 1 file Form.Validator.Russian.js). "ru-RU" - is for win-1251 code page,
"ru-RU-unicode" - utf-8. I made first file locale.russian.js in utf-8 and
MooTools.lang.set('ru-RU' ... So this breaks up mootools form validation and Jx 
multi
lang feature (cause language "ru-RU" for mootools in win-1251 but for Jx in 
utf-8).
See screenshot #1. So we have to rename "ru-RU" to "ru-RU-unicode" and add new
"ru-RU" for more compatibility with mootools. See screenshot #2.

In latest svn there broken win-1251 file, so I make 1 file from 2 (like in 
mootools),
to complicate your ability to break it. Just open it in utf-8 and all will be 
ok.

Uff, hope this helps.

Original comment by iweb.inbox on 8 May 2010 at 4:58

Attachments:

• screen-1-with-bug.jpg
• screen-2-without-bug.jpg
• locale.js

[GoogleCodeExporter]

hm, but this method (2 code pages in 1 file) seems doesn't work even in 
mootools form
validation... I'll check this later, have to create simple working example.

Original comment by iweb.inbox on 8 May 2010 at 8:26

[GoogleCodeExporter]

I see, this is indeed complicated :) thanks for the explanation. I'm not very 
deep
into those character sets with different browser/server/client settings :) Let 
me
know if you make any progress with this.

Original comment by conrad.b...@gmail.com on 8 May 2010 at 9:49

[GoogleCodeExporter]

Hi, Conrad again, sorry for all this spam :)

I made some examples for research. And I think JxLib don't needs 'ru-RU' locale 
:)

look at example with win-1251, it doesn't work even on pure mootools:
- http://www.falsecode.ru/blog/demos/mootools/form-validation-win1251.php

but utf-8 works fine:
- http://www.falsecode.ru/blog/demos/mootools/form-validation-utf8.php

and at last I made mix (page with win-1251 charset, and mootools.lang is set to
unicode, at my surprise it works fine:
- http://www.falsecode.ru/blog/demos/mootools/form-validation-win1251-utf8.php

so here is only right file.

uff, hope this helps.

Original comment by iweb.inbox on 8 May 2010 at 3:39

Attachments:

• locale.russian.js

[GoogleCodeExporter]

I added it in r899 and removed the extra unicode file. For me it seems that 
still
everything is working fine except the title of a splitter and the "no" button in
dialog.confirm ... I'dont know what we can do here... maybe write those 
characters in
unicode style &9xa23 ? http://www.tamasoft.co.jp/en/general-info/unicode.html

Original comment by conrad.b...@gmail.com on 10 May 2010 at 8:54

[GoogleCodeExporter]

I got latest svn code and local Russian examples works fine. So I think 
characters in
unicode style are unnecessary.

Original comment by iweb.inbox on 12 May 2010 at 4:39

[GoogleCodeExporter]

ok cool :) Then maybe my computer is just broken (which wouldn't suprise me). 
Paul
how does it look on your machine?

I will add some more translated examples this weekend (I hope) for jxMenu and 
then
try to find out where to reset the menu to have it fit to the new width of 
buttons

Original comment by conrad.b...@gmail.com on 12 May 2010 at 9:18

[GoogleCodeExporter]

Confirmed, splitter tooltip and the "yes" and "no" buttons work fine for me in 
Russian, excellent work!

Original comment by pagameba on 12 May 2010 at 10:58

[GoogleCodeExporter]

I translated the navigation to german too, iweb (what is your real name? :) 
could you 
please translate this into russian? I already copied the object to the russian 
part of 
locales.js 

Thanks, Conrad

Original comment by conrad.b...@gmail.com on 27 May 2010 at 10:08

[GoogleCodeExporter]

My name is Constantine, I don't know why here shows first part of email (At 
groups I 
could be as "insanio" depends on how I answer from site or gmail).

Wow! I like new system of examples!

Original comment by iweb.inbox on 4 Jun 2010 at 3:23

Attachments:

• locale.js

[GoogleCodeExporter]

Thanks Constantine :) added it in r953 

Original comment by conrad.b...@gmail.com on 4 Jun 2010 at 8:25

[GoogleCodeExporter]

Moved to Lighthouse:

http://jxlib.lighthouseapp.com/projects/71243-jxlib/tickets/10-russian-locale

Original comment by jbomgard@gmail.com on 5 Mar 2011 at 5:30

• Changed state: closed