I tried Kotobee Author and found that importing docx makes one large chapter.
How to split my book to chapters by style or pattern? (OK, I can copy and paste text chapter by chapter but I'd like to automate this process.)
Better doing it automatically during import.
And how to merge two chapters? (Again: copy-paste doesn't play!)
In brief using chapters is rather silly. You ought to work on it!
Why don't you convert your Word document into a PDF document and import it? This way it will split each page into a page/chapter by itself.
Let me know if that works for you.
Well, I tried that too. But its not too helpful to import a roman page to page.
And the main problem is to maintain (merge, split) chapters AFTER import!
If you want the best practice in creating a great ebook experience, then create the content as reflowable chapters manually. Sorry this means that you will need to copy bits and pieces from your Word document, and create separate chapters in Kotobee Author for this. It may sound like a headache, but trust me it will pay off at the end.
I trust you, but I'm making ebooks years ago with Jutoh. It split Word (and odt, html, txt) documents by pattern or by style at the process of import. After import you can reorganize chapters, merge or split them. You haven't to suck with separate pages.
It's a lot easier, trust me! :)
In Kotobee Author, the chapter can be as long as you want, since it's vertically scrollable. We haven't done much work with Word import, but only PDF import.
I apologize if how it is currently isn't very convenient for you.
Well in Jutoh (but in Word too) the chapter can be arbitrary long as long as fit in the 300k epub standard.
The problem is not Word import solely. If I could handle the chapters later manually more easy I didn't care import any more.
But the page-by-page pdf import causes breaks in the middle of sentences, what is unacceptable.
It doesn't make ebook creating easier but troublesome instead.
I totally agree. The reason for this is that PDF is a fixed-layout format. Words and sentences don't wrap. They are fixed in position in the page.
But I think it doesn't too much sense to convert a fixed layout pdf to fixed layout epub, does it? :)
More many times wants someone to convert to reflowable epub.
Yes definitely, it doesn't make sense, unless you have a project that is due the very next day. It's something quick and dirty.
Sorry, this methodology is terrible and may make this unusable for a small publisher. epub is fundamentally HTML. Docx (and RTF) are pretty easy to convert to HTML. Headings are then easy to convert to chapters. Most epub conversion tools do this automatically. At a minimum you should have an import of html option. Then I can use word's built in save as filtered HTML option, which creates a very clean HTML file. Headers should be automatically turned into chapters.
This program, unfortunately forces the user to essentially compose in the program. Even Adobe InDesign (and Adobe is notorious for funky interfaces) allows a better methodology. Free programs such as Calibre do a quite nice job of this too and if one want to tweak it, you open Sigil and tweak it.
Going FROM Word to PDF to this is a terrible process.
I love that this has some ePub3 support. Really the biggest issue with this program is 99% of authors/writers are going to write in Word or a similar program. You need to make the importing process nice and flexible! Cheers
Thanks Stan for the feedback. I understand what you're saying.
If it's easy to convert Word to HTML, then it's easy to just paste in the HTML into the chapter's source mode. The source mode displays the HTML behind the chapter, which you can edit or replace entirely. Actually, through the file manager you have access to each single chapter (html) file. The great thing about using HTML rather than PDF, is that you will maintain the reflowable layout of the chapter.
But you're right, we should include an easier option to have all this done automatically, by importing a Word file.
No, you are missing the point.
many/most editor/publishers that would on layout will work on the entire book. Word has a ONE CLICK export to HTML, filtered. It creates ONE LARGE HTML with heading tags. Pasting this large, SINGLE FILE HTML into you source mode does nothing for the user. Having to cut and past 36 times for a novel is tedious and error prone. Programs are made to automate tedious, error prone things.
Of course HTML maintains the reflow...that is the point of HTML which is ALL THAT AN EPUB IS (fundamentally).
Your program makes adding some epub 3 elements a bit easier, which I like, but to use this I would do the following: Save word to Filtered HTML. Use Calibre to convert to an EPUB AUTOMATICALLY creating chapters and 95% of what you want. Open in Sigil and check some things like indenting and meta data. If you want to add epub3, either use Sigil and edit elements by hand, or use your program to add some epub3 elements. So, for my process this might help, but only occasionally as I still need to use the other process for a FAST, EFFICIENT epub (or mobi, including I might add, the new Amazon format which is really a modified epub3).
This was really helpful. That's going on our to-do list as high priority.
But may I ask, what distinguishes the different chapters in the 'one-large' html file, once it's exported from Word? How does Calibre (for example) know the start and end of each chapter? I mean, the entire Word file can be intended to be a single chapter, or multiple chapters. Unless the user is using page-breaks, or inserting some special placeholder text, that is to be detected by Calibre. Would love to hear from you about this.
Can you remind me with the extension of the new Amazon format?
Thanks again for sharing this. Love to hear from actual users!
usually the h1 tag means the chapter header. But it is configurable in Calibre and th Jutoh too.
Moreover in Jutoh you can define a text pattern (such as 'chapter') or any CSS style to use as split marker.