Professional Publishing Software

Professional publishing software is not writing software. It is production publishing software. Its purpose is to take manuscripts (docx, LaTeX, etc) and convert them into standardised publish-grade documents for print (PDF) and web (HTML) at industrial scale.

What Professional Publishing Software Does

Large academic publishers rely on specialised systems to:

• Control typography, layout, and page design
• Enforce journal house styles
• Manage images, tables, and references
• Track revisions through editorial workflows
• Generate PDF, HTML, and EPUB outputs
• Distribute structured metadata to indexing systems

In modern publishing, the true “source of truth” is usually structured XML; in many large journal publishers, this is a format called JATS (Journal Article Tag Suite). Word files are typically converted into structured markup before final production.

The Industrial Workflow

The professional publishing pipeline can be reduced to:

Structured text (docx, LaTeX) → structured markup (JATS) → formatted outputs (PDF, HTML).

Publishers operate conversion engines. They transform structured content into styled formats suitable for print, web, and archiving. Professional publishing suites like Adobe InDesign, 3B2/APP, Arbortext, Typefi, Antenna House, FrameMaker are used by publishers.

The docx format is not inherently unstructured, but it is primarily designed for visual formatting rather than semantic clarity. Authors often encode appearance instead of meaning — manually adjusting fonts, spacing, and layout instead of defining structural elements such as sections, captions, and references in a consistent way. This produces countless small inconsistencies and edge cases that must be cleaned, normalised, and reinterpreted during professional publishing. As a result, large and expensive production systems exist largely to repair and standardise visually formatted manuscripts before they can be converted into reliable, machine-readable outputs.

Proprietary e-readers

As well as the backend proprietary software, there are also many user-facing proprietary software whose purpose is to protect the copyright of publications. Institutional libraries often do not own the book or article, but effectively loan the title from the publisher. These software provide a custom GUI for users reading pdf, epub and other formats. ProQuest Ebook Central and Adobe Digital Editions are two prominant software; there are others such as EBSCO ebook, and JSTOR ebook. Again, this "service" is not for the benefit of the reader; it's a digital library system to protect ebooks from actually being downloaded and read offline. Further, they effectively push university libraries and other institutional research providers into a proprietary software stack, which is very difficult to later change. It is very easy for the library to then provide all titles via these e-readers, not just the titles loaned from publishers. Even if a library has the rights to freely distribute the title offline, it may not do so because this would require two separate systems. Why not just make the libraries' job easier, and provide everything through ProQuest? Just like other proprietary software, it effectively produces a monopoly within an institution, and the reader must use that proprietary software in practice, even though there is absolutely no requirement to do so in law. Even where a download chapter option is provided, it is designed to inconvenience the user so much that they will decide to use the proprietary software anyway. For example, there are page limits to downloads, copy limits, etc which deliberately restrict the freedom of the reader to use the document as they wish. See ProQuest e-reader limits as a typical example.

The Plain Text Alternative

An open workflow replaces this industrial model with a simpler and more transparent systems that individual scholars can do alone, without a multimillion dollar publishing industry:

1. Write in plain text (Markdown, LaTeX, Typst, or similar).

It is simple to convert a structured plain text document to html; this replaces proprietary layout engines.

What This Replaces

• Layout software → CSS styling
• Production XML systems → open conversion software such as Pandoc

The Structural Shift

Print publishing required centralized layout control, expensive production tools, and managed distribution networks. The web eliminates those constraints.

When scholars no longer depend on expensive professional publishing workflows, they regain control over their own academic production process. Instead of submitting manuscripts into proprietary systems that handle formatting, distribution, and archiving behind closed infrastructure, researchers can write in open formats, generate their own outputs, and distribute their work directly. In practical terms, this means scholars 'control the means of academic production': the tools, the versions, the dissemination, and the archive. For those concerned with intellectual autonomy, institutional independence, and the long-term stewardship of knowledge, this shift represents a profound structural advantage.

When the canonical source is plain text and the primary distribution format is HTML, the publisher no longer owns the research. At most, it provides styling, curation, and endorsement.

Publishing becomes a process of versioned knowledge, openly distributed and socially validated rather than industrially controlled.