Dear Publisher, It is the end of typesetting as we have known it all these years. A patent-pending paging engine in Proof Central 2.0 renders the continuous XML-as-HTML page to neat, cookie-cut pages with publisher logos, footnotes, page numbers. The floats stay close to the their citations. Overfloating, the biggest painpoint of cookiecutting HTML, a rampant issue in ePub, is solved elegantly. Clearly, PostScript paging is too crude to handle the fluidity of HTML. And PDF is too heavy for travel. We need a new file format, one that reverses between fluidity and fixity.
Overfloating, the biggest painpoint of cookie-cutting HTML, is solved elegantly.
You publish in your style of copy editing, XML, DTD, schema. It is a feat of auto-pagination on the browser. There is no server side activity or any legacy desktop application. It is one-touch pagination, and it happens in seconds. Ah, it used to take days - Send file to typesetter -> Repaginate -> Regenerate Dataset -> Reload -> and Send a million signals to dozens of workflow systems that all this is happening. Forget it. Now you don’t need the typesetter to paginate and repaginate. We think your authors are going to be happier than ever before.
It is one-touch, browser-based pagination, and it happens in seconds. It used to take days.
They can see what the page is going to be like after all those changes they make. And they can do it as often as they like until they submit the proof. For the record, they can download it too. Proof Central 2.0 went live in August 2015 for one open access, e-first journal. The revolution has just begun.
In the meantime, Proof Central 1. 0 and 1. x, y, z continue to build on their strengths. Nearly 700, 000 journal articles have come back twice as quick as PDF proofs used to. Over 90% of authors have favoured Proof Central over PDF proofing when given the option to do it either way, consistently, for four years now.
Nearly 700, 000 proofs have returned twice as quick as PDFs used to.
Proof Central has saved publishers a lot of money, has spared them from having to transfer PDF annotations manually; equally from having to face irate authors because a new error got introduced while transferring PDF annotations into the application file.
In Proof Central, a journal article equals one URL (for books, a chapter equals one URL). XML-aware publishing systems share this URL with authors as HTML. The authors view the proof as HTML and edit it, and the XML beneath, and do it WYSIWYG, sans code view, in a Non-Destructive Editing Environment. Once the author finishes, this URL is available to Journal Managers, Editors, Typestters, or other actors as can be configured. Throughout, the XML remains intact.
Proof Central presents XML content as HTML. Users edit the HTML. The system protects the XML.
Every edit, comment, query and response in Proof Central is recorded by time, actor and nature of change in an Edit Log, which then becomes a table of contents of sorts to navigate through the edit points in the manuscript. This valuable record is archived, analysed, databased, secured and cloud-hosted. Request demo. See Presentation.