mandoc - UNIX manpage compiler toolset

	Commit message (Collapse)	Author	Age	Files	Lines
*	Yet another round of improvements to manual font selection.	Ingo Schwarze	2018-12-16	4	-18/+31
\| \| \| \| \| \| \| \| \|	Unify handling of \f and .ft. Support \f4 (bold+italic). Support ".ft BI" and ".ft CW" for terminal output. Support the .ft request in HTML output. Reject the bogus fonts \f(C1, \f(C2, \f(C3, and \f(CP. In regress.pl, only strip leading whitespace in math mode.
*	Several improvements to escape sequence handling.	Ingo Schwarze	2018-12-15	15	-38/+218
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Add the missing special character \_ (underscore). * Partial implementations of \a (leader character) and \E (uninterpreted escape character). * Parse and ignore \r (reverse line feed). * Add a WARNING message about undefined escape sequences. * Add an UNSUPP message about unsupported escape sequences. * Mark \! and \? (transparent throughput) and \O (suppress output) as unsupported. * Treat the various variants of zero-width spaces as one-byte escape sequences rather than as special characters, to avoid defining bogus forms with square brackets. * For special characters with one-byte names, do not define bogus forms with square brackets, except for \[-], which is valid. * In the form with square brackets, undefined special characters do not fall back to printing the name verbatim, not even for one-byte names. * Starting a special character name with a blank is an error. * Undefined escape sequences never abort formatting of the input string, not even in HTML output mode. * Document the newly handled escapes, and a few that were missing. * Regression tests for most of the above.
*	If man(7) next-line scope is open and the line ends with \c,	Ingo Schwarze	2018-08-25	2	-3/+29
\| \| \| \|	the scope remains open. Needed for example for groff_man(7).
*	catch up with ASCII renderings in chars.c rev. 1.72	Ingo Schwarze	2017-08-23	2	-10/+14
\|
*	Messages of the -Wbase level now print STYLE:. Since this	Ingo Schwarze	2017-07-04	34	-63/+63
\| \| \| \| \| \| \| \|	causes horrible churn anyway, profit of the opportunity to stop excessive testing, such that this is hopefully the last instance of such churn. Consistently use OpenBSD RCS tags, blank .Os, blank fourth .TH argument, and Mdocdate like everywhere else. Use -Ios=OpenBSD for platform-independent predictable output.
*	cope with changes in BASE messages	Ingo Schwarze	2017-06-25	5	-10/+15
\|
*	style message about missing RCS ids; inspired by mdoclint	Ingo Schwarze	2017-06-17	5	-0/+5
\|
*	correct handling of blank lines after \c	Ingo Schwarze	2017-06-17	4	-0/+25
\|
*	implement so-called absolute horizontal motion: \h'\|...',	Ingo Schwarze	2017-06-14	3	-1/+4
\| \| \| \|	used for example by zoem(1)
*	let \l use the right fill character	Ingo Schwarze	2017-06-14	4	-2/+42
\|
*	improve rounding rules for scaling units	Ingo Schwarze	2017-06-14	3	-1/+4
\| \| \| \|	in horizontal orientation in the terminal formatter
*	implement the roff(7) \p (break output line) escape sequence	Ingo Schwarze	2017-06-14	3	-1/+35
\|
*	Style message about legacy man(7) date format in mdoc(7) documents	Ingo Schwarze	2017-06-11	4	-0/+4
\| \| \| \| \|	and operating system dependent messages about missing or unexpected Mdocdate; inspired by mdoclint(1).
*	Minimal implementation of the \h (horizontal motion) escape sequence.	Ingo Schwarze	2017-06-01	1	-2/+2
\| \| \| \|	Good enough to cope with the average DocBook insanity.
*	Many people have been complaining for a long time that ``...'' looks	Ingo Schwarze	2017-02-17	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	ugly in -Tascii output. For that reason, bentley@ submitted patches to render "..." instead to groff in November 2014 (yes, more than two years ago). Carsten Kunze yesterday merged them for the upcoming groff-1.22.4 release. Yay! Consequently, do the same in mandoc: Render \(Lq and \(Rq (which are used for .Do, .Dq, .Lb, and .St) as '"' in -Tascii output. All other output modes including -Tutf8 remain unchanged.
*	Finally port the OpenBSD regression suite.	Ingo Schwarze	2017-02-08	31	-0/+488
	Both kristaps@ and wiz@ repeated asked for this, literally for years.