mandoc - UNIX manpage compiler toolset

	Commit message (Collapse)	Author	Age	Files	Lines
*	Lint-checks over mandoc-db.c.	Kristaps Dzonsons	2011-04-05	1	-18/+14
\|
*	Use a little more horsepower in parsing out NAME sections from -man	Kristaps Dzonsons	2011-04-05	1	-16/+56
\| \| \| \|	manuals. This covers the majority case.
*	Fix type- and NULL-check to be correct node (last, not child). Prevents	Kristaps Dzonsons	2011-04-05	1	-1/+1
\| \| \| \|	segfault in NetBSD.
*	Add mandoc-db.c checking for utility-name in NAME section of -man	Kristaps Dzonsons	2011-04-05	1	-3/+77
\| \| \| \|	documents.
*	Have `Fd' detection in mandoc-db also look for local includes (i.e.,	Kristaps Dzonsons	2011-04-04	1	-2/+2
\| \| \| \|	those that are quoted and not angular-bracketed).
*	Add manual page for mandoc-db (mostly to document the file format of	Kristaps Dzonsons	2011-04-04	1	-16/+17
\| \| \| \| \|	the generated index and keyword databases). Add some documentation within mandoc-db.c.
*	Have mandoc-db create an recno-addressed index of files alongside the	Kristaps Dzonsons	2011-04-03	1	-59/+83
\| \| \| \|	keyword database, which references the index of hard-coding files.
*	Have mandoc-db use config.h for strlcat(). Then create the btree	Kristaps Dzonsons	2011-04-03	1	-29/+37
\| \| \| \| \| \|	database from a directory, instead of a path. This is because it'll also output an index of files to that same directory. Add documentation to the local variable names, too.
*	Add an initial keyword-indexer as an alternative front-end to libmandoc.a.	Kristaps Dzonsons	2011-04-02	1	-0/+636
	This will be used during BSDCan-2011, paired with a web front-end, as a demonstrandum of semantic annotations (mdoc) versus those of man. This isn't linked to the build in any way but for cleaning created files. This code has been heavily tested under valgrind and is known to work on GNU/Linux (needs -ldb library), all BSDs, and Mac OSX. Please don't repost this, for the time being, as I don't want to spoil the fun for the conference. This utility is still constantly under development (e.g., it will also generate a recno database of filenames and `Nd' output so that paths needn't be hard-coded) but is mature enough to warrant being checked in.