Using dictionaries purchased from Kindle Store

[nezih]

Originally Posted by Thorns

Have sent you a PM with the file if you wouldn't mind looking at it? Just the MOBI file. I wasn't sure if allowed to post here publicly. Would really appreciate any advice either way

Alright, from what I gather you first converted the AZW3 to MOBI via calibre which I suppose stripped all dictionary related tags. Instead, you should have unpacked the azw3 directly via KindleUnpack plugin. Then, the script will be able to parse all entries. Here is the preview of resulting stardict file on GoldenDict:

[Thorns]

Originally Posted by nezih

Alright, from what I gather you first converted the AZW3 to MOBI via calibre which I suppose stripped all dictionary related tags. Instead, you should have unpacked the azw3 directly via KindleUnpack plugin. Then, the script will be able to parse all entries. Here is the preview of resulting stardict file on GoldenDict:

Hi, yes the steps I took are as follows. I have the azw3 which has DRM on it.

1. Load up the file in calibre
2. "Convert" the file in calibre to remove the DRM - I converted this to MOBI
3. Use the unpack plugin on the resulting MOBI file
4. Run your script in the mobi7 folder that gets created - this folder has the "book.html" file

Then I received the error.

I have just tried to run the unpack plugin directly without first converting it and it gives an error immediately - i assume because it has DRM on it.

I have also tried to "convert" it to azw3; i.e. just try to remrove the DRM. This works, but when I run the unpack I get a mobi8 folder which doesn't have the html file, and the mobi7 folder which only has the images and no html file so I'm not sure how I can run your script.

Could you please detail how you managed to get it to work? Many thanks again

[nezih]

Originally Posted by Thorns

Hi, yes the steps I took are as follows. I have the azw3 which has DRM on it.

1. Load up the file in calibre
2. "Convert" the file in calibre to remove the DRM - I converted this to MOBI
3. Use the unpack plugin on the resulting MOBI file
4. Run your script in the mobi7 folder that gets created - this folder has the "book.html" file

Then I received the error.

I have just tried to run the unpack plugin directly without first converting it and it gives an error immediately - i assume because it has DRM on it.

I have also tried to "convert" it to azw3; i.e. just try to remrove the DRM. This works, but when I run the unpack I get a mobi8 folder which doesn't have the html file, and the mobi7 folder which only has the images and no html file so I'm not sure how I can run your script.

Could you please detail how you managed to get it to work? Many thanks again

- Renamed the .original_mobi to .azw3
- Dragged and dropped this file to calibre then ran KindleUnpack on it
- In the output mobi7 folder ran the script as below:

python mobi2stardict.py --fix-links --html-file book.html --chunked

[Thorns]

Originally Posted by nezih

- Renamed the .original_mobi to .azw3
- Dragged and dropped this file to calibre then ran KindleUnpack on it
- In the output mobi7 folder ran the script as below:

python mobi2stardict.py --fix-links --html-file book.html --chunked

So when trying the exact same steps I get the following error with the plugin, which is the same error I get when trying to unpack the original azw file directly. How strange!
Is there any way you can share the output?

[Thorns]

OK - I got it to work! I had to use another version of the calibre plugin to get the unloading to work properly. Then I ran the script and copied the contents directly to Koreader and it seems to work perfectly. I attached the version I used incase anyone else needs it.

[nezih]

Originally Posted by Thorns

OK - I got it to work! I had to use another version of the calibre plugin to get the unloading to work properly. Then I ran the script and copied the contents directly to Koreader and it seems to work perfectly. I attached the version I used incase anyone else needs it.

Yeah, I remember modifying my local copy of the plugin to bypass that error. Glad it worked out for you.