Tag: Version Control

The transformation of an unpolished raw manuscript into an authoritative, market-ready volume is fundamentally an intensive collaborative human endeavor. The dynamic partnership between an author and their professional editor is one of the most creatively intimate relationships in the creative industries. However, without disciplined communication protocols, rigorous software version control, and standardized digital markup hygiene, the editorial process can rapidly descend into catastrophic file corruption, lost revisions, conflicting authorial queries, and damaged creative relationships.

In modern trade publishing, academic presses, and professional independent self-publishing pipelines, the editorial collaboration unfolds across distinct digital stages: tracking changes, querying ambiguities, resolving authorial disputes, and managing multi-file anthologies. Utilizing standard editorial markups in Microsoft Word Track Changes, maintaining living Editorial Style Sheets, and establishing unshakeable file naming conventions are the technical prerequisites for seamless publishing production. This comprehensive guide details the psychology of editorial diplomacy, digital markup mechanics, query formatting standards, conflict resolution protocols, and software version control architectures.

While historic editing was conducted on physical paper galleys using standardized red-ink proofreader symbols (such as delete loops, caret insertions, and transposition marks), modern trade editing is executed digitally inside Microsoft Word (.docx) utilizing the Track Changes engine. Using Track Changes effectively requires a shared understanding of mechanical conventions:

• Locking the Baseline Document: Before making a single keystroke, the editor saves the author’s original submission as an unedited, read-only Milestone Archive. Track Changes is activated, and Word options are configured to show inline strike-throughs for deletions, distinct colored underlines for insertions, and margin balloons for editorial queries.
• Granular Insertion and Deletion Discipline: Editors must avoid sloppy multi-word selections that delete punctuation alongside words unnecessarily. For example, when changing ‘He ran quickly, but stumbled’ to ‘He sprinted, then stumbled’, the editor changes only the specific target words, preserving surrounding comma punctuation to minimize visual clutter in the author’s review pane.
• Clean Passes vs. Tracked Passes: When returning an edited manuscript, professional publishing houses provide the author with two distinct files:
  1. The Tracked Changes File: Displays every single deletion, insertion, formatting tweak, and margin comment. This allows the author to inspect every editorial intervention.
  2. The Clean Review File: All proposed insertions and deletions are accepted, with only margin query comments remaining visible. This allows the author to read the text smoothly in its improved state without being overwhelmed by red strike-through text.

1. Track Changes Software Configuration (Microsoft Word / Docs):
   - Markup View: Simple Markup for reading flow | All Markup for audit inspection
   - Deletions Display: Strikethrough in red / maroon (Inline text)
   - Insertions Display: Underline in dark blue / teal
   - Formatting Tracking: Font size, italics, small-caps changes logged in margin balloons
2. Standard File Nomenclature Architecture:
   - Structure: [PROJECT]_[STAGE]_[ROLE]_[INITIALS]_[YYYYMMDD].docx
   - Example (Dev Edit): GILDEDPAGES_DevEdit_AuthorReview_AP_20261014.docx
   - Example (Copyedit): GILDEDPAGES_Copyedit_Pass1_EM_20261028.docx
   - Golden Rule: Never use 'Final' or 'Updated' in living project files
3. Editorial Style Sheet Sections (The Living Style Bible):
   - Part 1: Primary Reference Guides (e.g., CMOS 17th ed., Merriam-Webster's 11th Collegiate)
   - Part 2: Specific Word List (Spelling, hyphenation, capitalization anomalies)
   - Part 3: Character Directory (Ages, physical descriptions, eye colors, lineage)
   - Part 4: Timeline & Geochronology (Day-by-day sequence of events)
   - Part 5: Fictional Terminology / Jargon / Foreign Expressions

The single most vital technical document generated during the editing of a book is the Editorial Style Sheet. Created by the developmental editor and continuously expanded by the line and copyeditor, the style sheet functions as the customized, unyielding ‘constitution’ of the specific book project.

A comprehensive Editorial Style Sheet contains five core sections:

• 1. Authority and Baseline Standards: Identifies the project’s governing style manual (e.g., The Chicago Manual of Style, 17th Edition) and governing dictionary (e.g., Merriam-Webster’s Collegiate Dictionary, 11th Edition). Any deviations from these authorities must be explicitly logged.
• 2. Alphabetical Word List and Hyphenation Registry: Catalogs hundreds of specific lexical decisions made during editing:
  • Hyphenated compounds vs. closed compounds (e.g., ‘decision-maker’ vs. ‘decisionmaker’).
  • Capitalization conventions (e.g., ‘the President’ when preceding a name, but ‘the president’ in general narrative; ‘Earth’ as a planet vs. ‘earth’ as soil).
  • Numbers style (e.g., spelling out numbers zero through one hundred in prose, using numerals for percentages and physical measurements).
• 3. Character & Setting Master Directory: Logs every named character, their full aliases, physical traits (eye color, scars, handedness), birthdates, and family relationships. This prevents continuity blunders where a character’s blue eyes turn brown in chapter fourteen.
• 4. Chronology & Temporal Timeline: A day-by-day or hour-by-hour calendar tracking narrative time, travel durations, and moon phases.
• 5. Fictional / Worldbuilding Lexicon: In fantasy, science fiction, or technical non-fiction, logs spellings, grammatical rules, and italicization criteria for invented languages, alien flora/fauna, or technical acronyms.

When an editor encounters an ambiguity, logical inconsistency, potential libel issue, or confusing phrasing that cannot be resolved with a simple grammar fix, they insert an Editorial Query (AU Query) into the manuscript margin. Query writing is an art of psychological diplomacy:

• The Anatomy of an Effective Query: Professional queries follow a three-part structure:
  1. State the Problem Objectively: Describe the observed ambiguity without personal judgment (e.g., ‘AU: In Chapter 3, Marcus arrived in Paris by steam train on Tuesday evening, but here on Wednesday morning he mentions driving his automobile across Normandy…’).
  2. Explain the Reader’s Perspective: Explain why the friction matters to the reading audience (e.g., ‘…Readers may be confused by the sudden timeline acceleration and transport shift.’).
  3. Propose Actionable Solutions: Offer two or three concrete options (e.g., ‘Suggested fix: (A) Change train to automobile in Chapter 3; (B) Clarify that he rented the vehicle upon arrival; or (C) Revise timeline to Thursday. Please advise on preferred resolution.’).
• Tone and Editorial Humility: An editor must never write dismissive or sarcastic queries (such as ‘This makes no sense’ or ‘Awkward’). The editor’s stance is that of the author’s ideal, highly attentive reader whose sole objective is to help the author realize their own creative vision.

A fundamental ethical tenet of literary publishing is that the author retains ultimate creative ownership of their work. While editors provide authoritative recommendations, the author’s byline appears on the cover, and the author lives with the final product. Navigating editorial disagreements requires structured conflict resolution:

• The ‘Pick Your Battles’ Philosophy: Experienced authors and editors know that not every change is worth fighting over. If an editor corrects a comma splice or eliminates an unintentional dangling modifier, the author should accept the correction gracefully. Conversely, if an editor attempts to standardize an intentionally fragmented, poetic, stream-of-consciousness passage, the author has every right to ‘Stet’ the change.
• The Power of ‘Stet’: The Latin term ‘Stet’ (meaning ‘let it stand’) is used by authors to reject an editorial change and restore the original text. When writing ‘Stet’ in a comment balloon, professional authors provide brief context (e.g., ‘Stet. This dialect rhythm is intentional for this rural character.’).
• The 48-Hour Cooling Rule: When an author receives an extensively tracked manuscript, the psychological initial reaction is often shock, defensiveness, or grief upon seeing pages filled with red markings. Professional editors advise authors to close the file and step away for at least 48 hours. Once initial emotional defensiveness fades, authors almost universally recognize that 90% of the proposed edits substantially elevate the prose.

When all author queries are resolved, all Track Changes are accepted, and the manuscript is formally declared ‘Copyedited Clean’, the editor performs the final prepress cleanup before handing the file to the interior book designer:

• Accepting All Changes: The editor runs a final Word macro that accepts all tracked changes and deletes all resolved comment balloons. Submitting a file with lingering tracked changes into Adobe InDesign can cause rejected words to bleed into the final printed page.
• Global Character Cleansing: The editor runs GREP search-and-replace routines to eradicate common typographic errors: replacing double spaces with single spaces, converting straight typewriter quotes (") into true typographer curly quotes (“”), ensuring ellipses are formatted as proper Unicode ellipsis glyphs (…) or spaced periods, and converting double hyphens (--) into true em-dashes (—).
• Handoff Package: The final prepress delivery consists of the clean manuscript .docx, the complete Editorial Style Sheet, and an introductory brief detailing front matter requirements, dedication wording, and any special design requests.