It's The Way You Say It Epub
Stephanie Dejoode
Also notice the resolution: if you are using the ipad Retina document preset, set this resolution to 72. Do this also when exporting your epub, because InDesign exports the graphics at the native resolution of the device you selected when 72ppi is selected.
If you are working with the Kindle Fire/Nook document preset, again choose 72ppi for both the object export resolution as well as the epub publishing resolution, because any value over 72ppi will generate image assets which are much larger and eat up more file space then required. Just remember that InDesign will export the images at the exact required selected device's document preset's resolution when 72ppi is used.
PS one more thing to look out for when converting a FXL epub to Kindle: transparency in PNG files is converted to white, and the transparency is discarded. (You will notice this when opening such a FXL epub with transparent PNG files in the Kindle Previewer).
The problem is the lack of viable reader apps. I would never even attempt a fixed layout epub out of InDesign destined for anything other than iPads or Macs. Readium is making some progress but it's not ready, yet and I don't know when it will be.
This suggestion to rasterise seems to be completely wrong. If the book happens to have a very complex layout where accuracy is critical (for example a maths text book) this may be the only solution. But otherwise, rasterising severely reduces usability for the reader of the file (quality may suffer, can't reflow, can't search...) So this should only be done if the designer feels esthetics are more important than usability (I wouldn't employ a designer who felt that, but your mileage may vary). Is it really more important to keep exact font and kerning than, for example, the ability to search for the word you kerned so carefully? My tip: if you're going to epub be prepared to LET GO... learn about the medium, it's strengths and weaknesses and work with them, even if your fancy design is compromised.
You're right about reflowable, but I'll disagree about fixed layout not being able to handle some kerning. If you crack one open and dive into the mark up, you'll find a complete mess which is what's needed to make it fixed so kerning shouldn't really cause a need for this unless it's dramatic.
In the end, I changed the font for epub & it's working. All typekit fonts will not work with fixed epubs. Big lesson learned. Thanks for all of your input. Much appreciated.
Someone noted to just pdf & be done. I didn't think kdp would accept Adobe pdf ? the kindle previewer doesn't recognize pdfs. Could the client download a pdf to kdp for a fixed ebook?
Yes, always... thanks for the reminder Derek. This was the first epub I've created that didn't use a 'Pro' font for the main body. Ended up using Typekit Scala Sans 'Pro' font. So far, that's the only difference I can see from other successful epubs I've created.
Upon further review, fonts are still corrupt. Fixed epub file views fine with previewer on both mine & clients end. It's after the Amazon upload when the fonts get corrupted with terrible crashes. Any help would be appreciated. Fonts used are OpenType Type1 from Typekit.
I have an ebook that I'm trying to make adjustments to. When I load it on my Nook Simple Touch, it has large margins, ignoring the settings on the Nook to have a minimal margin. When going through the HTML for the ebook, nothing jumps out at me as causing this large margin. After I make changes to the CSS, I need to package the files back up as an epub, copy the file to my Nook, and then see if I fixed it. That whole process is time consuming, especially since I'm testing one minor change to the CSS at a time.
I know Amazon wants us to stop using mobi and start using epub format for books sent via email. Today I emailed 12 books to my Kindle account. 9 of them worked and 3 of them failed. I get a reply email from Amazon saying the book "could not be delivered." I cannot see any difference between the books that worked and those that didn't.
None of these techniques worked -- the book still failed. Any idea why some books would fail and others would not? I do not think it's a problem with Calibre, but I thought this group might have some idea what's going on.
If you email it to yourself as attachments that you can download, so that it's on an email address on your iPad, you can open the ePubs and it'll add them to the books feature. Assuming, of course, you're on the latest iOS.
I don't see how Logos could get in trouble for allowing EPUB file types to be imported. If someone were to use that function in a blatantly illegal way, then it's certainly their responsibility and not the Software they use. If it were the case that Logos would be liable for allowing import of EPUB file types, then Calibre has all sorts of problems on their hands! :-)
A .epub file, as noted in other answers, is essentially a zipped up file. When iBooks imports the .epub file, the .epub file it stores is an unzipped file. This explains why it has the Show Package Contents option which lets you explore the "unzipped" files. However, just zipping the package doesn't always work.
I had more than 2,000 .epub packages I wanted to convert to .epub files, so the above method wasn't feasible. To avoid the manual labor, I wrote a script that essentially runs the above method on all the files. I used the simple and elegant shell code provided by Matthias here and wrapped it in a python script shared below:
The extract_filename function takes a path to a directory that contains the .epub packages that need to be converted.[WARNING] It is best to work on a copy of the .epub packages in case something goes wrong. To be safe, just copy the packages to a different directory and work on that.
The create_epub function takes a path to a directory where you want to store the generated files. It then runs a shell command to open each .epub package and generate a .epub file.
As far as I can tell, compression does not need to be deactivated (-0). epubcheck has no complaints. There might be differences between versions of the epub spec, however. My test was with an epub 3.0 file.
This would imply that it's not completely straightforward to recreate with a simple zip app. However, it may be simpler than that.
Let's assume nothing has actually unpacked it, merely got confused about how to deal with it. Work on a copy.
There are a wide range of EPUB 3 reading apps available and the reading app evaluation available at epubtest.org helps the reader make the correct choice for them giving them the best access to their downloaded documents. There is also a quick roundup of these results on Inclusive Publishing to help beginners get started.
EPUB is an e-book file format that uses the ".epub" file extension. The term is short for electronic publication and is sometimes styled ePub. EPUB is supported by many e-readers, and compatible software is available for most smartphones, tablets, and computers. EPUB is a technical standard published by the International Digital Publishing Forum (IDPF). It became an official standard of the IDPF in September 2007, superseding the older Open eBook (OEB) standard.[2]
The mimetype file must be a text document in ASCII that contains the string application/epub+zip. It must also be uncompressed, unencrypted, and the first file in the ZIP archive. This file provides a more reliable way for applications to identify the mimetype of the file than just the .epub extension.[17]
EPUB 3.2 was announced in 2018,[26] and the final specification was released in 2019.[27] A notable change is the removal of a specialized subset of CSS, enabling the use of non-epub-prefixed properties. The references to HTML and SVG standards are also updated to "newest version available", as opposed to a fixed version in time.[28]
The first file in the archive must be the mimetype file. It must be unencrypted and uncompressed so that non-ZIP utilities can read the mimetype. The mimetype file must be an ASCII file that contains the string "application/epub+zip". This file provides a more reliable way for applications to identify the mimetype of the file than just the .epub extension.[51]
In the xhtml I would need it to be represented as an SVG inside the page with the text placed in the elements. In other words, it needs to be selectable in the web browser, because this will need to be used in readloud epubs where we need to be able to apply styles to elements.
It's possible it might not work either, some CSS customizations are not recognized by e-readers. To modify the epub kindle file and its content, you can use software such as "Calibre", it's free. To modify the CSS/html you can use whatever you feel comfortable with; it could be Dreamweaver or opening the css/html in a text editor.
If you decide to use a svg, you could have a look at these posts below and insert your svg manually in your epub as well; there's a few ways to do it but for epub, you're limited. One thing though, it's possible it won't work well on some e-readers or screen readers.
The only other option might be to use a straight line of text if you don't want to insert any code yourself and export only from Indesign. That would be safest option as well even though it's not the fanciest!
What about: (1) doc file to HTML through Mobi Pocket Creator (2) build table of contents in SIGIL on HTML file, (3) export as EPUB to Calibre, (4) convert epub to MOBI file in Calibre, (5) sell on Amazon?
aa06259810