From 513685a22134e8af5325570a2f656aca1fa1fbcc Mon Sep 17 00:00:00 2001 From: dotCooCoo Date: Thu, 15 Oct 2026 10:17:44 -0700 Subject: [PATCH] Docs: the Print section describes printing through the system's print service MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Print section of docs/mcp.md said that File → Print writes the job as a print-ready PDF and that there is no printer driver. The desktop app sends the PDF to the system's print service, the web build opens the browser's print dialog on it, and the PDF File entry in the Printer list saves it. The section now says so, points to Printing, and marks the `file.print` reply that follows as the headless one. --- docs/mcp.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/mcp.md b/docs/mcp.md index 8277b7e8b..9f48609f3 100644 --- a/docs/mcp.md +++ b/docs/mcp.md @@ -2477,8 +2477,10 @@ Screens doesn't write EPS. ## Print -File → Print writes the job as a print-ready PDF (there is no printer driver): each page is a sheet of the chosen -paper. `file.print {settings?, path?}` → `{pages, path | dataBase64, bytes, warnings}`; `print.preview {settings?}` +File → Print lays the job out as a print-ready PDF, in which each page is a sheet of the chosen paper. The desktop app +sends the PDF to the system's print service, and the web build opens the browser's print dialog on it. With PDF File +picked as the printer, File → Print saves the PDF instead (see Printing). Headless, `file.print {settings?, path?}` → +`{pages, path | dataBase64, bytes, warnings}`; `print.preview {settings?}` answers what it would print without writing it: `{pages (copies included), sheets: [{artboard, tile?, ink?, width, height, orientation, scale}] (one copy, in order), tiles: [{artboard, columns, rows, printed, tiles}] (document space), inks: [{name, spot, print, frequency, angle}], warnings, settings}`. `print.setup {settings?}` saves the