Answers.Body: <p>The first thing is: which reading system are you targeting? Edge is just a test environment, right? Or is this how people using Windows devices are reading ebooks these days? I always regard testing in browsers to be at best a preliminary approximation.</p>
  
  <p>I regard Adobe DE and Readium on Chrome as my 2 most reliable testing platform on a Windows machine. Then I try Google Play Books, iBooks  and then test mobis on various kindle platforms. </p>
  
  <p>I suspect that Edge uses a different rendering engine than the other browsers and might have different default settings for formatting. That might explain discrepancies. But the principles of responsive design dictate that you're not going to have pixel precision. 
  A quick look at your screenshot indicates that what renders in Edge looks pretty close to the other rendering. </p>
  
  <p>You would need to give the CSS code and what features are different/missing for me to give any better information. It looks like your project is not commercial and maybe that's why you worry about Edge rendering because you think people might open it up in a browser.  But I test a lot of ebooks, and I don't think I've ever tested tested on Edge.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-03T17:18:55.950Z
Answers.Text: Thanks for your input. Edge was easy to use as a test because it was already installed and when I double-clicked on the epub, it went straight there.
  
  I'll try Readium and see what that looks like.
  
  I'll add some html and css to my original post. It was too long to put here.
Answers.UserDisplayName: Matt
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-13T18:14:46.193Z
Answers.LastActivityDate: 2019-01-13T18:14:46.193Z
Answers.UserDisplayName: idiotprogrammer
Body: <p>I created a MOBI file using Kindlegen. I fed the MOBI file to Calibre and converted it to an EPUB.</p>
  
  <p>If I view the HTML files I used to create the MOBI file, they look great. All formatting is picked up from my separately defined .css file.</p>
  
  <p>I took the EPUB file and ran it through the EPUB checker/validator. I corrected all errors (except one saying my html files need to be xhtml files, which is only a warning anyway).</p>
  
  <p>I can view the resulting EPUB file in Abobe Digital Editions 4.5 and it looks great.</p>
  
  <p>The problem I'm having is when I view it in Edge, it seems to be missing some of the formatting (headers aren't centered anymore, some specific text I have labeled as a quote and deliberately decided to not Justify the text becomes Justified like the main body text).</p>
  
  <p>Since the EPUB passed the validator, I published it.</p>
  
  <p>Does anyone have an idea why this is happening? Why would the HTML files work great and Abode can read the EPUB and interpret the CSS file perfectly, but Edge can't?</p>
  
  <p>Im attaching a file with 3 different views so you can see how Edge loses the formatting. <a href="http://christianconcepts.com/public/epubformattingincorrect.jpg" rel="nofollow noreferrer">View Edge DE and BN</a></p>
  
  <pre><code>The quote HTML:
  &lt;div class=MsoIntenseQuote&gt;
  &lt;p class=MsoIntenseQuoteCxSpFirst&gt;
  For we are his
  workmanship, created in Christ Jesus for good works, which God prepared
  beforehand, that we should walk in them.&lt;/p&gt;
  &lt;p class=MsoIntenseQuoteCxSpLast&gt;—Ephesians 2:10&lt;/p&gt;
  &lt;/div&gt;
  
  The quote CSS:
  p.MsoIntenseQuote, li.MsoIntenseQuote, div.MsoIntenseQuote
  {
      margin-top:1em;
      margin-right:4em;
      margin-bottom:1em;
      margin-left:4em;
      text-align:center;
      text-indent:0em;
      border:none;
      padding:0em;
      font-style:italic;
  }
  p.MsoIntenseQuoteCxSpFirst, li.MsoIntenseQuoteCxSpFirst, div.MsoIntenseQuoteCxSpFirst
  {
      margin-top:1em;
      margin-right:0em;
      margin-bottom:0em;
      margin-left:0em;
      text-align:center;
      text-indent:0em;
      border-top:.1em solid;
      padding:.25em;
      font-style:italic;
  }
  p.MsoIntenseQuoteCxSpLast, li.MsoIntenseQuoteCxSpLast, div.MsoIntenseQuoteCxSpLast
  {
      margin-top:0em;
      margin-right:0em;
      margin-bottom:1em;
      margin-left:0em;
      text-align:center;
      text-indent:0em;
      border-bottom:.1em solid;
      padding:0em;
      font-style:normal;
  }
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-01-13T04:22:59.880Z
Comments.Text: what formatting issue are you encountering? I cannot tell on this screenshot.  To compare, you need to have the display size and defaults be the same across your test environments.
Comments.UserDisplayName: idiotprogrammer
Tags: <epub><css><formatting>
Title: EPUB 3 CSS stylesheet ignored in some cases?
UserDisplayName: Matt
ThreadText: # EPUB 3 CSS stylesheet ignored in some cases?
  
  (Asked by: username_0 on 2019-01-11)
  
  I created a MOBI file using Kindlegen. I fed the MOBI file to Calibre and converted it to an EPUB.
  If I view the HTML files I used to create the MOBI file, they look great. All formatting is picked up from my separately defined .css file.
  I took the EPUB file and ran it through the EPUB checker/validator. I corrected all errors (except one saying my html files need to be xhtml files, which is only a warning anyway).
  I can view the resulting EPUB file in Abobe Digital Editions 4.5 and it looks great.
  The problem I'm having is when I view it in Edge, it seems to be missing some of the formatting (headers aren't centered anymore, some specific text I have labeled as a quote and deliberately decided to not Justify the text becomes Justified like the main body text).
  Since the EPUB passed the validator, I published it.
  Does anyone have an idea why this is happening? Why would the HTML files work great and Abode can read the EPUB and interpret the CSS file perfectly, but Edge can't?
  Im attaching a file with 3 different views so you can see how Edge loses the formatting. View Edge DE and BN
  The quote HTML:
  
  
  For we are his
  workmanship, created in Christ Jesus for good works, which God prepared
  beforehand, that we should walk in them.
  —Ephesians 2:10
  
  
  The quote CSS:
  p.MsoIntenseQuote, li.MsoIntenseQuote, div.MsoIntenseQuote
  {
      margin-top:1em;
      margin-right:4em;
      margin-bottom:1em;
      margin-left:4em;
      text-align:center;
      text-indent:0em;
      border:none;
      padding:0em;
      font-style:italic;
  }
  p.MsoIntenseQuoteCxSpFirst, li.MsoIntenseQuoteCxSpFirst, div.MsoIntenseQuoteCxSpFirst
  {
      margin-top:1em;
      margin-right:0em;
      margin-bottom:0em;
      margin-left:0em;
      text-align:center;
      text-indent:0em;
      border-top:.1em solid;
      padding:.25em;
      font-style:italic;
  }
  p.MsoIntenseQuoteCxSpLast, li.MsoIntenseQuoteCxSpLast, div.MsoIntenseQuoteCxSpLast
  {
      margin-top:0em;
      margin-right:0em;
      margin-bottom:1em;
      margin-left:0em;
      text-align:center;
      text-indent:0em;
      border-bottom:.1em solid;
      padding:0em;
      font-style:normal;
  }
  
  **Tags:** epub, css, formatting
  
  > **Comments:**
  > **username_1**: what formatting issue are you encountering? I cannot tell on this screenshot.  To compare, you need to have the display size and defaults be the same across your test environments.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-01-13. Score: 0
  
  The first thing is: which reading system are you targeting? Edge is just a test environment, right? Or is this how people using Windows devices are reading ebooks these days? I always regard testing in browsers to be at best a preliminary approximation.
  
  I regard Adobe DE and Readium on Chrome as my 2 most reliable testing platform on a Windows machine. Then I try Google Play Books, iBooks and then test mobis on various kindle platforms.
  
  I suspect that Edge uses a different rendering engine than the other browsers and might have different default settings for formatting. That might explain discrepancies. But the principles of responsive design dictate that you're not going to have pixel precision.
  A quick look at your screenshot indicates that what renders in Edge looks pretty close to the other rendering.
  
  You would need to give the CSS code and what features are different/missing for me to give any better information. It looks like your project is not commercial and maybe that's why you worry about Edge rendering because you think people might open it up in a browser. But I test a lot of ebooks, and I don't think I've ever tested tested on Edge.
  
  > **Comments:**
  > **username_0**: Thanks for your input. Edge was easy to use as a test because it was already installed and when I double-clicked on the epub, it went straight there.  I'll try Readium and see what that looks like.  I'll add some html and css to my original post. It was too long to put here.  
  
  ---
  
  