DXF / PDF / AI artwork

Status

Field	Value
Extension(s)	.dxf, .pdf, .ai
Common ecosystem	Vector artwork exchange
Format family	Artwork/reference input
Satin Studio status	Researching
Open / import	No
Export	No
Confidence	Medium.

What it is

These formats may carry design artwork from graphics workflows but do not directly describe embroidery stitches.

Satin Studio direction

Possible future asset imports through explicit artwork conversion with unsupported-feature reports.

Versions and variants

DXF, PDF, and AI are each versioned artwork formats. Satin Studio should import through safe, explicit artwork conversion rather than assuming all versions are equivalent.

File identification notes

Container and structure vary by format.

Observed structure notes

• DXF is group-code text/binary CAD data, PDF is a document container, and AI/EPS are PostScript-family artwork containers. None are embroidery stitch streams by themselves.
• Import should extract supported vector geometry into safe project artwork, then require an explicit digitizing step.
• DXF entities are group-code records; useful embroidery artwork usually comes from lines, polylines, splines, arcs, blocks, and layers after unit normalization.
• PDF and AI/EPS artwork extraction can lose editing intent. Import should report unsupported effects, clipping, transparency, gradients, and embedded raster data explicitly.

Structure sketch

These are artwork exchange inputs. The parser should normalize artwork into project assets before digitizing.

enum VectorArtwork<'a> {
    Dxf { records: &'a [DxfGroup<'a>] },
    Pdf { header: &'a [u8], objects: &'a [u8] },
    AiOrEps { postscript: &'a [u8] },
}

struct DxfGroup<'a> {
    code: i32,
    value: &'a str,
}

What we still need

Import pipeline decisions and safe parsing strategy.