View Single Post
Old 04-27-2012, 06:27 AM   #18
VydorScope
Wizard
VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.VydorScope ought to be getting tired of karma fortunes by now.
 
VydorScope's Avatar
 
Posts: 3,293
Karma: 34338466
Join Date: Jun 2011
Device: Kindle Fire HD 7
Quote:
Originally Posted by gmw View Post
I am not certain I follow the logic behind Smashwords - but note that I am looking at this as a total outsider (so far). Let me see if I have this straight...

The writer writes their novel (or whatever) using Word (or whatever) and is careful to get everything exactly as the writer wants it to be - perhaps exporting out to epub (or whatever) every now and then to see if it is all working.

Then, when everything is done and is looking just right, the writer is supposed to strip out all that careful formatting (smart-quotes, em-dash, bullet points, etc. etc.) and upload this essentially plain text file up to Smashwords.

Smashwords will then, if the few examples I've found are anything to go by, execute an automatic process that puts some of your original formatting (smart-quotes etc. etc.) back in to the final document.

The main difference between the writer's original epub and the smashwords' epub is that the original was carefully crafted for a specific result, while the second is automatically generated based on some fixed set of, one-size fits everyone, rules.

I have a little difficulty seeing that a writer supplied epub (which is probably produced using a software automation process rather than hand-coded, and so the format is likely to be highly consistent), could possibly produce a worse result than the tortuous process already in place. If they can already parse Word documents to reject all those things they don't like, it doesn't seem like it should be beyond them to reject epubs that don't fit within some reasonable criteria.

No, not exactly. For most books the process is...

1) Type up your book in MS word sticking to the older .DOC file type not the new DOCX one. Use italics, bold, page breaks, tabs, etc. (except bullets apparently), all are fine.

2) Take your .DOC Word Doc up load it to Smash

3) Wait like 10 mins for it to be automatically converted to every major ebook format for you.


That is it. Most authors I have talked with do just that and their books look fine on my Nook, or in my Kindle apps.

As with anything, Smash build a process that fits the majority of the cases, and edge cases suffer. If you follow their style guide not only will you get good results with them, but that same style guide works to get you good results with the automatic conversion at Amazon, and elsewhere.
VydorScope is offline   Reply With Quote
 
http://www.mobileread.com/forums/showpost.php?p=2059416&postcount=18
www.mobileread.com
crawl=CC-MAIN-2014-15
12926
application/http; msgtype=response
sha1:DQOWJXJ6PAI4KS44KYQDDVTOA7EILAIK
<urn:uuid:225a9688-acca-4ceb-a79c-581f214aceb5>
2014-04-20T18:42:45Z
67.205.70.12
sha1:JKICOG5VYFUXL4A3TWJKOT3GSQ2RU7UR
<urn:uuid:14c67e73-69d4-4d54-b2ac-4f853809a210>
http://www.mobileread.com/forums/showpost.php?p=2059416&postcount=18
length
response
<urn:uuid:2b424318-2a23-47d5-ac23-c322caa8b51e>
robots: classic
hostname: ip-10-147-4-33.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-15
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for April 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf