Answers.Body: <p>KindleGen will work equally well on epub 3.0 and epub 2.0.  Just make sure that you're being consistent throughout with the structure&mdash;you can't use an epub 3.0 toc.xhtml for navigation in an epub 2.0 document, for example. As long as you have a valid epub document of one flavor or another (validated with the current version of <a href="https://github.com/IDPF/epubcheck" rel="nofollow">epubcheck</a>), your file should be fine.</p>
  
  <p>A special note for fixed layout files: Early epub fixed layout was an iBooks-specific format. Much of that format was adopted by the IDPF into the epub format, but it's not completely integrated. If you have a fixed layout epub that you want to run through KindleGen, make sure that it's epub 3.0 fixed layout, or you may have errors crop up.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-25T10:06:42.037Z
Answers.LastActivityDate: 2015-02-25T10:06:42.037Z
Answers.UserDisplayName: Tom
Answers.Body: <p>Well kindlegen basically just strips all code that isn't on Amazon documentation from HTML and CSS. So if your ePub is not too complicated the results should be satisfactory. This can change when you will try convert fixed layout where hierarchy of DOM isn't logic.</p>
  
  <p>To give you straight answer: It not make any difference unless your DOM is in logic order.</p>
  
  <p>DOM (Document Object Model) define structure of an document. Ideally structure (or hierarchy ) should be logic in terms of rendering. For example:</p>
  
  <pre><code>&lt;div&gt;
      &lt;p&gt;Lorem ipsum&lt;/p&gt;
  &lt;/div&gt;
  &lt;div&gt;
      &lt;p&gt;Lorem ipsum 2&lt;/p&gt;
  &lt;/div&gt;
  </code></pre>
  
  <p>here you have two divs with two paragraphs one after the other. If you will not manipulate with them, they will also render one after the other. But you could use CSS or JS to manipulate them and render <code>&lt;p&gt;Lorem ipsum 2&lt;/p&gt;</code> before <code>&lt;p&gt;Lorem ipsum&lt;/p&gt;</code> without change your actual HTML. This situation happens very often when you designing fixed-layout ePub which are parto of ePub3 spec. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-25T10:07:50.760Z
Answers.Text: It's not clear what you mean by "hierarchy of DOM isn't logic" and "unless your DOM is in logic order". Could you clarify or explain?
Answers.UserDisplayName: Tom
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-25T12:28:33.047Z
Answers.Text: look on my edit please. If you have any further questions just ask.
Answers.UserDisplayName: Glorifind
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-24T09:43:42.780Z
Answers.LastActivityDate: 2015-02-25T12:27:55.783Z
Answers.LastEditDate: 2015-02-25T12:27:55.783Z
Answers.UserDisplayName: Glorifind
Body: <p>After creating a valid EPUB 2 or EPUB 3 file, I am often able to run the file through Amazon's kindlegen convertor, and assuming neither file was overly complicated in terms of page layout, have the resulting mobi file look pretty decent in the kindle viewer.</p>
  
  <p>That being said, does kindlegen do better with converting EPUB 2 specifications or EPUB 3 specifications to its proprietary format?</p>
  
Tags: <mobi><kf8>
Title: Kindlegen Convert EPUB 2 and 3 Equally?
UserDisplayName: maxwell
ThreadText: # Kindlegen Convert EPUB 2 and 3 Equally?
  
  (Asked by: username_0 on 2015-02-24)
  
  After creating a valid EPUB 2 or EPUB 3 file, I am often able to run the file through Amazon's kindlegen convertor, and assuming neither file was overly complicated in terms of page layout, have the resulting mobi file look pretty decent in the kindle viewer.
  
  That being said, does kindlegen do better with converting EPUB 2 specifications or EPUB 3 specifications to its proprietary format?
  
  **Tags:** mobi, kf8
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-02-25. Score: 1 | Accepted answer
  
  KindleGen will work equally well on epub 3.0 and epub 2.0. Just make sure that you're being consistent throughout with the structure—you can't use an epub 3.0 toc.xhtml for navigation in an epub 2.0 document, for example. As long as you have a valid epub document of one flavor or another (validated with the current version of [epubcheck](https://github.com/IDPF/epubcheck)), your file should be fine.
  
  A special note for fixed layout files: Early epub fixed layout was an iBooks-specific format. Much of that format was adopted by the IDPF into the epub format, but it's not completely integrated. If you have a fixed layout epub that you want to run through KindleGen, make sure that it's epub 3.0 fixed layout, or you may have errors crop up.
  
  
  ---
  
  ### Answer by username_2 on 2015-02-24. Score: 1
  
  Well kindlegen basically just strips all code that isn't on Amazon documentation from HTML and CSS. So if your ePub is not too complicated the results should be satisfactory. This can change when you will try convert fixed layout where hierarchy of DOM isn't logic.
  
  To give you straight answer: It not make any difference unless your DOM is in logic order.
  
  DOM (Document Object Model) define structure of an document. Ideally structure (or hierarchy ) should be logic in terms of rendering. For example:
  
  ```
  <div>
      <p>Lorem ipsum</p>
  </div>
  <div>
      <p>Lorem ipsum 2</p>
  </div>
  
  ```
  
  here you have two divs with two paragraphs one after the other. If you will not manipulate with them, they will also render one after the other. But you could use CSS or JS to manipulate them and render `<p>Lorem ipsum 2</p>` before `<p>Lorem ipsum</p>` without change your actual HTML. This situation happens very often when you designing fixed-layout ePub which are parto of ePub3 spec.
  
  > **Comments:**
  > **username_1**: It's not clear what you mean by "hierarchy of DOM isn't logic" and "unless your DOM is in logic order". Could you clarify or explain?  
  > **username_2**: look on my edit please. If you have any further questions just ask.  
  
  ---
  
  