“ Note that the Dynamic Layouts "Layout 2" has a central text column width of 36em. At "normal" font sizes, this is 576px, so any image large than this will likely not render correctly in Layout 2 on the main website.
Many ebook readers (and the mobile Wikisource site) provide extra logic to ensure images fit the screen, so you may find this is not an issue. The EPUB and PDF export tools apply this logic too. However, it is possible apply your own CSS that nullifies this protection, so beware when setting image sizes. ”

“ Page 2 - this will be a new page in an e-reader
Testing You can test e-book formatting in 2 ways:
Viewing the online page in a browser's "mobile view". Downloading an EPUB or MOBI format and viewing on an e-reader or e-reader app. Only this method allows to you to check for issues like missed sections. You can also use the W3C EPUB validator tools to check technical correctness of EPUB files.
Online viewing You can use the "Mobile view" gadget under "Development" in your gadgets preferences, which shows the page in both the desktop and mobile mode, as well as simulating a narrow screen. ”

“ For now, most dot leader template use ws-noexport to suppress the dots on export and degrade to a simple table. This only works for templates like {{TOC row 1-dot-1}}. Templates like {{Dtpl}} and {{TOCstyle}} use very complex formatting that usually doesn't render properly on e-readers and are still broken. {{TOCstyle}} in general doesn't work well, as it embeds a whole table in each

element. Generally for 2-cell rows it works, for 3-or-more-cell, it's patchy. Sidenotes rarely work in ebooks. ”

“ E-reader devices generally have much smaller screens E-reader devices, apps or the ebook export tools may not support all formatting features that work in browsers Some content visible on Wikisource is excluded from the exported formats Formatting for small screens Smartphones often have an effective pixel width [4] of around 350px. For a "normal" font size, this is about 23em. Because e-readers can adjust the font size, you should be cautious when making assumptions about screen width in relative terms such as "em". ”

“ Table-based columns templates like {{multicol}} cannot do this, and these are very likely to produce ebook content that is difficult to read due to extremely narrow columns, especially if there are more than 2 columns.
Sometimes, for things like side-by-side translations (as is common in bi-lingual treaties, for example) , there might be not much you can do about this.
Block-center narrow content There are no dynamic layouts in exported formats, so narrow text (e.g. plays and poems) will be left aligned on the screen unless something like {{block center}} is used. ”

“ If the user has set a large font (perhaps due to their vision) , they may have a page only 10em wide.
Avoid fixed-width formatting Content spilling off a narrow page. Any formatting that uses a "fixed width" is at risk of not fitting on a mobile device screen, especially if the width end up over about 350px. ”

“ Dot leaders Table dot-leaders generally do not export well, as they are generated by a complex "hack" that some ebook readers do not understand [7] . Most dot-leader templates exclude the dots from the export for this reason.
Other considerations Page breaks
Shortcut:
H:PAGEBREAK
The {{page break}} template should be used to force page breaks in ebooks. It contains special CSS that ebook readers can use to paginate content. ”

“ Green boxes are an indication of correct formatting.
Here, we have a fixed-width block that is wider than the screen. Everything outside the red box will spill off the screen on an e-reader of that size:

[↩︎]

Source: Wikisource

auto_stories Explore the passage content_copy Cite excerpt

“ Do not use it for important content. ☐ {{overfloat image}} ☐ Some TOC template do not export well: for example {{TOCstyle}} and {{Dtpl}}. {{TOC begin}} and plain wikicode tables both work. Headers are not exported The {{header}} template is not exported [1] . This includes the notes field. There should be no content in that field that is necessary for the navigation of the e-book. For example, do not put a Table of Contents in that field if there is no TOC also in the main text body. ”

“ Some templates, like size and alignment templates, have no effect in these exports. Other templates are specifically designed to work as correctly as possible without styling:
{{bar}} and {{longdash}}: degrades to em-dashes Capitalisation and {{small caps}} It is a common construct to use {{small caps|lowercase}} to simulate a word in small caps, rather than {{sm|smaller uppercase}}, eg. ”