[Hitch]

Originally Posted by DLSieving

I meant that I imported the DOCX into Calibre, then went through the input and output options and exported to EPUB. I then opened the EPUB in the Amazon Kindle Previewer, which automatically converts it to MOBI. I then opened the MOBI in the Kindle App and in Apple iBooks. After several iterations I saw everything I wanted to see, including my embedded fonts. I had to remove section and chapter numbers from the DOCX to get *whatever* to not try to infer structure and indent them; it could have been Calibre but was more likely the Kindle Previewer conversion.

Yes--I admit I don't understand what you mean. The Section and Chapter numbers--these are headings and subheadings, is that right?--should render exactly how you styled them, I'd assume. For you and for anyone else that comes along: if you didn't style them as headings, but instead as PARAGRAPHS, and used styling to make them look like headings, then...yes, the KP or KG conversion would assume that you wanted the typical cascading style. That paragraph style has a base style that has a first-line indent. It's not hard to get rid of, but you'd need to either a) style it in Word as an HTML heading or b) you'd have to regex them in HTML, in Sigil or the Calibre editor.

You didn't answer my earlier question, about whether you used only the Stylesheet, or if you used his templates As you used something that you got from Kawasaki. I may know the source of the issue, now that I cogitate on it a bit. Did you use his APE template? And you used his styles? Like the ChapterNumber style? And "Chapter Title?" This APE template is one of my grievances with that book and his templates--they used paragraph classes (styles) for what should be HEADINGS. And thus...your file is inheriting the default, first-line indent for paragraph styles. This problem in rendering can be fixed in 5 minutes or so. You can skip the next paragraph if you don't want to fix them now, which I can certainly understand, but for anyone who comes along later:

Regex the paragraph class and replace it with an H class, e.g., (p class = "section" to h2 class="section") give the H class a suitable name (same name, for that matter, as shown above) and then make sure you use the correct class in the CSS. The styling may even already be available, if it outputs as .section. You may only have to add the heading class to the CSS. Bada-Bing, it ought to be fixed. I'm guessing, of course, because I don't have your book in front of me, but...I've seen this before. With folks that use named PARAGRAPH classes for what should be structural heading classes. They confuse what something looks like--a chapter head--with what it is--a chapter head.

I have not yet looked at the EPUB directly because I'm focused for the moment on KDP. EPUB is just an intermediary output for me right now, though I realize the EPUB will be the branch point for other platforms when I get to that point. I'm focused now on proofing and font licensing.

Did you use a foundry font? I'm merely curious; I'm not the font police. Although, of course, I do indeed like to see IP licensed properly. Did you subset your font?

I have not yet started the Kindle upload process, though I have been through it in the past. I'm hoping my fonts won't be stripped or anything else dumbed down. If they are then I'll be back to the forums and if nothing changes at KDP then I'll be off to another platform starting from the EPUB output.

The font retention/rendering is one of my curiosities, indeed--if your upload retains the fonts. There have been murmurings that Amazon fixed the issue, but we're not taking any chances at my shop, we're still using our secret sauce workaround.

I look forward to hearing back on your upload results. Was I clear enough about the indentation thing?

Hitch