update config attached:

- Comments removed from XML
- Right/Left directions fixed

I found out (the hard way) what breaks by having comments inside XML:

- impossible to generate XML through Xsql
- impossible to generate Voice menu html

Yes, check my addition on the last line to previous post.

I have the same concern, but in theory it looks doable.
There are not that many languages, If I remember correctly 21 languages, some of them just different dialects (en-US, en-CA, en-GB), so the alphabet would be the same.

The logic I am thinking, when building grammar:
 parse the phrases
 remove all non-confirming with selected SR characters (you would just need to have a regex for each language)
 if remaining phrase is empty (or less than defined threshold) then completely ignore it

Of course all of this should be optional to user.  But it is very important especially if it slows down the engine.

For Russian it should be very straight forward as the alphabets in Russian and English are completely different (eventhough some letters look the same, they have a different ASCII code)
For European languages, such as German, it should be no problem also, as I believe German has all the English letters + few accented and national.  In any case for some languages the regex can be empty if it is not required.

And you already know what language is selected for SR, so no need to detect it

Btw, can you create a grammar xml file (not compiled) from the backup I've sent you, there we can probably see if the SR ignores the non-cyrillic characters or not?  If it does, then nothing needs to be done.
 

User generated OSD I've tested today and it works perfectly.  Only event driven have an issue.

I'll take a look at creating a regex to strip unneeded characters, but I am not a regex expert either

You were definitely not rude

The recheck mic option I enabled just to see if it will help the mic initialization issue.  I did not make any difference.  Btw, I never had this issue playing with VC1 using English SR.

I think most issues with my music collection are "bad" tags in mp3 files (some are uft8 while some are not), I don't really listen to music through XBMC, so I never bothered to fix it. I will remove all songs from the XMLs to see if it helps.

So comments can't be added to payload XMLs?  I put them there, so it will be easier to understand later what each view is actually is (for ppl that don't read Russian).

Dealing with English texts on non-English SR is definitely something to take a look at, as I would suspect that many ppl would have the same issue, as very often the scrappers do not find localized translations for movie/song/artist info.  I was under impression that it just ignores it, as I do not have any issues with recognition.  If there is a problem then maybe when building grammar files you can filter the entries with regex or something similar to remove all characters that are not present in the selected SR culture.  It could be that you did not have this issue earlier as German or Portuguese alphabet is almost the same as English and SR just tries to recognize it phonetically.

Regarding XJson OSD notifications, I've seen earlier on forum someone asked about similar issue, and you provided a fixed xjson.dll, but that was for VC1, where the same fix applied for version 2?
On the screenshot I posted I am using voice command "Take screenshot", there are no alternatives offered.  So most likely it should have "сделай снимок" (which is take screenshot in Russian) on the left top corner in XBMC.   It looks like some issue with UTF8 encoding/decoding.

Here is the backup.

The problem phrase is in the .\payloads\xbmc_aeon_mq5_viewmodes.xml

Also something is going on with the OSD display of commands in XBMC.  Very often I get gibberish for both the title or the message. See attached screenshot.

I've tested the GUI.ShowNotification and it properly displays both English and Russian.  Actually I am not even sure what sends the info to OSD, as for example the take screenshot command does't have any notification actions.

1. Very slow microphone initialization.  After startup or rebuilding it takes 1-2 minutes for the mic to become active.
This is what I see in log file:

15.04.2014 18:41:10 504 unable to reset speech engine: System.InvalidOperationException: Cannot perform this operation while the recognizer is doing recognition.
   в Microsoft.Speech.Recognition.RecognizerBase.SetInputToDefaultAudioDevice()
   в eval_e.eval_ᜎ()

2. When I was creating payload XML, I had an issue that one of the payload phrases was too long.
When that happened none of the phrases from this XML worked, and Vox crashed when I tried to edit the XML through the build-in editor.

Btw, what is maximum phrase length?  My phrase was:
<phrase>инфо баннер, инфо баннеры, информационный баннер, информационные баннеры</phrase>
I had to remove the last option for the phrase to get accepted.

I've updated XBMC Russian commands.

Now the only untranslated part remaining are the sort orders.

Changes:
- "Activate XBMC screens" payload XML created, added some of the screens that were missing in original payload list, also removed duplicates from other sections of commands list
- Aeon MQ5 viewmodes payload XML created, covers all of 15+ MQ5 views, existing MQ2 payload XML kept, if someone needs it edit the "Activate Window" command to use the old "aeon viewmodes.xml"
   if someone wants to use it for other languages I've added comments to the XML, so it is easy to understand what view it is.
- some misc changes and fixes


Please note I am using nightly builds of XBMC (which is XBMC Gotham beta 3+ currently) with Aeon MQ5 skin.

Yes, Alt-F4 is fine for me

But take a look at LCB and option window, in neither of them Escape does anything at all.

In the command tree you are correct, it much better there to Escape editing the labels or payloads than close the window.

Preferably all that have a Cancel button, for example options dialog, LCB dialog.
And actually dialogs for plugin settings could do that too, as the way it is right now, it is not too clear (for novice users) how to close those dialogs without saving settings.

Some notes/requests for future:

Currently if you install Version 2 and you do not have en-US speech recognizer language installed, the VoxCommandoSP.exe will fail to start.
To overcome this issue, either:

• install en-US
• or run VoxCommando.exe go into options and change Speech Recognizer Culture to ru-RU, after that the VoxCommandoSP.exe will start correctly
• or unpack the configuration file I've supplied in previous post

And a small request: would it be possible for Escape key to close dialogs in Vox?

P.S. James, if you send me the XML for Display language, I can translate it to Russian too.

I've translated XBMC commands to Russian.

I've translated most of the items (~80%), except some of the test items and items that use payload lists (ex. focus window), these need to be changed to payload xml, I might do it later if there is interest in it.
All of the TTS.Speak commands are changed to TTSMS.Speak, as the default Russian TTS voice (in windows 8 ) sounds very bad.  The voice that comes with the Speech Platform sounds much better.
Live TV commands were added to config.

Ensure that your movies/albums/tv channels are scrapped correctly, the titles, actor names, genres, etc must be in Russian, otherwise you will not be able to select it by name or title.

I've also changed some of the options:
TTSMS plugin is enabled
Speech Culture is set to ru-RU
Speech recognizer is set to Microsoft Server Speech Recognition Language - TELE (ru-RU)