MobileRead Forums - View Single Post - Kindlegen gets stuck on second xhtml for dictionary creation

Musrar · 09-20-2025, 07:06 PM

Thanks for pointing out the possible route.

I tested the official dictionaries and the same happens. The dictionary only picks up the entries that have есть as their orth value (which are 3 in the RU-EN official dictionary), it ignores the entry for быть, which contains an iform value="есть".

So it's safe to assume that kindle gives priority to orth values over iforms in the sense that if there's an orth value with the same value as an iform value, the entry for the iform value doesn't get picked up.

I'll test option 3 when I have time, seems like the only possible workaround. Considering each entry has between 10 and 20 iforms, this will turn the 76 MB mobi intro a monster, so maybe it's not super feasible.

09-20-2025, 07:06 PM	#14
Musrar Member Posts: 10 Karma: 10 Join Date: Sep 2024 Device: Kindle Oasis	Thanks for pointing out the possible route. I tested the official dictionaries and the same happens. The dictionary only picks up the entries that have есть as their orth value (which are 3 in the RU-EN official dictionary), it ignores the entry for быть, which contains an iform value="есть". So it's safe to assume that kindle gives priority to orth values over iforms in the sense that if there's an orth value with the same value as an iform value, the entry for the iform value doesn't get picked up. I'll test option 3 when I have time, seems like the only possible workaround. Considering each entry has between 10 and 20 iforms, this will turn the 76 MB mobi intro a monster, so maybe it's not super feasible.