docrev 0.6.6 → 0.6.7

package/README.md

@@ -1,24 +1,19 @@
 # docrev
 
 [![npm](https://img.shields.io/npm/v/docrev)](https://www.npmjs.com/package/docrev)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-**Write papers in plain text. Generate Word when needed.**
-
-## Why
-
-Scientific papers go through many revision cycles. You send a Word document to collaborators, they add comments and track changes, you address the feedback and send it back. Then journal submission, reviewer comments, more revisions. After a few rounds, track changes become unreadable, you have fifteen versions of the same file, and nobody knows which one is current. Equations break when copying between documents. Figures get embedded at the wrong resolution or disappear entirely.
-
-docrev takes a different approach. You write in plain text using Markdown, a simple formatting syntax that takes ten minutes to learn. When you need to share with collaborators or submit to a journal, docrev generates a Word document or PDF. Your collaborators review and comment in Word as usual. When they send it back, docrev imports their feedback into your Markdown files. You address the comments, rebuild the document, and send it back. The cycle continues, but your source files stay clean and under version control.
-
-Your collaborators do not need to install anything or change how they work. They keep using Word. You handle the conversion on your end. The result is proper version history, equations that never break, figures that stay linked rather than embedded, and automated citation formatting.
+Write scientific papers in Markdown. Generate Word documents for collaborators. Import their feedback. Repeat.
 
 ```
-Markdown files  -->  docrev  -->  Word/PDF
-      ^                              |
-      |                              v
-      +---- docrev <---- reviewer feedback
+Markdown  ──►  docrev  ──►  Word/PDF  ──►  Collaborators
+    ▲                                           │
+    └───────────  docrev  ◄─────────────────────┘
+                (import feedback)
 ```
 
+Scientific papers go through many revision cycles with collaborators and reviewers. Track changes become unreadable, versions multiply, equations break when copying, figures get embedded at wrong resolutions. docrev keeps your source in plain Markdown under version control while generating Word documents for the review cycle. Your collaborators keep using Word as usual. You handle conversion on your end.
+
 ## Install
 
 ```bash

package/bin/rev.js

@@ -1683,7 +1683,11 @@ program
             }
           }
 
-          // Step 1: Replace comments with markers
+          // Step 1: Strip track changes but keep comments for Word conversion
+          // This applies {++insertions++}, removes {--deletions--}, keeps {>>comments<<}
+          markdown = stripAnnotations(markdown, { keepComments: true });
+
+          // Step 2: Replace comments with markers
           const spinMarkers = fmt.spinner('Preparing markers...').start();
           const { markedMarkdown, comments } = prepareMarkdownWithMarkers(markdown);
           spinMarkers.stop();
@@ -1691,11 +1695,11 @@ program
           if (comments.length === 0) {
             console.log(chalk.yellow('\nNo comments found - skipping comments DOCX'));
           } else {
-            // Step 2: Write marked markdown to temp file
+            // Step 3: Write marked markdown to temp file
             const markedPath = path.join(dir, '.paper-marked.md');
             fs.writeFileSync(markedPath, markedMarkdown, 'utf-8');
 
-            // Step 3: Build DOCX from marked markdown using pandoc
+            // Step 4: Build DOCX from marked markdown using pandoc
             const spinBuild = fmt.spinner('Building marked DOCX...').start();
             const markedDocxPath = path.join(dir, '.paper-marked.docx');
             const pandocResult = await runPandoc(markedPath, 'docx', config, { ...options, outputPath: markedDocxPath });
@@ -1704,7 +1708,7 @@ program
             if (!pandocResult.success) {
               console.error(chalk.yellow(`\nWarning: Could not build marked DOCX: ${pandocResult.error}`));
             } else {
-              // Step 4: Replace markers with comment ranges
+              // Step 5: Replace markers with comment ranges
               const commentsDocxPath = docxResult.outputPath.replace(/\.docx$/, '_comments.docx');
               const spinInject = fmt.spinner('Injecting comments at markers...').start();
               const commentResult = await injectCommentsAtMarkers(markedDocxPath, comments, commentsDocxPath);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docrev",
-  "version": "0.6.6",
+  "version": "0.6.7",
   "description": "Academic paper revision workflow: Word ↔ Markdown round-trips, DOI validation, reviewer comments",
   "type": "module",
   "types": "types/index.d.ts",