New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kindle App confused by books with the same title #60

HarryT-MR opened this Issue Jan 2, 2014 · 1 comment


None yet
2 participants

HarryT-MR commented Jan 2, 2014

I have two books in my Calibre library with the same title, but different authors. Both the books are called "Conqueror"; one is written by Stephen Baxter, the other by S.M. Stirling. When I try to send them to the Kindle App on my iPad Mini, the following sequence of events occurs:

  1. I send the Baxter book to the device. It successfully appears in the library of the Kindle App, and opening it shows that it's the correct book.
  2. I send the Stirling book to the device. Nothing apparently changes in the Kindle App library - it still lists "Conqueror" by Stephen Baxter, but when I open the book I find that it's now the Stirling book of the same title.

This is absolutely reproducible - the first book to be sent appears in the library; the second overwrites it, but without altering the library entry in the Kindle App (so you see the wrong book when you open it).

I suspect that what's happening is that the plug-in is simply using the book's title as the filename, so the first book is being overwritten by the second. The "Send to Device" template in "Preferences" does not appear to be being honoured.

I've worked around the issue by slightly changing the title of one of the two books, but if this could be fixed (eg by using the filename template specified in "Send to Device", it would be useful.




This comment has been minimized.


GRiker commented Jan 2, 2014

I've updated the plugin to version 1.3.3. Generated filenames now include the first author, which should disambiguate books with the same title.

@GRiker GRiker closed this Jan 2, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment