mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-11-18 17:50:02 +00:00
Under automation read roots, an exporter plug-in's format (plugin.<id>) counts as an output that carries the native document, since its plug-in is given the document's JSON. document.serialize, document.export, document.exportSelection, Export for Screens and assets.export rows and file.exportAs refuse it before the plug-in runs and before any file or folder is written when the document links a JavaScript file, a linked image or placed file, a kept relative path or a data set's image outside the roots, with the existing errors. The JSON the plug-in is given leaves out an Export for Screens folder outside the roots. file.package refuses, before anything is written, a linked file whose native document it can't read to check: a native document that doesn't load, a PDF or .ai file that can't be opened (one that needs a password to open, or a damaged one), and a PDF, .ai or EPS file whose editing data doesn't load. The error, "a linked file's editing data can't be read to check it against the read roots", names no file or folder and gets rows in the complete-message catalogs. A PDF or EPS file without editing data is copied as before, and packages made without read roots are unchanged.