<span class=s3><img src="images/ne-logo100.png" alt="ne-logo100.png" class=s2/></span></img>.s2 { /* NE LOGO */
height: 50%;
width: 50%
}
.s3 { /* NE LOGO */
display: inline-block;
vertical-align: baseline;
width: 1.336em;
margin-left: 0%;
margin-top: 2%;
padding-top: 2%;
margin-right: 0;
margin-bottom: 0%;
text-indent: 0;
max-width: 50%;
width: 100.000%;
}<meta name="output encoding" content="utf-8" />
<meta name="RegionMagnification" content="true" />
<meta name="primary-writing-mode" content="horizontal-lr" />
<meta name="fixed-layout" content="true" />
<meta name="orientation-lock" content="landscape" />
<meta name="original-resolution" content="1152x756" />
<!-- EPUB3 MedaData converted from EXTH -->
<meta property="rendition:layout">pre-paginated</meta>
<meta property="rendition:orientation">portrait</meta><div style="width: 100%; max-height: 100%;">
<img style="max-height: 100%; max-width: 100%; display: block;" src="image.jpg" />
</div>|
We uploaded [...] ePub that you did for us to RedShelf, and in reviewing its functionality, we are seeing problems caused by their proprietary pagination. The page numbers in their browser display system sit off to the right of the page, and push the content out of alignment, and/or introduce large gaps between paragraphs. We brought this up to them, and they replied that the pagination issues are a result of page numbers not being embedded in the ePub. RedShelf displays each chapter as one scrollable page, with the specific page numbers as callouts to the right. Rather than RedShelfs arbitrary placement of their page numbers, we would like to assign our own page numbers that would coincide with the page breaks in the print book. We would like your help in embedding these into the ePub file, if possible. Is there a way to easily address this kind of issue by somehow appending the ePub file, without throwing off compatibility with other ePub readers? Or would we need to develop a separate ePub file specifically for this vendor? Another issue is that a few graphics at the bottom of the unit pages get cut off (clipped) at the bottom of the page. These are QR Codes, specifically, which are important to navigation in the case of [...]. Its as if some kind of space needs to be added at the end of these chapters. There are only a few instances of this and wed love to see if there is something you can do to prevent the QR Codes from being cut off. |