E?? / F??

Status

Field	Value
Extension(s)	.e00–.e99, .f00–.f99 style leads
Common ecosystem	Eltac / Forton leads
Format family	Machine-specific lead
Satin Studio status	Researching
Open / import	No
Export	No
Confidence	Low.

What it is

Some embroidery format lists describe numbered Eltac and Forton file families where the first letter is followed by version or machine digits.

Satin Studio direction

Research lead only.

Versions and variants

The suffix digits may be part of the format family. Treat each observed extension as a dialect until proven otherwise.

File identification notes

Reported details:

• Eltac .e??: 256-byte header with triplet-coded DST-style encoding.
• Forton .f??: 256-byte header with unsigned x, y, control-style encoding.

Observed structure notes

• Observed Eltac/Forton leads use fixed headers plus compact stitch records, but the numbered extensions are not one proven format.
• Observed .exy-style files use Eltac-specific records; observed .fxy-style files follow unsigned x, y, control-style movement. Each suffix still needs separate validation.

Structure sketch

The numbered E/F families should be tracked as separate dialects.

struct EltacENumberedFile<'a> {
    header: [u8; 256],                 // reported fixed header
    dst_style_triplets: &'a [[u8; 3]], // reported triplet-coded DST-style body
}

struct FortonFNumberedFile<'a> {
    header: [u8; 256],
    records: &'a [UnsignedTripletRecord],
}

struct UnsignedTripletRecord {
    x: u8,
    y: u8,
    control: u8,
}

What we still need

Files with exact extensions, machine/software provenance, and command mapping.