Intro to paged.js
Notes from 2019 Editoria Community Meeting Discussion
Participants: Fred, Kate, Nicholas,Lisa, Bob
- how can non-developer production editors made changes in CSS/paged.js; composition and text editing, separate from design
- Fred--they're trying to make documentation for how to use it, in particular how to make changes that will result in the outputs that the user wants
Nicholas' Use Case
They work in Open Office and apply their own styles (this is editors doing this, not authors) He used Inkscape for the cover, not paged.js. (At UC Press covers are handled completely separately)
Many ways to produce a book
Have to edit the PDF output to put in the crop marks
Why does footnote text have to be inline where the reference is for paged.js to read it?
Wax is storing edits and Editoria is sending HTML to paged.js
We have to be careful about not assuming that everyone is comfortable with every view of the text (e.g. some people will see HTML encoded text and not be comfortable editing there)
There is a limit to how automated the production can be, for example for the set of typesetting "unacceptables", such as ensuring pages are bottom-aligned, either in paged.js or Wax. We need to collect this set of specifications. Production editors need to make minor page-specific fixes. There is a problem with this now, in that you can make changes in Wax, but that's not the PDF/print output. Options are either accepting these, or recognizing that there is a new set of skills that typesetters, production editors, compositors will need to have in web-based book production.
InDesign can export EPUB and HTML; CSS is embedded; Lisa asked if you could feed the CSS to paged.js, but Nicholas was concerned that it would be very noisy and it might not be more efficient. We looked at this, and it looked good for importing. The person working on genealogical books uses this workflow. #269
Idea of new publishers coming to Editoria who could import one or more house "styles" into Editoria that paged.js wills start with. Challenges: need Wax to know about the styles; also won't have pagination, etc.