Sheesh…I know I’m a slow reader, but this is ridiculous. Just had a bunch of things interfere. But almost done now, and it is such a treat. Sasha and Pyetr are so cute!
It’s a bit tedious…I’m going through and cleaning up all the html junque WYSIWYG programs put in. I’m not sure how Namo is creating these smart quotes. They just show up as angled quotes in the html panel. I hope they work when we take the file into other formats. If not, I s/b able to do a search and replace with the decimal numeric codes fairly quickly.
We’ve pretty much decided not to justify the right side of the text. Since this will be “flowable”, right justified text on the smaller screens might be pretty unpleasantly spaced. It won’t look as “published book” I suppose, but I think it s/b more universally attractive and readable.
Skating went well today. Got to see OSG, which is always nice. She’s looking strong. I think her workouts are really paying off.
Ja ne!
OSG said we wouldn’t recognize her when we see her next!
Her smile never changes. :D
I am determined to get my kittenish figure back!
One of these days I’m going to write about Pretty Page versus Transparent Page, but for now, for e-book purposes, think audio not print when formatting. If something, such as full justification, or Drop Caps, or font changes, wouldn’t happen in audio, don’t do it!
The human reader wants the story. Decorative stuff is either ignored or gets in the way.
Currently struggling to get books to look decent in Kindle format (lots of fun without having a Kindle!) One thing I’ve found is that numerical/Unicode stuff for things like curly quotes does not work for Kindle. Have to use the & l d q u o ; (without the spaces) type of codes rather than the Unicode numerical codes.
Aargh! Just found out the Kindle converter does not do WP Typographic Symbols. It does weird symbols, sorta. Actually, not so much weird as out of place. Example the open double quote is rendred as some sort of capital A and Word’s Find can’t tell the difference.
Author orignally wrote in WordPerfect, converted to Word for editing. I didn’t catch it because I have both on my system and Word just used the WordPerfect font. Had to delete the font from system to see what the problem was.
Sigh, if you ever decide to do a Kindle version best to start with a very plain vanilla old fashioned html.
This is exceedingly useful.
I’m making the file as clean as I can. That’s my philosophy and I’m sticking to it! I wrote my original (fairly complex) website from scratch, converted that to three different WYSIWYG programs without a single hitch. These new programs (especially Word!!!!) pack so much garbage into a file, trying to be everything to everybody…Icky.
Anyway, I’m going to be getting into the conversion stuff after I get the website stuff comfy with Lynn. I’ll probably get back with all of you who’ve done conversions at that time.
Whoops! Hit submit too soon. Right now, I’m just concentrating on getting a simple, clean text file, with curly quotes as something Namo can search and replace. That done, you can convert to just about anything, once you know the right code.
Simple. Oh, yes, please! I love simple! When you have a simple file, no fancy stuff, to start with it is so much easier to work from. Fancy can always be added for particular purposes, but taking it out…
BTW, when do you work on YOUR books, the text part? I have most of CJ’s on paper but somehow missed yours along the way and really, really want to buy them!