DUCKTYPE(1)

✨ DUCKTYPE(1) ✨

okay bestie, welcome to the ducktype(1) page from the General Commands Manual πŸ’… this is the whole vibe, let's get into it


🌸 NAME 🌸

ducktype β€” convert Mallard Ducktype to Mallard XML


πŸ¦‹ SYNOPSIS πŸ¦‹

ducktype [--output=OUTPUT|-o OUTPUT] INPUT ...

πŸ’– DESCRIPTION πŸ’–

so the ducktype(1) tool does one thing and it does it slay: it converts Mallard Ducktype β€” which is a lightweight markup language for topic-oriented help β€” into Mallard XML. that's it. that's the whole job. iconic behavior honestly πŸŽ€


✨ OPTIONS ✨

  • --output=OUTPUT, -o OUTPUT β€” sets the output file or directory name. if you don't pass this, the default is lowkey smart: it takes each input pathname, yeets any .duck suffix off it, and appends .page. 🫢 also, if there's exactly one input file, then OUTPUT is allowed to be a filename. but if there's more than one input file, OUTPUT must be a directory name, and the files get created in that directory instead of sitting in the same directory as the input. periodt.

πŸ‘‘ SEE ALSO πŸ‘‘

  • yelp-build(1), yelp-check(1), yelp-new(1) (only if they had man pages, which at the time of writing they do not β€” so, like, manifesting? πŸ™ˆ)
  • http://projectmallard.org/

πŸ’œ AUTHOR πŸ’œ

Ducktype was written by Shaun McCance. this manual page was written by Simon McVittie for the Debian project (but it may be used by others).


okay that's the whole page, no cap 🧚✨ this was the DUCKTYPE(1) manual page, dated 2018-02-06 β€” tysm for reading, mwah, go convert something πŸ’–πŸŒΈπŸŽ€

πŸ“¦ where this page comes from