gromox-abktconv(8)

okay bestie, welcome to gromox-abktconv(8) from the Gromox admin reference — it’s the utility for converting between ABKT and JSON, and it’s lowkey iconic for moving between MS-OXOABKT data streams and a textual representation. ✨

🎀 Name 🎀

gromox-abktconv — utility for converting between ABKT and JSON. That’s the whole vibe: ABKT ⇄ JSON, no cap. 💅

🦋 Synopsis 🦋

gromox-abktconv {-b|-j} [-gw?] [-c cpid]

🌸 Description 🌸

gromox-abktconv can be used to convert between data streams as specified in MS-OXOABKT and a textual representation. It reads and writes to standard input and output, respectively. So yeah: stdin in, stdout out, main character energy only. 🫶

✨ Options ✨

• -b — produce type-1 ABKT from JSON. That’s the “JSON goes in, type-1 ABKT comes out” direction. 🔥
• -c cpid — when converting to ABKT (-b), convert strings to the given codepage and emit them as 8-bit strings. Codepage girlies rise 💅
• -g — when converting to ABKT (-b), emit extraneous gaps in the data stream to mimic what Exchange would do. Without -g, the ABKT stream will have no unnecessary gaps. So -g is the “match Exchange’s little quirks” button, fr fr. 🎀
• -j — produce JSON from ABKT type-1 or type-2. Both types are invited to the party. ✨
• -w — when converting to ABKT (-b), emit strings in UTF-16 form. This is the default. So if you don’t say anything else, UTF-16 is the vibe. 🌈
• -? — display option summary. Tiny help moment, very demure. 🫶

📚 Normative references 📚

• MS-OXOABKT: Address Book User Interface Templates Protocol
• oxoabkt.rst: Type-2 ABKT template protocol

👀 See also 👀

gromox(7), gromox-abktpull(8gx)

source/version: Gromox, page gromox-abktconv(8) — the original footer didn’t give a date, so I’m not inventing one, periodt 💅💖