diff options
author | 2010-12-28 10:51:03 +0000 | |
---|---|---|
committer | 2010-12-28 10:51:03 +0000 | |
commit | 79e37cdd7920997b204cf36aa45b387db8bc02ff (patch) | |
tree | 00a06351a5961ddbe5c00fa54b7f5ceaafbddf73 /mandoc.1 | |
parent | a629f7c1e6958d7f3fd35692d5c0df8697a743a0 (diff) | |
download | mandoc-79e37cdd7920997b204cf36aa45b387db8bc02ff.tar.gz mandoc-79e37cdd7920997b204cf36aa45b387db8bc02ff.tar.zst mandoc-79e37cdd7920997b204cf36aa45b387db8bc02ff.zip |
Initial tbl framework. Parse point is in libroff, which keeps a
reference to a current tbl parse and routes ALL text into the tbl parse
after stripping reserved words and making block-level pre-processing
(e.g., `ig'). This is consistent with an analysis of embedded `TS/TE'
in manuals with sprinkled -mdoc, roff, and -man macros.
Fact of a parse is exposed to main.c by a return value (ROFF_TBL), which
will trigger main.c to add a foreign parsed body to the -mdoc or -man
parse stream. This interface isn't in yet, but will follow the
parse-text functions in both libraries. I put this login in main.c
because I don't want libroff calling directly into libmdoc or libman.
As a consequence, a parsed row can be pushed directly into any -mdoc or
-man context (put a `Bd -literal -offset indent' into a `TE/TS' block to
see why this is necessary). It will then absorb formatting cues in the
front-ends.
A note on naming. I decided on libroff.h instead of tbl.h because this
is purely within the roff layer. Separate tbl implementations will
need, then, to interface with libroff. This is "how it should be"
because tbl is tightly linked with roff in terms of `ds' and other
formatting macros, as well as, of course, special characters and other
roffisms.
Diffstat (limited to 'mandoc.1')
0 files changed, 0 insertions, 0 deletions