Update russian.js #356
Update russian.js #356
Conversation
ihsoft
commented
Jun 6, 2015
ihsoft
commented
- Access language settings via a dictionary key instead of object property.
- Change "alt" to the same caption as Russian Windows 8 shows (RUS: Russian keyboard).
- Translate "Accept/Cancel/Change sign" since these captions are not commonly recognized in Russian.
- Translate "Space" since in most virtual keyboards it's translated as "Пробел".
- Access language settings via a dictionary key instead of object property. - Change "alt" to the same caption as Russian Windows 8 shows (RUS: Russian keyboard). - Translate "Accept/Cancel/Change sign" since these captions are not commonly recognized in Russian. - Translate "Space" since in most virtual keyboards it's translated as "Пробел".
Less common translation of the keyboard:
- Language name is displayed in Russian as "Русский". Though, word "Russian" is well recognized by native speakers.
- "Backspace" and "Shift" don't have non-weird one-word translations so, they are replaced by icons and verbose explanation moved to the title.
- "Space" is well recognized by its direct translation and doesn't need title (it would be exactly the same as key caption).
- "Enter" is well recognized word but in many cases it's translated as "Ввод" which is well recognized too. Though, title ("Line feed") may be misleading when used in non-multiline controls.
|
Hi @ihsoft! Thanks! |
|
You're welcome :) It's a great plugin! Unfortunately, I had stop using it in my project because of jQuery UI + keyboard is extremly slow on the target device (LG SmartTV 2012): a dialog with vitual keyboard controls opens 5-6 seconds :( I've spent hours tyring to figure out why but eventually gave up. Though, I used your ideas in my own simplified solution (pure jQuery, minimal functionality) and decided to keep compatibility with the Mottie Keyboard layout files because I see them doing the job very well. Why inventing the wheel, right? :) |
|
jQuery UI is an optional dependency. The default plugin uses the jQuery UI theme & position utility, but neither are needed if you modify the class definitions (see the Bootstrap demo on the main page), and position the keyboard manually. Alternatively, you could build a custom version of jQuery UI with only the stylesheet & position utility. |
|
Well, I don't remember for sure what was the problem but when I ran keyboard w/o UI it was awful. Basically, that's how UI appeared in my project in the first place. Now I think it was a wrong idea, and I'm going to remove UI dependencies despite of the convenience they offer. When you run a 1Ghz single core processor with 1Gb of memory things look different. |
What do you mean? Is there a specific issue that needs to be addressed? I made this demo which is using a Bootstrap theme without jQuery UI loaded. It doesn't look too bad to me, but I am a bit biased 😉 |
