Karen,
If I was doing this I'd save from Word as filtered HTML, edit the HTML with Sea Monkey (a version of the Mozilla browser that contains an HTML editor) and use that to make the links for the table of contents and the footnotes. If the author used heading styles in his MS you can automatically generate an HTML table of contents using the Sea Monkey editor. If not, mark up the chapter headings as H2, H3, etc. and then generate the TOC.
Once you have the HTML looking good the next stop is to import it into Sigil and split the file into multiple chapter files. This will generate an EPUB for you. Create a cover image using The GIMP and import it into the EPUB. View the EPUB on a PC using the Nook viewer and fix anything that doesn't look right. Run kindlegen on the EPUB to create a MOBI file. Check it out using the Kindle previewer.
Lather, rinse, repeat. It will take practice to learn to make a book that looks good on both Kindle and Nook. Both platforms have quirks.
Consider charging the guy *something* for your time. Maybe a flat rate rather than an hourly rate. Remember, do somebody a favor and they will always remember you--when they need another favor!
James Simmons
On Sun, Jan 1, 2012 at 1:03 AM, Karen Lofstrom
<klofstrom@gmail.com> wrote:
I helped an ESL author with his book about Theravada Buddhism, and
told him that I would convert his book to Kindle and ePub, and upload
to Amazon and Smashwords, for free. Because I need the experience, and
because I couldn't possibly charge him if I'm spending hours figuring
out how to do it.
So far, I'm stymied. I figured that the appropriate path would be to
convert the Word doc to HTML, and from there go to Kindle and ePub. I
thought I'd start by using Dreamweaver rather than using Save as HTML
in Word. However, my antique copy of Dreamweaver (Dreamweaver 4) is
refusing to open the Word 2003 doc. It seems that I can copy and paste
from the doc into Dreamweaver. Should I do that?
Should I preformat the work in Word, using Outline to produce various
levels of headings?
What should I do about the XE codes that appeared in the document
AFTER I sent the finished manuscript to the author? I think that they
were introduced by the Sri Lankan publisher. They look like this: { XE
"awakened" /i}. Some of them lack the /i. I believe that these are
codes that generate an index, yes? An ebook doesn't need an index,
does it? Just searching should suffice? Yes? No? Should I just
jettison all these codes, or convert them to something in HTML?
What about footnotes? Insert anchors and link, right? Same for TOC, yes?
Dreamweaver output, check with HTMLTidy, then process with Mobipocket
Creator and Sigil?
(Yes, I should have a later Dreamweaver. I maintain my zendo's
website, and I'm producing it in deprecated code. However, I'm too
poor to afford $400 for the latest Dreamweaver.)
I'm not a complete HTML newbie, but my skills are fairly basic. I
would appreciate some help from the folks here. I figured I've earned
it by proofing 78,000 pages at DP. You could send me to the best site
for advice, or send me a private email, or post it here, in case this
would be of interest to other volunteers.
Oh, and Happy New Year!
--
Karen Lofstrom
Zora on DP
_______________________________________________
gutvol-d mailing list
gutvol-d@lists.pglaf.org
http://lists.pglaf.org/mailman/listinfo/gutvol-d