Quote:
Originally Posted by mazdaspeed
In re-reviewing the EULA for Adobe Originals fonts, I must retract part of my previous statement. I'm not providing legal advice.
|
The ultimate topic on this was last year:
(And/or all other responses written by Hitch.)
Long story short, what Adobe says about "our cloud/embedded fonts working in ebooks" is complete hogwash in reality.
Trying to sell such an ebook in any of the actual stores (Amazon, B&N, Kobo, etc.) won't work.
Quote:
Originally Posted by Quoth
1) Don't use Adobe CC Fonts. They won't pass any normal upload for distribution as they are encrypted. Only use unencrypted fonts.
|
Correct.
You'd have to purchase fonts separately and get actual embedded licenses (which cost MUCH more than normal fonts).
(See topic above + the tons of "embedded fonts" topics over the years.)
For example, Hitch's amazing:
or some other minor discussion in:
where I summarized some of the embedded fonts knowledge + referenced Hitch's posts.
(Again, Hitch is the ultimate resource on this topic.)
Quote:
Originally Posted by Quoth
2) Use Indesign for paper, not ebooks. It's a terrible tool for ebooks.
|
Stop this.
If you know how to use Styles properly, it's fine. (Just like Word/LibreOffice with Styles is fine.)
Yes, it's mostly designed for a Print-first workflow, but the ebook section of it is "okay".
You also get more control over HTML/EPUB output compared to Word (
because of Style Mapping).
- - -
Side Note: Yes, a lot of the InDesign output is junk... but if you're one of the 1% that knows how to use it properly...
Side Note #2: I like to bash Adobe/InDesign (and Microsoft) as much as anyone, and will steer people clear when needed or if I think it's the completely wrong tool for the job...
But in this specific case, continuing to use InDesign is fine.
No need to recommend throwing everything out and use completely different tools when it's not applicable to the topic at hand (font embedding stuff).
Quote:
Originally Posted by Quoth
MS Word or LO Writer (extra Save As in docx) and then Sigil or Calibre. Make sure you use paragraph and heading styles sensibly.
|
Yes, of course. Same can be done in InDesign.
And if you use your Styles properly, you can even map:
- Word/LibreOffice Styles <-> InDesign Styles -> HTML/EPUB Classes.
Quote:
Originally Posted by mazdaspeed
Now, many will ask, why are you specifying fonts, anyway? The answer is that I'm creating a Brand. I really don't care what font the end user chooses to read the book with, but I do care what the book looks like the first time the book is opened -- namely, just like the paperback. I would also like to think I'm choosing fonts that are pleasing to read, but that's an expectation beyond this scope.
|
Doesn't work this way in reality.
IF insisting on using embedded fonts, use them very sparingly (headings, title pages, etc.). To try to force them as the body text is asking for trouble.
I won't rehash reasoning why. Read the above topics + the 10+ years of "embedded fonts" discussion on MobileRead.
Print ≠ Cellphones (LCD/OLED) ≠ E-ink
Fonts that work well in one technology won't work well in others.
And lots of the advanced CSS3 that InDesign may insert (font-kerning, letter-spacing, etc.) might "look correct on the surface", but will explode when users decide to change fonts.