Quote:
Originally Posted by osprofi
Hi
thanks for your quick responses
1) I read in an articles that I have to divide the content files into chunks which equal the page content and then reference in the spine element. This seems hurrible work.
2) I agree that having diff screen sizes the page outlook will be different. This is maybe solved with some css formatting ?
|
Files should be broken into chunks because there are ereaders that cannot handle content files which are too large. However, you should divide the content files into 1 file = 1 chapter, and that will take care of creating pagebreaks to separate each chapter.
css will not solve the different screen sizes issue, but does it really need fixing? ebooks are a different paradigm altogether from paper books. Page numbers are meaningless except as a reference to locations within the paper copy of the book. The rule for ebooks is to just divide up the chapters and let the ereader create the "pages" -- it is how basically all ebooks are made.
By using the
PageList you can create a page number index that Amazon will use to generate page numbers; by using
Page-map, Adobe-based readers/apps will generate page numbers as well.
If you don't need to reference a paper book, you can just ignore these altogether.