I finally found a second work-around in googledocs for automatic first line indentation in each paragraph. It’s a blue rectangle up in the margins that they recently added. This solves my earlier problem.
However, I’m still having difficulty figuring out margins when uploading to the kindle. When I load the html format to the kindle the margins are way too narrow. However, when I send to Word first and then save as an html file, the margins are fine. Again, this works but the whole idea is to avoid using word and instead only use tools that are free. I’m open to ideas on why the margins are uploading as way too narrow.
On the plus side, Ive finished drafting chapter 4. I’m planning on uploading a preview of sample of some chapters during the summer on this blog and my website. Continue following to see a sample soon!
So the kindle wants a special indentation to be set up for the first line at 0.5.” GoogleDocs doesn’t have a feature to perform this function. After experimenting with different strategies to resolve this problem, it appears that there simply isn’t a workaround that works 100% of the time.
I experimented on a Word document to see how hard it would be to change the indentation settings after drafting on GoogleDocs. To my surprise it is actually a very simple adjustment that I can do later on.
I have decided that I will continue using GoogleDocs to draft, and during the editing process I will convert to word to add the indentation settings. While this admits a small degree of defeat in terms of staying away from Word for this process, it still allows me to use GoogleDocs as the primary drafting tool.
After doing some research on publishing on the Kindle, I found out that the Kindle has some strange quarks in terms of formatting. These quarks are supposedly easy to avoid as long as the author sets up the proper formatting ahead of time.
For example, one quark is that the Kindle does not want an author to hit tab in order to indent each paragraph. Instead, the formatting wants a special setting to be turned on inside the word processor.
Amazon has a free book in their store titled Building Your Book for Kindle. I plan on reading it today and trying to make changes based off of its suggestions.
Of course, the biggest “hick-up” in this project is that I won’t be using Microsoft Word; I will have to find work-arounds for functions in Microsoft Word in how they translate to GoogleDocs.
Unfortunately, I have already started writing. This means I’ll have to go back and tweak what I have already typed. Fortunately, I’m not too far along, so maybe this isn’t so bad.
After way too much time spent procrastinating, I have finally decided to get serious about publishing my memoir.
However, in addition to blogging about the writing process I wanted to share my experiences in the eventual goal of publishing my work to the Kindle platform via Amazon.
To make things really interesting, I have decided to attempt this entire project by only using a Chromebook and GoogleDrive features. That’s right, I will be attempting to create a book that is correctly formatted without using Microsoft Word.
I want this project to demonstrate the shifting state of publishing that I feel is becoming more and more democratic due to free and easily accessible tools. Will I be able to pull it off? What problems will I encounter? This blog will trace my progress and provide a guide to others in the future who may attempt a similar project.