View Single Post
Old 05-03-2015, 09:29 PM   #4
susan_cassidy
Wizard
susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.susan_cassidy ought to be getting tired of karma fortunes by now.
 
Posts: 2,251
Karma: 3720310
Join Date: Jan 2009
Location: USA
Device: Kindle, iPad (not used much for reading)
If you want the dictionary to be used in a book encoded for English, yes, it has to be encoded as English.

Just use a tool like Calibre to change the language encoding as needed. No tutorial needed, unless you need one for Calibre.

Yes, a dictionary with a prc file extension should work, but you don't ordinarily see them. Usually you see mobi or azw.

Windows relies heavily on file extensions, Linux does not. Kindle apparently does care, though, even though it is Linux. Does your application work if the file extension is associated with that application? You probably wouldn't want to leave the pc that way, though, as you would normally want ePub to be associated with a reading app.

I have not heard of any changes to dictionary formatting since the Kindle 1.
susan_cassidy is offline   Reply With Quote