View Single Post
Old 02-07-2026, 11:37 AM   #21
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,789
Karma: 24088595
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by retoid View Post
In order for me to use pyGlossary, what do I need in terms of input?
Any of the supported input files listed on the github page.

Quote:
Originally Posted by retoid View Post
I basically have an unpacked .mobi of the dictionary I want to convert into the working lookup dictionary. So .html and .opf
If both the .html and the .opf file are correctly formatted, you can simply generate the dictionary with KindleGen. (pyGlossary is only needed for converting word lists and other dictionary formats to Kindle dictionaries.)

BTW, if you unpack a working mobi dictionary using Calibre or KindleUnpack you might not get the required .opf file, because Amazon uses some custom <x-metadata> metadata entries that are usually not restored.

They look like this for a monolingual US English dictionary:

Code:
    <x-metadata>
      <DictionaryInLanguage>en-us</DictionaryInLanguage>
      <DictionaryOutLanguage>en-us</DictionaryOutLanguage>
      <DefaultLookupIndex>default</DefaultLookupIndex>
    </x-metadata>
Without this section, KindleGen will treat the source file like a regular book.

For more information see this website and the Kindle Publishing Guidelines.
Doitsu is offline   Reply With Quote