GXL2GV,GV2GXL(1)

✨ GXL2GV,GV2GXL — the GXL ⇄ GV converters ✨

okay bestie, listen up, this is gxl2gv and gv2gxl from the General Commands Manual section (section 1, iykyk), and they are literally your little graph-translation besties 💖

🌸 NAME 🌸

gxl2gv, gv2gxl — GXL-GV converters 🦋

---

✨ SYNOPSIS ✨

gxl2gv [ -gd?  ] [ -ooutfile ] [ files ]
gv2gxl [ -gd?  ] [ -ooutfile ] [ files ]

that's it. that's the whole vibe check. two binaries, same energy, opposite directions 💅

---

💜 DESCRIPTION 💜

okay so here's the tea 🍓: gxl2gv converts between graphs represented in GXL and in the GV language. like, it's a translator. a graph bilingual. a polyglot icon 👑

Now, unless you specify a conversion type using a flag, gxl2gv will deduce the type of conversion from the suffix of the input file. No cap. Here's how that reads:

• a .gv suffix ➡️ causes a conversion from GV to GXL
• a .gxl suffix ➡️ causes a conversion from GXL to GV

and if there's no suffix available (like, say, when the input is from a pipe, which is so valid of you), and no flags are used, then gxl2gv assumes the type of the input file from its executable name. so:

• gxl2gv converts from GXL to GV
• gv2gxl converts from GV to GXL

it literally reads its own name to figure out who it is. main character energy fr fr 💀

---

GXL supports a much richer graph model than GV does, and honestly? it's giving overachiever. gxl2gv will attempt to map GXL constructs into the analogous GV construct when this is possible 🫶. If not possible, the GXL information is stored as an attribute.

and the intention behind all of this, the dream, the goal ✨: applying gxl2gv|gv2gxl is supposed to be semantically equivalent to the identity operator. like, round trip and you're back where you started. the way that's iconic 😭

---

💅 OPTIONS 💅

the following options are supported, bestie, and you better believe every single one is here:

• -g — the command name and input file extensions are ignored; the input is taken as a GV file and a GXL file is generated 🌈
• -d — the command name and input file extensions are ignored; the input is taken as a GXL file and a GV file is generated 🌈
• -? — prints usage information and exits. she said "let me explain myself" and then dipped 👋
• -o outfile — if specified, the output will be written into the file outfile. Otherwise, output is written to standard out ⭐

---

🎀 OPERANDS 🎀

the following operand is supported:

• files — names of files containing 1 or more graphs in GXL or GV. If no files operand is specified, the standard input will be used 🧚

---

🔥 RETURN CODES 🔥

both gxl2gv and gv2gxl return 0 if there were no problems during conversion, and non-zero if any error occurred. zero means slay, non-zero means 😭

---

💀 BUGS 💀

okay, small yikes, but we have to be honest with you:

• gxl2gv will only convert in one direction even if given multiple files with varying suffixes. she picked a lane and she's staying in it 🙈
• the conversion can only handle one graph per GXL file
• there are some GXL constructs which gxl2gv cannot handle

no cap, these are real limitations, don't come for me, come for the code 💖

---

👑 AUTHORS 👑

• Krishnam Pericherla <kp@research.att.com>
• Emden R. Gansner <erg@research.att.com>

legends, honestly. we stan 🫶

---

🌈 SEE ALSO 🌈

dot(1), neato(1), twopi(1) — go read those too, they're the whole friend group 💜

---

and that's the page bestie!! this version is from the 20 December 2002 edition of the General Commands Manual, so yeah, she's vintage, she's an elder icon, and she still hits 💅✨ bye!! 🎀