The project is a 152-page book. It was ''created'' in ID CS4 and is straight text except for the publisher's logo, which appears on the title page. Each chapter is its own file, as is each element of the front matter. Three fonts are used in the publication: Arial, Formata, and Palatino. The Formata and Palatino fonts are OT fonts; they were newly purchased as OT fonts for this client. Each use of italic or bold in the book's text, excluding heads, is by a character style that includes the font family name. For example, if the text is supposed to be Palatino Italic, the character style includes both bits of information, a generic Italic is not used.
I combined all of the elements of the project into a single ID Book, which is what I used to update numbering, etc. When I export to PDF from the Book, everything works fine. When I export to Adobe Digital Editions from the Book, the following occurs:
1. Arial and Palatino are embedded but Formata is not.
2. The first and last files of the Book (i.e., the title page and the References) appear in the ePub file and are viewable in the ADE viewer, but everything between those two files, including all of the text chapters, are empty files that appear as blank pages in the ADE viewer.
What am I doing wrong? How do I
a. Get Formata embedded?
b. Get the complete project into an ePub file?
Another thought: Would the way to do this be to do each chapter as a separate export to ADE and then combine each of the separate files into a single ePub file? If so, how would one do this? I've noted that when creating an ePub file several additional informational files are created. It isn't clear to me how one would combine that information.
Also, is there a good source and/or book (or several sources and/or books) that gives step-by-step instruction information on turning a project into an ePub file? Although this project has no graphics, tables, etc., future projects will have numerous graphics, tables, etc. and so any help will be appreciated.
Thanks.
ID CS4 and Adobe Digital Editions
Adobe Tech Support has solved the problem. Apparently a corruption was caused in the files by my having third-party plug-ins installed, even though I hadn't used any of them for this project. Removal of the plug-ins and then copying the files to new ID documents will solve the problem, according to Tech Support.
ID CS4 and Adobe Digital Editions
Interesting, thanks for the update!
What plug-ins were they and where do you find them to remove them? This sounds similar to the problem I'm having exporting to epub from a trial IDCS4 - The most recent chapter I've created in Indesign is not being fully recognised in DE. The navigation bar says the chapter is there but it views blank and when I've unzipped the epub the XHMTL file is there but unlike the other chapters the content hasn't exported through, it is blank again.
These were third-party plugins like MultiDo. I had installed them because they were recommended but never used them. The plugins are not the plugins that come with CS4.
The way I finally got my book to export to ADE was to create a whole new document from scratch and then copying the text from the old document the new document. I found that one of the problems was in linking of the frames, so what I had to to do was create a single file of the entire project for the export rather than separate files for each chapter.
Adobe really needs to work on its ebook production scheme. It doesn't work very well and there is no easy way to find out why something is not exporting correctly. A better and specialized preflight system is needed.
Yes, I can't believe how little step-by-step instruction there is for ebook production, it has been daunting and frustrating trying to work things out piecemeal.
Am I understanding correctly though, instead of breaking the book up into separate indesign docs you have one large indesign file? I understood that most books would create too large a XHMTL file done that way for readers to cope with. And how are you able to navigate chapters, won't it lack a table of contents in Digital Editions?
Hope an adobe bod will look over this thread shortly...
Hi
Sorry it took me so long to find this thread, I'm not up here much.
Book Export:
---------------------
Yes, it is really very broken. Unfortunately it hadn't been recognized as broken in time for the 6.0.1 update, so the fix will have to be in a future release.
There is a work around, but it's not really a workable solution. We'll work on getting this fixed.
Font Embedding:
--------------------
If you got a warning saying that Formata could not be embedded, then the font wasn't found (was it in a suitcase, or otherwise not in a normal location.)
If you did not get a warning, then the font is probably embedded in the document, but not *used* by the document. If this is the case, and you're comfortable with editing CSS you could potentially fix the CSS rules yourself. This tool would probably help a little: http://blogs.adobe.com/digitaleditions/2008/10/a_great_tool_for_making_small.ht ml
Contents for single Document:
--------------------
Even when you work with a single document, you can use the TOC Style feature to create the Contents panel in ADE.
You need a TOCStyle with the appropriate paragraph styles set to the levels you'd like. Then you need to go to the ''Contents'' panel during export. You'll probably want to turn on both check boxes in the ''Table of Contents'' section. That is to say, you'll want to turn on the ''Include InDesign TOC Entries'', choose the TOC Style that you've set up for EPUB, and then turn on ''Suppress Automatic Entries for Documents.'' (Unless you want both chapter names and file names in the TOC.)
HTH,
Paul
Hi Paul,
My problem with blank sections in the EPUB export has been with Technical support for over a fortnight now. I really hope someone will actually call me to explain how CS4 is 'really very broken' (the first I've heard of this) and what the work around is and its limitations are. And how long we will need to wait for an update that will sort out this issue properly.
Ebook production was the only reason my company upgraded to CS4, understanding that CS4 was better enabled to move on that front and annoyingly we couldn't upgrade just Indesign, but had to buy the entire suite. Thus far it has really not been worth the money.
I look forward to hearing from Adobe shortly.
Lesley
%26gt; annoyingly we couldn't upgrade just Indesign, but had to buy the
%26gt; entire suite.
Indesign, all by itself, can certainly be upgraded to a newer version of
Indesign. The Creative Suite can be upgraded to a newer version of the
Suite. But you can't upgrade the Suite to a newer version of Indesign.
--
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com
Yes, I am painfully aware of that. So not only did we have to pay for versions of photoshop etc that we didn't really need, but Indesign which we did want has been no use so far.
A month on from submitting the problem to tech support and I am still to have any feedback or advice from Adobe regarding this problem, despite numerous calls.
I thought others might find this response from tech support useful, especially if you're considering upgrading to CS4 as we have:
''After testing at our end, we can confirm that there is a current limitation in InDesign CS4 where content is dropped during Digital Editions Export when 2 or more documents are included in a book.
Engineering is working on a fix, which will hopefully be released soon
although we can not estimate an exact date.''
I'm pushing for some kind of eta so I can judge whether we need to return our copy of CS4 to Amazon (that'll be fun explaining that to them) and whether we need to start farming work out to conversion houses.
I was very glad to find this thread, as I am having the very same problem. So now I can stop trying to figure out what I'm doing wrong and expend my energy seeking a different approach while waiting for the fix.
I am glad to find this thread also. I'm having the same problems.
Exporting to to epub (DTbook) drops both pages and fonts. Still working on it, but it looks like the best solution is keeping the file in Word, doing as much formatting as possible there and exporting from there. It seems counterproductive to maintain two versions of the file (and convince the editors that this is how it needs to happen), but Word seems to have the most reliable options for export.
No comments:
Post a Comment