[Kindle touch]: How to write documents

[dwig]

Originally Posted by imfede

...t i want what is the best software to create a .pdf?

What is "best" for you is a value judgment only you can make.

You might consider PrimoPDF. It is a virtual printer driver that allows you to "output" PDF files from any app that can print. You simply select PrimoPDF as your printer. To create usable PDFs for 6" ereaders you still need to format the document appropriately, selecting a small "paper" size and zero or minimal margins.

Originally Posted by imfede

since the basic rule of css is that it can do only what html can do but in an easier way, i will try how much css the kindle is able to render... do you suggest a conversion in .mobi using kindlegen or just the .html file? and lets go on with question: how can i create (if is possible) a ToC in html/css? does the kindle support external .css? and last, in case the "html/css way" is not what i want what is the best software to create a .pdf?

EDIT: oh, a big thank to everyone for their response

EDIT2: a pic of almost what i want is like the one provided by jswinden

If you want to display math formulas then you will need to create them using an app like MS Word (time consuming) or using MathML (time consuming and very complicated), then you either need to save the document as a PDF (problematic) or turn the formulas into small images that can be used within a mobi/KF8 eBook (time consuming).

Books with math formulas are a major PITA, time consuming to create, problematic for displaying on small 6" screens. But they are possible to create.

Probably the easiest method is to use MS Word to create the book and then export it to PDF. However, PDFs on an eInk 6" reader suck. They are a pain to navigate, they do not reflow text, etc.

It is a lot more work to create image files of your math formulas then display them in a mobi/KF8/ePub book, but this method is much more flexible and is reflowable. The text in the images cannot reflow or be resized but the text in the rest of the book can be.

As for as HTML goes for creating a mobi/KF8/ePub book, there are many limits to using only HTML and then converting it via Kindle Previewer.

• Must be a single HTML file with internal CSS
• No TOC
• No cover

This might work well for a simple, small document, but not for complex documents requiring a TOC.

A better method for using HTML to create an eBook is to use Sigil. With Sigil you create a ePub using HTML files:

• Can use multiple HTML files (recommend one file per section/chapter)
• Can use separate CSS file (but CSS is not necessary)
• Can easily add cover
• Can easily design structure of book and create TOC
• Has WYSIWYG editor

I recommend using Sigil to create an ePub version of your book. Calibre is okay for converting an existing eBook into another format, but it is not designed as a book creation app. After you create your ePub in Sigil, either use calibre or Kindle Previewer to create the mobi/KF8 book. Kindle Previewer will let you test the book on various simulated Kindle devices.

[imfede]

Originally Posted by thomass

Alternatively you can use this word extension to save your docs in pdf format with appropriate settings for Kindle.

Unfortunately is for win only i forgot to say i own a iMac, but thanks

[imfede]

jswinden, very very thank you for your clear and comprehensive answer. i'm downloading Sigil right now, i will let you know how it goes


EDIT: it looks great! little more question: is it possible to use, in Sigil, html with some css rather than strict xhtml + css?

Originally Posted by imfede

jswinden, very very thank you for your clear and comprehensive answer. i'm downloading Sigil right now, i will let you know how it goes


EDIT: it looks great! little more question: is it possible to use, in Sigil, html with some css rather than strict xhtml + css?

I usually create my HTML files in Dreamweaver. I've been using it for years so it is my "comfort" app when it comes to creating multiple HTML files that are linked to one another for a larger document (or a web site). I like to use HTML 5, not XHTML. I've noticed that Sigil has always converted my HTML 5 files into XHTML whenever I import them. I haven't found a way around that, but to be honest I haven't looked very much either!

If I'm going to create a large document/book that will be published, this is my actual workflow:

• Create the HTML 5 and CSS files in Dreamweaver, including a stand-alone TOC.
• Use Dreamweaver to organize the book.
• Use Dreamweaver to incorporate any image files.
• Start Sigil and import all my HTML, CSS, images, etc.
• Use Sigil to designate a cover.
• Use Sigil to edit the metadata.
• Use Sigil to create a TOC, internal file structure.
• Create the ePub in Sigil.
• Copy the ePub file to a working folder.
• Rename myBookName.epub to myBookName.zip then unzip the file.
• In the unzipped folder that was the ePub, I replace all the XHTML files created in Sigil with the HTML 5 files I originally created in Dreamweaver. This gets rid of the stuff Sigil added or changed as for as ML goes.
• Edit the toc.ncx and ensure all the file name references are correct and add or correct the references for the cover and TOC in accordance to Amazon's guidelines for creating KF8.
• Use Kindle Previewer to compile the files into a KF8/mobi book.

I know this looks rather convoluted and complex, but it really isn't. Dreamweaver is the main development tool. Sigil lets me take my book files and generate a clean ePub. Sigil does a good job with the toc.ncx file, and trust me you don't want to have to create one of those by hand! Since Amazon's specs for clean KF8 are a little different from those of an ePub, it is back to Dreamweaver to clean up the files before finally using Kindle Previewer to compile the files into a KF8/mobi. As a result I seem to consistently create trouble free books.

If I'm merely creating a document solely for my own use, I won't go to this much trouble.

Forgot to mention this important fact about my workflow:

I do NOT convert the Sigil ePub to a mobi via Kindle Previewer. You can certainly do that of course. Rather I unzip the ePub and basically modify the content.opf file a little bit. When I compile the book I point Kindle Previewer to the content.opf file, not to the ePub file. So basically Dreamweaver is the heavy lifter, the tool I use the create and edit the text and initially lay out the book structure, then finalize the book. Sigil is merely used to add a cover, edit the metadata, add a TOC, and create the content.opf and toc.ncx files which are quite frankly a PITA to create manually. Everything I use Sigil for I could do manually, but Sigil saves a lot of time and is way more accurate than my manually created files would be.

You can of course totally create your book in Sigil then have calibre or Kindle Previewer convert it to mobi. That would be much quicker and easier. For personal documents this makes a lot of sense. But for published books I desire more control.

EDIT:

• Think of the content.opf file is being the blueprints from which to build your book. It lists all the files, lists where they are located, defines what they do, and how they should be used to create the mobi book. It also contains metadata for the book.
• The toc.ncx file defines the TOC and structure of the book.

[NACarter]

Originally Posted by thomass

Alternatively you can use this word extension to save your docs in pdf format with appropriate settings for Kindle.

Has anyone got this Word add-in to work with Word 2007? I can't get it to appear. The add-ins settings always shows the COM KindleSender add-in unchecked.

Thanks for any help.

Nick

Originally Posted by NACarter

Has anyone got this Word add-in to work with Word 2007? I can't get it to appear. The add-ins settings always shows the COM KindleSender add-in unchecked.

Thanks for any help.

Nick

It really isn't necessary. What I did way back when was simply create a re-usable Word 2007 template for creating PDFs designed for 6" eInk readers.

Set up the template by setting:

• Paper Size = 3.4" x 4.7" (play around until this looks right)
• Margins = 0.1" (or whatever looks best to you)
• Set up your fonts and font sizes for each style you use

That is pretty much it. It will take a little while to get the template tweaked for your tastes, but afterwards it is very quick and easy to apply it to a Word document. Then create your document in Word and save it. Then save the Word document as a PDF.

BTW, I cannot remember the paper size I used, but just play around with the dimensions until you get as little waste as possible.

EDIT: I think using a template the allows you to view the text in approximately the same size and configuration as the finished PDF will look on a Kindle is much better than simply converting a larger format document. It is sure easier when editing the document to get each page to display the way you want.

[NACarter]

Thanks Jack. That's a great help!

Nick

[imfede]

thank yo all very much, in particular jswinden for his exhaustive answers
this is how i will proceed: taking notes with a kind of wordpad with just basic basic html, not to get distracted form studying
when i finished i will use dreamweaver (which is one of my fav editor) to set up all the layout, images and so on; import that in Sigil to create a ToC and to convert in an .epub and then convert it into a .mobi using kindlegen

But i don't really understand one passage: how do you "manually convert" the .epub in a .mobi? i don't get the part "When I compile the book I point Kindle Previewer to the toc.ncx file, not to the ePub file."

thx in advance

Originally Posted by imfede

thank yo all very much, in particular jswinden for his exhaustive answers
this is how i will proceed: taking notes with a kind of wordpad with just basic basic html, not to get distracted form studying
when i finished i will use dreamweaver (which is one of my fav editor) to set up all the layout, images and so on; import that in Sigil to create a ToC and to convert in an .epub and then convert it into a .mobi using kindlegen

But i don't really understand one passage: how do you "manually convert" the .epub in a .mobi? i don't get the part "When I compile the book I point Kindle Previewer to the toc.ncx file, not to the ePub file."

thx in advance

Actually that was a booboo on my part. I wrote toc.ncx file but should have written content.opf file. I'll edit the post to correct it. When you start Kindle Previewer it prompts you to open a file. Kindle Previewer can open mobi, ePub, HTML, or OPF files. What I do is have it open the content.opf file which was created in Sigil as part of the ePub. The content.opf file basically defines the book by pointing to each file that is used in the book and defining how those files are used. Think of it as the blueprints to how you want your book built. When you have Kindle Previewer open the content.opf file it reads the file and understands how you want the book built and then compiles the files into the mobi/KF8 book.

Here is a sample content.opf file so you can understand what it is and what it does:

<?xml version="1.0" encoding="UTF-8"?>
<package xmlns="http://www.idpf.org/2007/opf" unique-identifier="BookID" version="2.0">
    <metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:opf="http://www.idpf.org/2007/opf">
        <dc:title>W5JCK Amateur Radio Extra Class Exam Q&A Review 2012-2016</dc:title>
        <dc:creator opf:role="aut">Ceburn Jack Swinden</dc:creator>
        <dc:language>en</dc:language>
        <dc:identifier id="BookID" opf:scheme="UUID">urn:uuid:f6605485-aafd-45c2-a8dd-2e5d7667e7b8</dc:identifier>
		<meta name="cover" content="my-cover-image" />
    </metadata>
    <manifest>
        <item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>
        <item id="extra-exam.css" href="Styles/extra-exam.css" media-type="text/css"/>
        <item id="Section-E0.html" href="Text/Section-E0.html" media-type="application/xhtml+xml"/>
        <item id="Section-E1.html" href="Text/Section-E1.html" media-type="application/xhtml+xml"/>
        <item id="Section-E2.html" href="Text/Section-E2.html" media-type="application/xhtml+xml"/>
        <item id="Section-E3.html" href="Text/Section-E3.html" media-type="application/xhtml+xml"/>
        <item id="Section-E4.html" href="Text/Section-E4.html" media-type="application/xhtml+xml"/>
        <item id="Section-E5.html" href="Text/Section-E5.html" media-type="application/xhtml+xml"/>
        <item id="Section-E6.html" href="Text/Section-E6.html" media-type="application/xhtml+xml"/>
        <item id="Section-E7.html" href="Text/Section-E7.html" media-type="application/xhtml+xml"/>
        <item id="Section-E8.html" href="Text/Section-E8.html" media-type="application/xhtml+xml"/>
        <item id="Section-E9.html" href="Text/Section-E9.html" media-type="application/xhtml+xml"/>
        <item id="front-matter.html" href="Text/front-matter.html" media-type="application/xhtml+xml"/>
        <item id="linked-toc.html" href="Text/linked-toc.html" media-type="application/xhtml+xml"/>
		<item href="Text/images/cover.jpg" id="my-cover-image" media-type="image/jpeg" />
    </manifest>
    <spine toc="ncx">
        <itemref idref="front-matter.html"/>
        <itemref idref="linked-toc.html"/>
        <itemref idref="Section-E1.html"/>
        <itemref idref="Section-E2.html"/>
        <itemref idref="Section-E3.html"/>
        <itemref idref="Section-E4.html"/>
        <itemref idref="Section-E5.html"/>
        <itemref idref="Section-E6.html"/>
        <itemref idref="Section-E7.html"/>
        <itemref idref="Section-E8.html"/>
        <itemref idref="Section-E9.html"/>
        <itemref idref="Section-E0.html"/>
    </spine>
    <guide>
        <reference type="text" title="Beginning" href="Text/front-matter.html"></reference>
        <reference type="toc" title="Table Of Contents" href="Text/linked-toc.html"/>
    </guide>
</package>

So I use Sigil to create the content.opf file and the toc.ncx file. Both can be created manually, but they are a PITA to create manually. So use Sigil to create them. They are created when Sigil creates the ePub and you can see them by expanding (unzipping) the epub.

If you open an ePub or HTML file in Kindle Previewer it will convert that file to a mobi file. If you open a content.opf file Kindle Previewer will create your book using the instructions contained therein. Like I said, or meant to say, in the previous post, a mobi content.opf is slightly different than an ePub content.opf. Either will work, but if you make a couple tweaks to the ePub content.opf you will have better luck getting the cover to display correctly and the TOC to work correctly and few other things can be tweaked as well.