Hi,
We are using ePub module version 'Epub 6.x-1.0-BETA2, 2010-08-27' on a Drupal 6.x version.
The problem we have is that node titles appear in the outputted ePub document as 'Table of content items' for docuent navigation, but do not appear in the body of the ePub document. Logically the node title should appear in the body of the text and as a TOC item.
It would become unmanageable to create as second H1 or H2 in the bosy of the text on the Drupal node.
Comments and help appreciated.
Simon
http://metamute.org/ (this isnt the site we're testing on)
| Comment | File | Size | Author |
|---|---|---|---|
| Don’t Panic, Organise! A Mute Special on Struggle in Education Today-1.zip | 69 KB | mrchristian |
Comments
Comment #1
omissis commentedHi, I've tried to open a test epub file I prepared using both Firefox 3.6 extension "ePub Reader" and "Stanza" on an iPod Touch 2G and yes, the "book page"(as Drupal content type) title does only appear in the Table Of Content, so if I got it well you'd like to have the title printed at the beginning of every chapter(ie. of every book page), right?
Comment #2
mrchristian commentedHi Omissis,
Thank you very much for getting back in contact and thanks for the work in the beggining with the module, great stuff.
Yes your correct we'd like to have the title appear in the body of the document as a H1 or equivelnt Chapter heading coding.
As I say this is needed and would be logical, if you look at a printed book a Chapter title appears in the TOC and at the start of a chapter, this could also be the case of child pages too as they are sub sections.
As long as a user adds child pages in the Drupal books module system then can appear as nested items within the ePub TOC and as titles in the ePub book block.
All best
Simon
Comment #3
mrchristian commentedHi Omissis,
We're you able to give any time to looking at the issue of including the chapter title in the body of the book, this is an essential requirement of making a book and fundamental to the book navigation.
If you could let us know if you'll have time to address the situation it would be very much appreciated.
All best
Simon
Comment #4
omissis commentedHi, yeah it's in my schedule for the next weeks, at the moment I'm a bit busy and with the Fosdem/Drupal Dev Days in Brussels this week I fear I have to postpone the thing a little bit more, unless I can find some time for doing a sprint in the proper rooms there, let's see. Anyway yes, I will take some time to fix the issues and port it to 7. I won't abandon this module, don't worry :)
Comment #5
mrchristian commentedHi
Good luck at the Brussels event, ill have a look myself online.
Simon
Comment #6
mrchristian commentedHi
I was looking at the Booki eBook http://openweb.flossmanuals.net/ and its interesting to see how their Table of contents relates to the Chapter titles as they appear in the book body, as sometimes the correlate and other times they dont. Also they all nested categories in the Table of contents, so somehow these nested Headers within a chapter would need to be created from the Drupal doc.
The good thing is that the flossmanuals.net/ project is FLOSS and has a friendly developer team who Im sure would lend some advice if needed.
Cheers
Simon
Comment #7
omissis commentedhi, thanks for the suggestions, I'll have a look at the manual soon.
Comment #8
omissis commentedI have introduced a configuration flag in the admin section(admin/content/epub/settings) for making the node title available in every page of the epub. At the moment is only available in the git master branch, but it'll be released in the beta3 soon together with other bugfixes.
Comment #10
mrchristian commentedHi
Thanks for this omissis, is the githib version the DEV version
Development snapshot from branch: 6.x-1.x Last updated: February 25, 2011 - 07:33
http://drupal.org/node/1002706
Or is the updated github version at a different address (URL).
Thanks
Simon
Comment #11
omissis commentedWell you should be able to git clone the repository this way: git clone --branch 6.x-1.x http://git.drupal.org/project/epub.git
I haven't deeply tested this release though, so beware of dropping it directly in production, since there are some changes that might break your site.