|
Thank you for your quick response, Doitsu. As I mentioned in my initial post, I was hoping to gain some insight into the problem itself.
Incidentally, I did actually buy a Paperwhite 4 at the start of the year, partly for the Russian dictionaries. Unfortunately these only indicate stress in the basic form (headword), as you can see. That is, they do not show the minimum information necessary to determine shifting stress or indeed ambiguous or unusual inflections for newly encountered words. It is true that nominal inflections are occasionally given in the illustrative examples however this is by no means systematic. Verbal inflections are rare in the examples and usually only give on of an aspectual pairs (which are grouped together for the most part). Of all the dictionaries I have tested, the otherwise very good Smirnitsky Ru-En dictionary showed most inflection information, but still no stress. One version I found online of the Ru-En Lingvo Universal dictionary showed decent stress information, but then only patchy inflection (obviously more targeted to Russian speakers learning English)... Unfortunately this renders these dictionaries less useful to my purpose than even Wiktionary (which in any case I do not have in a conversion-ready format for).
Happily, I already found a file for the Малый академический словарь showing both pieces of information and covering a sufficiently wide range of vocabularly. It was a breeze to format that into conversion-ready html and everything works until the lookup problem on the KT (works fine on PW, see below why that doesn't help). To clarify, the lookup shows a list of words (in cyrillic as opposed to the expected latin transliteration), but they do not change with further input although the list does vary in relation to the initial input letter (but it is not an obvious relation).
At the end of the day I actually vastly prefer the UI experience on the KT funnily enough (word lookup, highlighting, pop-up menus). Especially irritating is the PW lookup, which has a short delay after the initial keystroke in which the keyboard momentarily disappears, meaning a search "заниматься" will be entered "зниматься" or even "зиматься". If it wasn't for the higher DPI enabling me to now read fullscreen PDFs, I would have sold the device again and just kept the KT. As my KT does not handle PDFs well, it has become my dictionary device, which is why it also does not help me that my file works fine on my PW lookup.
For the reasons outlined above and in my initial post, I'd like to get the KT lookup to work on my own dictionary. I was hoping to shed some light on why the lookup fails for my user generated dictionary when it clearly works for many other user generated dictionaries on the same device. I know it can be done, I'd like to understand how. I was curious if anyone had any ideas of a more elegant solution than my transliteration idea or if that really how it's done?
Cheers,
|