DXF / PDF / AI artwork

Status

What it is

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

Satin Studio behavior

Import converts supported vector geometry into project artwork and lists every omitted or flattened feature before you accept the result.

Versions and variants

DXF, PDF, and AI each have their own versions and dialects. Satin Studio identifies the source version before conversion instead of treating the extensions as 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,
}

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.