You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
UCS reads its R2000+ elevation and ortho fields on R13/R14 (§20.4.62) #274
The spec's own example, §20.4.62.1 (p171-172, OBJECT: ucs (3FH), len 45H (69), handle: 4C, printed CRC verifies), closes exactly on the RL boundary of its R13-R14 common object data with the common fields alone.
tables::ucs::decode reads Elevation, OrthographicViewType and the fields after them on every pre-R2007 release, R14 included, so it reads the record's handle bytes as an ortho view type and fails:
UCS ortho_view_type 29456 outside 0..=6
The R2000+ fields need the same release gate the spec gives them. No UCS record is in the R14 files of the local corpus.
Reproduce
cargo run --release --example spec_examples
Row 20.4.62 of tests/fixtures/spec-examples/r14-objects.tsv (#107).
Acceptance
On R13/R14 the decoder stops after Y-direction.
The §20.4.62.1 row closes, and its expect cell becomes closes.
Activity
test(fixtures): run the specification's own worked examples through t…
test(fixtures): run the specification's own worked examples through t…
test(fixtures): run the specification's own worked examples through t…
test(fixtures): run the specification's own worked examples through t…
fix(tables): a UCS record ends after its Y axis on R13/R14 (§20.4.62, #…