| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
top-level DIV is used with only an H1 or H2 as the section header. This
makes manuals much more readable in lynx, less complicated, and
relegates left-margin widths to example.style.css.
|
|
|
|
| |
enough.
|
|
|
|
| |
Remove superfluous language in output-mode short description.
|
| |
|
|
|
|
|
| |
the first step to having a simpler ref-counted system for "data"
associated with a node.
|
| |
|
|
|
|
| |
Merge other TODO regarding `It' and paragraphs.
|
|
|
|
| |
study to see exactly what's legal and what's not.
|
|
|
|
| |
compact mode.
|
|
|
|
|
|
|
|
|
|
|
| |
`Bl' (before any `It' have been invoked). Next, have the existence of
either macro raise a warning, as it's technically not legal according to
mdoc.7.
Second, delete any `Pp' as the first element of a `Bl' (i.e., before an
`It') ONLY when -compact has not been specified. This matches with the
latest version of groff. This deletion happens prior to the above
check, so double-warnings will not be issued.
|
|
|
|
|
| |
printing as the first or last child of an `Ss' or `Sh': this is now
ensured within the validator.
|
|
|
|
|
|
|
| |
Remove `Pp' or `Lp' if it is the FIRST or LAST child of an `Sh' or `Sh' body.
Make "skipping paragraph" be an error, not a warning, as information (an
invoked macro) is ignored.
|
| |
|
|
|
|
|
|
|
| |
paragraph breaking in CSS).
Use -man's handling of `sp' and `br', which accomodates for scaling
widths (-mdoc wasn't).
|
|
|
|
| |
have to do this manually).
|
| |
|
|
|
|
| |
Make `Dl' and `D1' both use BLOCKQUOTE instead of DIVs.
|
|
|
|
|
|
|
|
| |
be handled in CSS.
Clarified "lit" tag (will be the subject of future clarification).
Removed CSS2 note in mandoc.1, which is no longer the case.
|
| |
|
|
|
|
|
| |
OL, and UL. Issue raised by Will Backman, solution proposed by
schwarze@.
|
|
|
|
|
|
|
|
|
| |
behave as if the whole code were wrapped in .Bk/.Ek,
i.e. keeping input lines together on output lines.
This is compatible with new groff behaviour and deviates
from historical groff.
Tweaked version of a patch sent by kristaps@ on July 16, 2010.
ok kristaps@ jmc@ sobrado@ millert@
|
|
|
|
|
|
| |
For now, use the simplest conceivable approach, like groff does:
Just a fixed, ugly input stack limit.
"check it in" kristaps@
|
| |
|
|
|
|
|
|
|
|
|
| |
`Brq') to have zero arguments without warning. This makes sense because
the multi-line quote macros (`Oo/Oc' etc.) allow zero children anyway.
Furthermore, the documentation doesn't state that they're required to
have children.
Originally reported by Alex Kozlov, thanks!
|
|
|
|
|
|
|
|
| |
me package, aren't recognised by "groff -mandoc" so we don't need to do
so either. Discussed on tech@ with schwarze@.
While at it, remove references to `b' in man.7. As far as I know, this
was never supported anyway.
|
|
|
|
|
|
|
|
|
|
|
| |
changes these last months (less tbl). There are still some issues that
require thought, but this extends beyond synchronisation.
This WILL NOT be pushed to the main site; it's merely a logical tag so
that there's a common fall-back in future changes.
Note that the TODO file is NOT up to date. This is ok since the tag is
purely internal.
|
|
|
|
| |
except for the tbl one which will be the focus of later study.
|
|
|
|
|
|
|
|
|
|
| |
for the new libroff macros, the new libman macros, and for the sake of
general clarity.
Note that `ft' documentation is NOT included, as I've kept it in -man:
it's highly confusing to have it in roff.7 when it's not implemented for
both -man and -mdoc, as at least in theory, roff.7 should include only
macros recognised by BOTH formats.
|
| |
|
|
|
|
|
| |
schwarze@, but without the -T[x]html handling, which structurally does
not work. Also add man.7 documentation (not in original patch).
|
| |
|
| |
|
|
|
|
|
| |
Merge patch by schwarze@ consolidating RB, BR, etc. into one function.
man_html.c already does this.
|
|
|
|
|
|
| |
Make non-uppercase warning only occur once.
Make scope-open-on-error warning only occur once.
|
| |
|
|
|
|
| |
tested patch by schwarze@.
|
|
|
|
| |
tested patch by schwarze@.
|
|
|
|
|
|
|
|
|
|
| |
returning empty strings in roff_getstrn() instead of NULL. This caused
maddeningly irregular segfaults in the pod2man preamble for `de IX'.
But only on DEC alpha.
Also integrate the kinda-probably-safe assertion relaxation in term.c,
field-tested by schwarze@. This allows ALL [unpreprocessed] base and
xenocara manuals for all BSD systems to run without segfault.
|
|
|
|
| |
ending of scopes and drop stray scope-endings.
|
|
|
|
| |
which are now accomodated for the new libroff modifications.
|
| |
|
|
|
|
| |
NOARGV warnings. From patch by schwarze@.
|
| |
|
|
|
|
|
|
|
| |
making sure output doesn't add a superfluous newline with the nested displays.
Also add a COMPATIBILITY note.
Rename a macro (DATESIZ) to be in line with OpenBSD (DATESIZE).
|
|
|
|
|
|
|
|
| |
we can for example skip rendering on FATAL parsing errors,
and globally (exit_status), such that we know what to return.
Without this, following files produced no rendered output
once a single file suffered from a FATAL error.
Bug reported by kristaps@, fix by me.
|
|
|
|
|
|
|
|
| |
primarily adds a roff_userdef() function for parsing new defines and
modifies the look-up procedure.
NOTE: there is a bug hidden away in this update that causes an infinite
loop in some pages. The cause is for the moment unknown.
|
| |
|
|
|
|
| |
schwarze@ and joerg@ for his comments!
|
|
|
|
|
| |
behaviour only happens if `Dt' isn't specified, which can be exhibited
by running mandoc -mdoc on a man manual.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
being inherited during the parse sequence, making pset() meaningless.
Make sure that the mdoc/man curp pointer is set for each parse from a
persistent object.
This flushes out an obscure error where `man' pages called with `mdoc'
will parse and segfault due to a missing title. Never happened earlier
because `mdoc' pages were guaranteed to have a prologue. Fix this
later.
Also document the new main.c functions. Please make sure these sort of
things are documented! Throw in some whitespace to make things a bit
more readable.
|