Welcome to Writers Talkback. If you are a new user, your account will have to be approved manually to prevent spam. Please bear with us in the meantime
Just bumping this up as I'm getting desperate.
Okay: still going round the bend here. I'm trying to change the dropped caps at the beginnings of the chapters. Today I've cleared everything from the chapter title (underneath Chapter One etc) to a full line or more past the capital. The result is that all that text turns up in large bold letters on the Kindle previewer. The more text I delete, whether changed in Word doc or changed into RTF and put back, the more bold text appears.
Just for fun, a totally random line and a half midway through Ch 3 is turning up in bold too, and I haven't touched that.
The changes I've made to indents and to a couple of typos in the forematter have taken; this text is all in the body of the text, which is separated from the forematter by a break.
I've changed the indents after scene breaks, and they have worked all the way through. It's just the wretched drop caps that won't change successfully.
Losing the will to live here. Help! again.
Comments
The problem with the varying indents: how did you create your indents? If they were tabbed you will have issues.
The indents were all done as page layout, not tabbed. I've been able to change the ones after the section breaks by pressing the back arrow, with no problems in the kindle version.
Whether the wandering indents are a knock-on from having written in Scrivener and then exported to Word, I don't know. The drop caps were added after I'd exported to Word.
The apostrophes are straight and that's a Scrivener issue – they're at odds with the serif font. You only need to 'select all' and then 'replace all' to correct them. But you would need to ensure none were 'turned' – that's not easy to spot when they're straight.
The Scrivener usage possibly explains the hyphen-en dash problem.
If I'd done the Kindle version first, I (probably) wouldn't have had this problem.
Yes, I think it was changing font in Word from a Scrivener document export that caused the dash problem.
I'm all computered out now. Even Mr Bear, the resident techie and all-round (not to mention all round) computer go-to man has had enough.