BLO

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

SANKOM Audytor Block Library.

At a glance

How much Poka reads

B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-16: read parsers/poka-blo/src/lib.rs in full and the samples test. Covers the legacy AUDBLOKI container (3.20, 3.50, 3.60, 3.80) and the PWFILEVERINF wrapper (CO___BLO, STKANBLO). The corpus the tests expect (25 libraries, at least 15) is not in poka-samples or the crate, so nothing here was proven against a real file; medium confidence.

What Poka does not read

• Block geometry and symbol drawing
• Block records (layout not decoded; names come from a printable-text scan, not a record walk)
• Block names are a heuristic: names under 3 characters are missed, duplicates are merged, and stray text in the records can appear as a name
• At most 200 names are listed
• Header counters shown raw, with no meaning attached
• Per-block properties such as dimensions, connection points or categories
• Wrapper header fields beyond data kind and version

Background

Two container families share the extension. The legacy one starts with AUDBLOKI and a format version; the newer SANKOM wrapper starts with PWFILEVERINF and a data kind, the same container as .ekd. The block records are proprietary and are not decoded. Poka reads both containers and shows the library version and the printable text runs it finds in the block data (a heuristic scan, capped at 200 and labelled as found by text scan).

Versions

Sources

• parsers/poka-blo/src/lib.rs