Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 1 Nov 2026. What's built · Install 0.2.0
jadpo
Reference: Standard library

Standard types

VideoCodec

On this page

A video codec as the W3C WebCodecs Codec Registry names it (RFC 6381's form): avc1.42001E, vp09.00.10.08.

Media and visual; not ordered; since Jadpo 0.1.0.

Make one

Build one from its text, VideoCodec("avc1.42001E"), which checks it: text that isn't one breaks format.

text.parse(raw, as: VideoCodec) reads one from its text; text that isn't one at all fails malformed, such as h264, avc1 or AVC1.42001E.

Text, JSON and storage

text.from writes its canonical text, the one form text.parse reads back. JSON sends its canonical text as a string.

Text JSON
avc1.42001E "avc1.42001E"
hvc1.1.6.L93.B0 "hvc1.1.6.L93.B0"
av01.0.04M.08 "av01.0.04M.08"
vp09.00.10.08 "vp09.00.10.08"
vp8 "vp8"

It is stored in one column named for the field, of type text. av01.0.04M.08 is stored as 'av01.0.04M.08'.

Shown to people

text.format(value, locale:) shows it to people in their locale.

With locale: Locale.en_gb:

Value Shown
avc1.42001E avc1.42001E
hvc1.1.6.L93.B0 hvc1.1.6.L93.B0
av01.0.04M.08 av01.0.04M.08
vp09.00.10.08 vp09.00.10.08
vp8 vp8

Operations

It has the contract's own operations: text.parse, text.from, text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.

Markdown for agents: /docs/types/type-video-codec.md.Built from Jadpo main at e00e61f.