PDF worksheets and proofs
Status
| Field | Value |
|---|---|
| Extension(s) | .pdf |
| Common ecosystem | Human production notes |
| Format family | Report/export artifact |
| Satin Studio status | Supported export |
| Open / import | No |
| Export | Yes |
| Confidence | High for workflow role. |
What it is
PDF worksheets and proofs are human-readable production artifacts with thread charts, color order, approvals, or sew-out notes.
Satin Studio behavior
PDF export creates a human-readable proof or production worksheet. It never stands in for the machine stitch file or editable project.
Versions and variants
The exporter writes a self-contained PDF with embedded fonts, dimensions, thread order, construction steps, proof identity, and project-version identity.
File identification notes
PDF document.
Observed structure notes
- PDF files start with a
%PDF-header and end with a trailer/cross-reference structure or xref stream. - For Satin Studio, PDF is an output artifact. It should be generated from project facts rather than imported as embroidery source.
- PDF generation should embed all worksheet facts from the project version used for export. Importing a PDF back into Satin Studio should not recreate editable embroidery objects.
Structure sketch
PDF worksheets are document exports, not embroidery stitch streams.
struct PdfDocument<'a> {
header: &'a [u8], // starts with b"%PDF-"
body_objects: &'a [PdfObject<'a>],
xref_or_xref_stream: &'a [u8],
trailer: &'a [u8],
}
struct PdfObject<'a> {
object_id: u32,
generation: u16,
payload: &'a [u8],
}
Compatibility evidence
Compatibility checks cover signatures, metadata, command boundaries, malformed records, and files from the machines and software named above. Unsupported variants stop with a specific report instead of being silently rewritten.