- Jutoh could not start the epub checker Pc#
- Jutoh could not start the epub checker windows 8#
- Jutoh could not start the epub checker windows#
I transferred the file to a visible folder on the phone memory and to another on the phone’s SD card. Getting it onto the phone was easy…using OneDrive or a USB cable.
Jutoh could not start the epub checker windows#
Then I tried to find a way to transfer the file to my Windows phone and view it with the Kindle Reader. I transferred the mobi file to the Nexus tablet via USB cable and it opened in the Kindle reader.
Jutoh could not start the epub checker windows 8#
I tried opening it on my Windows 8 phone and got the same read error. I copied the file to One Drive and opened and tried to preview it on my Nexus tablet and got a read error.
Jutoh could not start the epub checker Pc#
I opened the mobi file in Kindle for PC and previewed it. I did a quick preview, closed it and used Jutoh’s export feature to export the ePub to mobi (Kindle). It also found “No Errors.” Next I clicked on Launch and the newly created ePub opened in Adobe Digital Editions 3. I edited the medata and clicked Compile again and it stated “No Errors.” Next I clicked on Check that does an overall ePub check. I had not entered Book Type and Book description. One popped up saying some important metadata was missing. I saved the project and clicked on Compile and hoped for no errors. After renaming and reordering the segments, I previewed each one, browsing for errors. Copy the segment, paste it before or after a chosen segment, then delete the original. After that, I had to edit the alphabetical order of the Table of Content. Although each file was uniquely named, they appeared in Jutoh as numbered chapters…25 of them instead of titled chapters. So that cured my curiosity and I imported the htm files created with Word 2007 into Jutoh 2xx. When I tried to compile them I got more errors. As a matter of curiosity, I imported some old htm files created with Word 2003 and got error warnings. Errors can be corrected in Word and then converted again to htm.Īlthough htm conversion was easy and without any problems, I was worried about possible glitches in the new Jutoh program. Randomly open them in a web browser to preview them. Do the same with each segment until all segments of the project are converted to htm. Click Save and make sure it’s saved to the blank file with the same name (Title Word doc to Title htm file). It’s a pretty straightforward process, open the project, copy a segment, select Save As, select Web Page Filtered under Save As Type, make sure the title of your segment matches the segment…if not change it under Change Title. I’ve also tried Rich Text Format, XML and ODT but wasn’t satisfied with the result. Plain text is great for text only projects and htm for projects with images, although you can use either if you’re proficient with layout programs and formats. Two basic ways of doing this is conversion to plain text or htm. It’s time consuming but is extremely helpful later.ĮBook creator and editing programs don’t like Word formatting, so to avoid compiling errors, Word documents have to be stripped of their formatting. The entire project was broken down into unique segments. Each new Word file is the same size as the project, (ex. Title, Copyright, Dedication, Foreword, Parts One and Two, Chapters, About the Author and other sections. I created a new file for each section of the project, ex. I created a folder titled htm files and opened my project in Word. With these updated and upgraded tools, I created my eBook from scratch…manually. Calibre, an eBook conversion tool, has been updated regularly and Jutoh, an eBook creator and editor, has been upgraded from version 1xx to 2xx. I upgraded my operating system from XP to Windows 8.1.
Since my last eBook project, I’ve also upgraded the program I’m presently writing with, Word 2007 upgraded from 2003. Between now and then, I decided to create an eBook version of the project to test my updated tools. Recently I completed a proofing that was one of many and probably will do another in the near future.
0 kommentar(er)
