Answers.Body: <p>First, the Calibre epub reader does include a function to allow you to print an epub file. It accomplishes this by converting it first to a PDF. </p>
  
  <p>There have been efforts to add new features in CSS to make it easier to print (and as a replacement for FOP). </p>
  
  <p>It's already fairly easy to produce both EPUB and PDF. If that is true, there is no special need to make EPUB printable. </p>
  
  <p>The end goal of EPUB is not to produce printable documents, but it's probably true that certain publishers prefer PDF because people can easily download it and print it -- and that feature in missing in EPUB readers. Government bodies, open source communities, educational institutions  and businesses probably benefit from letting users print  EPUB files.  But  Adobe Digital Editions does not include the print function for an unencrypted epub file.  </p>
  
  <p>Up until now, book publishers have been the main force behind the EPUB working group, and so the print-function has been a low priority. (They don't  even want epub reading systems to allow  cutting and pasting!)  I've seen commentary  predicting  that the epub group will align itself more closely to the HTML5 standards group, so maybe it will be easier to incorporating the increasing print functionality of CSS.  </p>
  
  <p>Currently it is not  hard to  convert  EPUB into the more easily printable PDF. Even Calibre does it relatively easy or well, Adobe Indesign should make such conversions easy to do as well.  Incorporating this function into the EPUB reader does not strike me as particularly hard, except Adobe has no commercial incentive to do so. </p>
  
  <p>Another issue is Google. The Google Play epub reader doesn't support page-oriented css (like page-break-before, etc). THE GP reader (and even Readium) don't have print capability even for unencrypted epubs or PDFs. When viewing PDFs in Google Play books on a web browser, you can't even print that. You must open the PDF in the browser itself. </p>
  
  <p>I would guess that scientific publishers like Elsevier have perfected the PDF production process and don't see any real advantage in focusing more on EPUBs -- especially when it's already easy to produce output in both EPUB and PDF (and mobi, etc).  With articles and journals, they want to prevent people from printing these things (or at least to control this ability), and Adobe Reader offers these controls already on PDF. Therefore, there's no need for publishers to want a change.  </p>
  
  <p>Until an epub reading system (standalone or browser-based) develops a way to allow the publisher to control what printing is allowed and what printed is not allowed, it seems unlikely that printing epubs will ever be urgent for people who build reading systems. </p>
  
  <p>From my standpoint as a small indie publisher, I could care less about whether my unencrypted ebooks are easy to print.  If an ebook is unencrypted, then anyone could unzip the file and paste what they want into a MS word document or use Calibre to do it. I see no reason to change my formatting to accommodate the possibility of printing. (Of course, my ebooks are not particularly technical or require elaborate formatting). Maybe my viewpoint will change later.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-21T12:24:16.033Z
Answers.Text: Hi, thanks! About your comment *"There have been efforts to add new features in CSS to make it easier to print"*, I understand that it is 100% the https://www.w3.org/TR/css-break/  ...So, in the context of the question, it is important to explicit that you agree about this consideration, or not.
Answers.UserDisplayName: Peter Krauss
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-22T14:20:18.047Z
Answers.Text: I don't have any special knowledge about this subject, but in the HTML world, this is certainly happening. In the ebook world, it's hard to say...
Answers.UserDisplayName: idiotprogrammer
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-19T15:49:49.327Z
Answers.LastActivityDate: 2018-06-19T15:49:49.327Z
Answers.UserDisplayName: idiotprogrammer
Body: <p>Is there any reason not to  use EPUB after <a href="https://www.w3.org/TR/css-break/" rel="nofollow noreferrer"><strong>CSS3-break</strong> standard</a> is  incorporated  to browsers?</p>
  
  <p>Or will this not be a barrier? </p>
  
  <ul>
  <li><p>for transform HTML or XHTML into PDF, see <a href="https://print-css.rocks" rel="nofollow noreferrer">print-css.rocks</a> (!) or <a href="https://stackoverflow.com/a/21345708/287948">publishing industry from XSL-FO to CSS3</a>. So, can I assume that we not need PDF as main format, PDF it is only a printer-output mode, the main "open ecosystem format" is HTML+CSS.</p></li>
  <li><p>the <a href="https://en.wikipedia.org/wiki/Browser_engine" rel="nofollow noreferrer">renderization-engines</a>:  yes, it is a barrier... But they are evolving in the <em>CSS-break standard</em> tests. (eg. <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=368053" rel="nofollow noreferrer">Chromium</a> passed in 6 of 8 CSS-break tests)... So we can suppose that in near future (2018 or 2019) good "HTML for print" will arrive.<br/>In this "imagined context" there are another barrier?</p></li>
  </ul>
  
  <hr>
  
  <p>As this <a href="https://github.com/w3c/publ-epub-revision/issues/971#issuecomment-301300790" rel="nofollow noreferrer">comment here</a>, right now, EPUB v3.1+ standard is adopting <a href="https://www.w3.org/TR/css-break/" rel="nofollow noreferrer">CSS-break</a>,</p>
  
  <blockquote>
    <p>The following modules have completed design work, and are fairly stable, but have not received much testing and implementation experience yet.
    We hope to incorporate them into a future snapshot.</p>
  </blockquote>
  
  <p>So, this will happen automatically when <a href="https://www.w3.org/TR/CSS/" rel="nofollow noreferrer">CSS working group</a> (as 2018... 2019 Snapshot) decides the CSS-break spec  is both stable and widely implemented.</p>
  
  <hr>
  
  <h2>NOTE for working definition and scepticisms</h2>
  
  <p>Most of EPUB readers produce <em>ugly layout</em>, and EPUB3 format  without CSS3-break can't produce good or professional-quality layout as PDF format... So, there are a lot of scepticism about EPUB. Please, <strong>lets imagine the future in this question (!)</strong>,  please ignore this kind of scepticism.<br/>CSS3break is to improve EPUB layout, and this question is supposing (is correct?) that PDF layout and EPUB layout <strong>will be equivalent</strong> when printing.</p>
  
  <p>... And this quesiton is also not concerned with the (supposedly finite) development time in web browsers ... <em>"The future is now!"</em> for investments and plans in digital preservation.</p>
  
  <p>WORKING DEFINITION: the context here is the use of <strong>HTML5+CSS3break and/or EPUB for official documents</strong>, in a <strong><a href="https://en.wikipedia.org/wiki/Digital_preservation" rel="nofollow noreferrer"><em>digital preservation</em></a> perspective</strong>.  Examples:</p>
  
  <ul>
  <li><p>Open structure and semantic: HTML5 offers a lot of tags for organize contents in a structured way and some semantics. Adding RDFa layer (with good standards as <a href="https://schema.org" rel="nofollow noreferrer">SchemaOrg</a>) we can express any kind of semantic for official contents, from <a href="https://schema.org/ScholarlyArticle" rel="nofollow noreferrer">scientific articles</a> (<em>ScholarlyArticle</em>) to contracts and <a href="https://pending.schema.org/Legislation" rel="nofollow noreferrer">legislation</a>.<br/>In November 2017 <a href="http://webdatacommons.org/structureddata/index.html#results-2017-1" rel="nofollow noreferrer">~1,229,000,000 of URLs was using some kind of HTML+semantic</a>, mainly  <a href="https://en.wikipedia.org/wiki/Microdata_(HTML)" rel="nofollow noreferrer">Microdata</a> and some other variants of the RDFa standard.    <strong>Digital content ecosystem</strong> need HTML, CSS, RDFa, MathML, etc. (<strong>not PDF</strong>). <br/>When a digital preservation initiative need to "zip all content in to a file", can use EPUB standard.<br/><strong>Conclusion</strong>: only attractives (plans to enhance all with CSS3-break), no barriers to use EPUB for digital preservation. </p></li>
  <li><p>Open Science: today they use a XHTML-like format,  the <a href="https://en.wikipedia.org/wiki/Journal_Article_Tag_Suite" rel="nofollow noreferrer">JATS</a> standard, as  official digital preservation format for scientific articles, and the "content matrix" that generats all other formats (EPUB and HTML automatic but PDF not)... There are many "official preservarion repositories" as PMC and SciELO. <a href="https://www.ncbi.nlm.nih.gov/pmc/" rel="nofollow noreferrer">PubMed Central</a> offerts ~5 million articles in all formats, including ~5 million of EPUB.<br/>Sample PMC2150930 article in all formats: ugly layout <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930/epub/" rel="nofollow noreferrer">EPub</a> and good <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930/pdf/f-62-00001.pdf" rel="nofollow noreferrer">PDF</a>, and HTML variants as  <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930/?report=classic" rel="nofollow noreferrer">HTML classic layout</a>,
  <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930" rel="nofollow noreferrer">HTML modern layout</a>.<br/> There are plans to migrate from JATS to <em>ScholarlyArticle</em> in minor publisher houses, to use directly HTML5+RDFa as official digital preservation format.<br/><strong>Conclusion</strong>: only attractives, no barriers to use EPUB+CSS3break for digital preservation in <a href="https://en.wikipedia.org/wiki/Open_science" rel="nofollow noreferrer">open science</a>. </p></li>
  <li><p>Open Government and Digital transparency: today all contries are migrating its "official documents", that are articles in the <a href="https://en.wikipedia.org/wiki/Government_gazette" rel="nofollow noreferrer">government gazettes</a>, from PDF to HTML and/or EPUB... They are going up the stairs in the <a href="http://5stardata.info/en/" rel="nofollow noreferrer">5-star deployment scheme for Open Data</a>. It is a transition: e.g.  <a href="http://eur-lex.europa.eu/n-lex/" rel="nofollow noreferrer">European countries National Law</a>, <a href="http://portal.imprensanacional.gov.br" rel="nofollow noreferrer">Brazilian Official Gazzete</a>,  <a href="http://www.legislation.gov.uk" rel="nofollow noreferrer">UK legislation</a>, etc. today are producing "twin documents" (HTML and PDF) from a XML matrix.<br/>... With CSS3break they will need only HTML as matrix. In fact, there are plans to migrate from "ugly non-standard XML" to good XHTML5 (plus RDFa when necessary) in minor publisher houses, so HTML ecosystem as "content matrix", and EPUB as official digital preservation format.<br/><strong>Conclusion</strong>: only attractives, no barriers to use EPUB+CSS3break for digital preservation in open government. </p></li>
  </ul>
  
  <p>PS: of course, the conclusions above are personal and only a illustrative sample. The question is looking for better foundations, credible and/or official sources, etc.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-15T03:11:48.547Z
Comments.Text: I need answer for +50 rep.
Comments.UserDisplayName: 69 420 1970
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-15T15:36:31.780Z
Comments.Text: Hi @NemoXXX, yes, the question seems, but it is not "purely academic question" as you say. The business face is investment, the "how much" and the "timming" thing... Raising capital for a small publishing houses: we need discuss, with a little bit more of *"reliable theoretical fundations"*, to reduce risks and attrack more investors.
Comments.UserDisplayName: Peter Krauss
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-15T23:34:54.360Z
Comments.Text: Thanks @misdeed (!),  please check if you agree with the question's text changes.
Comments.UserDisplayName: Peter Krauss
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-15T23:56:21.230Z
Comments.Text: @PeterKrauss, agree. Fine!
Comments.UserDisplayName: 69 420 1970
Tags: <epub><page-break>
Title: CSS3-break will break PDF? In a digital preservation perspective
UserDisplayName: Peter Krauss
ThreadText: # CSS3-break will break PDF? In a digital preservation perspective
  
  (Asked by: username_0 on 2018-06-12)
  
  Is there any reason not to use EPUB after [**CSS3-break** standard](https://www.w3.org/TR/css-break/) is incorporated to browsers?
  
  Or will this not be a barrier?
  
  * for transform HTML or XHTML into PDF, see [print-css.rocks](https://print-css.rocks) (!) or [publishing industry from XSL-FO to CSS3](https://stackoverflow.com/a/21345708/287948). So, can I assume that we not need PDF as main format, PDF it is only a printer-output mode, the main "open ecosystem format" is HTML+CSS.
  * the [renderization-engines](https://en.wikipedia.org/wiki/Browser_engine): yes, it is a barrier... But they are evolving in the *CSS-break standard* tests. (eg. [Chromium](https://bugs.chromium.org/p/chromium/issues/detail?id=368053) passed in 6 of 8 CSS-break tests)... So we can suppose that in near future (2018 or 2019) good "HTML for print" will arrive.  
    In this "imagined context" there are another barrier?
  
  ---
  
  As this [comment here](https://github.com/w3c/publ-epub-revision/issues/971#issuecomment-301300790), right now, EPUB v3.1+ standard is adopting [CSS-break](https://www.w3.org/TR/css-break/),
  
  > The following modules have completed design work, and are fairly stable, but have not received much testing and implementation experience yet.
  > We hope to incorporate them into a future snapshot.
  
  So, this will happen automatically when [CSS working group](https://www.w3.org/TR/CSS/) (as 2018... 2019 Snapshot) decides the CSS-break spec is both stable and widely implemented.
  
  ---
  
  ## NOTE for working definition and scepticisms
  
  Most of EPUB readers produce *ugly layout*, and EPUB3 format without CSS3-break can't produce good or professional-quality layout as PDF format... So, there are a lot of scepticism about EPUB. Please, **lets imagine the future in this question (!)**, please ignore this kind of scepticism.  
  CSS3break is to improve EPUB layout, and this question is supposing (is correct?) that PDF layout and EPUB layout **will be equivalent** when printing.
  
  ... And this quesiton is also not concerned with the (supposedly finite) development time in web browsers ... *"The future is now!"* for investments and plans in digital preservation.
  
  WORKING DEFINITION: the context here is the use of **HTML5+CSS3break and/or EPUB for official documents**, in a **[*digital preservation*](https://en.wikipedia.org/wiki/Digital_preservation) perspective**. Examples:
  
  * Open structure and semantic: HTML5 offers a lot of tags for organize contents in a structured way and some semantics. Adding RDFa layer (with good standards as [SchemaOrg](https://schema.org)) we can express any kind of semantic for official contents, from [scientific articles](https://schema.org/ScholarlyArticle) (*ScholarlyArticle*) to contracts and [legislation](https://pending.schema.org/Legislation).  
    In November 2017 [~1,229,000,000 of URLs was using some kind of HTML+semantic](http://webdatacommons.org/structureddata/index.html#results-2017-1), mainly [Microdata](https://en.wikipedia.org/wiki/Microdata_(HTML)) and some other variants of the RDFa standard. **Digital content ecosystem** need HTML, CSS, RDFa, MathML, etc. (**not PDF**).   
    When a digital preservation initiative need to "zip all content in to a file", can use EPUB standard.  
    **Conclusion**: only attractives (plans to enhance all with CSS3-break), no barriers to use EPUB for digital preservation.
  * Open Science: today they use a XHTML-like format, the [JATS](https://en.wikipedia.org/wiki/Journal_Article_Tag_Suite) standard, as official digital preservation format for scientific articles, and the "content matrix" that generats all other formats (EPUB and HTML automatic but PDF not)... There are many "official preservarion repositories" as PMC and SciELO. [PubMed Central](https://www.ncbi.nlm.nih.gov/pmc/) offerts ~5 million articles in all formats, including ~5 million of EPUB.  
    Sample PMC2150930 article in all formats: ugly layout [EPub](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930/epub/) and good [PDF](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930/pdf/f-62-00001.pdf), and HTML variants as [HTML classic layout](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930/?report=classic),
    [HTML modern layout](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2150930).  
     There are plans to migrate from JATS to *ScholarlyArticle* in minor publisher houses, to use directly HTML5+RDFa as official digital preservation format.  
    **Conclusion**: only attractives, no barriers to use EPUB+CSS3break for digital preservation in [open science](https://en.wikipedia.org/wiki/Open_science).
  * Open Government and Digital transparency: today all contries are migrating its "official documents", that are articles in the [government gazettes](https://en.wikipedia.org/wiki/Government_gazette), from PDF to HTML and/or EPUB... They are going up the stairs in the [5-star deployment scheme for Open Data](http://5stardata.info/en/). It is a transition: e.g. [European countries National Law](http://eur-lex.europa.eu/n-lex/), [Brazilian Official Gazzete](http://portal.imprensanacional.gov.br), [UK legislation](http://www.legislation.gov.uk), etc. today are producing "twin documents" (HTML and PDF) from a XML matrix.  
    ... With CSS3break they will need only HTML as matrix. In fact, there are plans to migrate from "ugly non-standard XML" to good XHTML5 (plus RDFa when necessary) in minor publisher houses, so HTML ecosystem as "content matrix", and EPUB as official digital preservation format.  
    **Conclusion**: only attractives, no barriers to use EPUB+CSS3break for digital preservation in open government.
  
  PS: of course, the conclusions above are personal and only a illustrative sample. The question is looking for better foundations, credible and/or official sources, etc.
  
  **Tags:** epub, page-break
  
  > **Comments:**
  > **username_1**: I need answer for +50 rep.  
  > **username_0**: Hi @NemoXXX, yes, the question seems, but it is not "purely academic question" as you say. The business face is investment, the "how much" and the "timming" thing... Raising capital for a small publishing houses: we need discuss, with a little bit more of *"reliable theoretical fundations"*, to reduce risks and attrack more investors.  
  > **username_0**: Thanks @misdeed (!),  please check if you agree with the question's text changes.  
  > **username_1**: @PeterKrauss, agree. Fine!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2018-06-19. Score: 2
  
  First, the Calibre epub reader does include a function to allow you to print an epub file. It accomplishes this by converting it first to a PDF.
  
  There have been efforts to add new features in CSS to make it easier to print (and as a replacement for FOP).
  
  It's already fairly easy to produce both EPUB and PDF. If that is true, there is no special need to make EPUB printable.
  
  The end goal of EPUB is not to produce printable documents, but it's probably true that certain publishers prefer PDF because people can easily download it and print it -- and that feature in missing in EPUB readers. Government bodies, open source communities, educational institutions and businesses probably benefit from letting users print EPUB files. But Adobe Digital Editions does not include the print function for an unencrypted epub file.
  
  Up until now, book publishers have been the main force behind the EPUB working group, and so the print-function has been a low priority. (They don't even want epub reading systems to allow cutting and pasting!) I've seen commentary predicting that the epub group will align itself more closely to the HTML5 standards group, so maybe it will be easier to incorporating the increasing print functionality of CSS.
  
  Currently it is not hard to convert EPUB into the more easily printable PDF. Even Calibre does it relatively easy or well, Adobe Indesign should make such conversions easy to do as well. Incorporating this function into the EPUB reader does not strike me as particularly hard, except Adobe has no commercial incentive to do so.
  
  Another issue is Google. The Google Play epub reader doesn't support page-oriented css (like page-break-before, etc). THE GP reader (and even Readium) don't have print capability even for unencrypted epubs or PDFs. When viewing PDFs in Google Play books on a web browser, you can't even print that. You must open the PDF in the browser itself.
  
  I would guess that scientific publishers like Elsevier have perfected the PDF production process and don't see any real advantage in focusing more on EPUBs -- especially when it's already easy to produce output in both EPUB and PDF (and mobi, etc). With articles and journals, they want to prevent people from printing these things (or at least to control this ability), and Adobe Reader offers these controls already on PDF. Therefore, there's no need for publishers to want a change.
  
  Until an epub reading system (standalone or browser-based) develops a way to allow the publisher to control what printing is allowed and what printed is not allowed, it seems unlikely that printing epubs will ever be urgent for people who build reading systems.
  
  From my standpoint as a small indie publisher, I could care less about whether my unencrypted ebooks are easy to print. If an ebook is unencrypted, then anyone could unzip the file and paste what they want into a MS word document or use Calibre to do it. I see no reason to change my formatting to accommodate the possibility of printing. (Of course, my ebooks are not particularly technical or require elaborate formatting). Maybe my viewpoint will change later.
  
  > **Comments:**
  > **username_0**: Hi, thanks! About your comment *"There have been efforts to add new features in CSS to make it easier to print"*, I understand that it is 100% the https://www.w3.org/TR/css-break/  ...So, in the context of the question, it is important to explicit that you agree about this consideration, or not.  
  > **username_2**: I don't have any special knowledge about this subject, but in the HTML world, this is certainly happening. In the ebook world, it's hard to say...  
  
  ---
  
  