-
Notifications
You must be signed in to change notification settings - Fork 33
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
Periodical navigation buggy on Kindle Touch #5
Comments
Hi @danchoi - thanks for reporting this problem. Unfortunately, I don't see any reasonable way to go about solving this type of problem at the moment. I don't see the problem you describe on my Kindle 3rd generation, but there are certainly more subtle problems with the navigation on that device as well. Unless someone gets hold of a |
@mhl The problem is specific to the Kindle Touch. I actually solved the problem by tinkering for an hour with the NCX and OPF section. I'm not sure exactly how I did it yet, but I'll let you know when I've pinned this down. Thank you for writing and releasing this script. |
Great :) I look forward to hearing what the required changes are - perhaps they will fix some of the other problems too... |
This is what I think I did. Here is a gist for reference. The top is an opf generated by your Python script. The bottom is an opf generated by my Ruby script. I also include the nav-contents.ncx that my script generated. https://gist.github.com/1589856 What's different about mine is that I have manifest items not just for each article but also each section. Also, in the I hope this is clear enough and that it helps. I'm not 100% percent sure that everything I changed is necessary to get the navigation working on the Kindle touch, but at least some of it is, based on my experiments. |
I generated a MOBI file for the guardian using the Python script and copied it to my Kindle Touch. Most of it works well, except the two-column table of contents. If you click the Sections on the left, the Articles on the right do not update correctly.
The text was updated successfully, but these errors were encountered: