Forum Replies Created
-
AuthorPosts
-
incblot
MemberA different question about endnotes:
I’m setting a book with 400 endnotes. In the Word doc, the endnote numbering starts again at each chapter. When I place the text into ID, this is not honoured and endnote numbering runs from 1–400.
Is there a way to honour the Word doc setting and start the endnote numbering again at each new chapter?
MemberPooja, Thanks for the clarification!
Yes, iBooks is its own beast. Safari not honouring the margins worries me more. It leaves me wondering how other reading devices will react.
I also can’t understand why having two stylesheets is causing a conflict, even when both css files are adjusted to the same setting.
MemberThanks Pooja, that fix is indeed very helpful!
I have a question regarding point 6, if you might assist?
I am using a preexisting css (template.css) alongside the ID generated css (idGeneratedStyles.css). I’ve set margins to 150px in IDCC during export (nb: using a large margin of 150px to exaggerate its effect for testing). The idGeneratedStyles.css shows:
@page {
margin : 150px 150px 150px 150px;
}The template.css shows:
@page {
margin : 0.5em;
}Yet the text is not indented. I have tried deleting this from template.css:
@page {
margin : 0.5em;
}But it has no effect.
If I export the epub from IDCC without adding my own template, the 150px margins work in Adobe Digital Editions, but not in Safari or iBooks.
Could you please explain what is happening?
MemberPooja, thanks very much for your reply!
3. The cover issue is fine. I did prefer having control of this but I shall submit to the wisdom of EPUB3.
5. I tried again and encountered the exact problem. The CSS is: font-family:”Georgia (OTF) Regular”, sans-serif
I’ve defined Georgia with the paragraph style, no overrides. I suspect this is not a widespread problem then, possibly something to do with my font management program’s relationship to IDCC (Suitcase Fusion 4). I actually delete Georgia from my CSS anyway (I still design without embedded fonts, as I learnt to create ebooks when embedding fonts was riddled with problems – I’m happy to let the readers define the font until I’m confident any design embellishments will not cause problems on any reading platforms [has this day come yet?], but I find this glitch strange/new, so thought worth mentioning)
6. Thanks for the tip, I’d overlooked that option. I only seem to be able to add pixel for the margin, not ems, but I’m glad I can experiment with that in ID. Does anyone have a recommended pixel with for standard margins?
8. I find this a really odd problem. Can anyone explain exactly what this means and why it has changed (I cannot see any benefit, but would like to be enlightened if there is one). Also, are there any foreseeable problems not having the ISBN in these fields (which seems the easiest fix to output a valid epub file)?
Thanks for continuing the conversation. I’m only on my second book via IDCC (after years in CS5.5), so its early days, early days.
MemberThanks for the reply, Anne-Marie! I’d read the adobe list of updates but not that article. Impressive.
Haven’t yet taken advantage of any new features – just trying to keep up with publication dates for our books/ebooks. Spent my time trying to work around the above list of changes after exporting my first IDCC generated epub.
I’ve completed my first ebook after the switch, will endeavor to make some notes about it as time allows. For now, I’m reverting to CS5.5 as deadlines loom.
Re number 8: I’m under the impression some retailers use the UID for the ISBN (as well as the uploaded metadata spreadsheet); as I’ve made an error in the past and not updated the ISBN in the UID, which resulted in one epub replacing another. Perhaps it was a unique case.
MemberHowever, I've downloaded the iBookstore EPUB Example 1.3, and not all the book elements are in the <guide> block. Go figure?
MemberI'm currently reading the iBookstore Asset Guide 4.7 Rev.3.
It seems my first problem was not including all the book elements in the <guide> block.
I'm also surprised to learn that page breaks do exist! I hadn't had any luck with InDesign's keep options, so this is promising:
To indicate that a page break should come before or after an element, set up a style in CSS using the
page-break-before or page-break-after properties. Accepted values for these properties include:
? auto: Insert a page break before or after the element as necessary
? always: Insert a page break before or after the elementJune 30, 2011 at 2:38 am in reply to: InDesign CS5.5 to EPUB, Kindle, and iPad by Ann-Marie Concepcion #59964MemberWould love to see the CS5.5 instalment. I'm currently enjoying the CS5 version while working in CS5.5. Most of the information remains relevant.
Epubs are a new world to me and I've learnt a lot (more than I would have hoped necessary!) but still have a long way to go. If I might put a request out there (food for thought perhaps), there are some basic elements I would like to see covered in future instalments (or perhaps I missed them, or I could find tutorials elsewhere?).
For instance, I'm converting books that we typeset for print in InDesign. Many of our books include Section Breaks and Chapter Breaks. Quite often we will have a Dedication or an Epigraph on its own page with no title. In keeping with the print edition, I want each Section Page to appear on a new page, with only the Section Title on it. Likewise, I want all our New Chapters to start on a new page. But because I can only 'Break Document at [one] Paragraph Style' this is made difficult (and I have limited coding expertise!). I wish InDesign included an option to 'Break Document at [multiple] Paragraph Style[s]' so we could set multiple para styles at specific levels (al la the ToC Style options) to create a nice simple parent/child TOC file with all the correct page breaks.
As far as single pages with no titles, such as Epigraphs or Dedications, I began adding generic page titles [eg Epigraph, Dedication], styling them with my New Chapter para style (which I use to Break Doc at), and then effectively 'hid the text' by colouring it with a white swatch. This way it appears in the TOC as 'Epigraph'; and the Epigraph page appears as a new page without a visible title on screen – but it seems so silly – there must be a better way. Same goes for Section Breaks (I could use character styles to differentiate the style from the New Chapter para style, but ideally I want the Section Titles centred and the Chapter Titles left aligned, so I need to do that in paragraph styles).I'd love to see a video cover this sort of multi-level TOC construction that also catered for the relevant page breaks. While I'm rabbiting on here, I'd also love to see some tutorials on dealing with references, footnotes, endnotes, indexes – some of the common things we deal with in many print books, but I still feel unsure how to reproduce in epubs.
All this said, I hope I haven't threadjacked and diverted too much. Greatest respect for your talents and teaching ability, and I’ll happily finish off the CS5 vids as I await the CS5.5 instalment.
MemberLasatalayas: would this be relevant to an InDesign document that has all the text for the entire book in a single document/frame?
-
AuthorPosts