bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #64018] [man, mdoc] decide on a common base paragraph indentation


From: G. Branden Robinson
Subject: [bug #64018] [man, mdoc] decide on a common base paragraph indentation
Date: Thu, 3 Aug 2023 17:56:33 -0400 (EDT)

Follow-up Comment #13, bug #64018 (project groff):

[comment #11 comment #11:]
> The codebase is the “last” nroff I could use under the Caldera licence,
i.e. that was shipped with a BSD covered by these. The macropackages are a
conglomerate from the TUHS archives and pre-mdocml OpenBSD’s,

Is there anyplace these can currently be obtained?  I'm curious to see if this
is the same place from which the modernized (just for build/portability
purposes) [https://github.com/n-t-roff/DWB3.3/ DWB 3.3 troff] originated.

> but I invested heavily into them to get them to mostly work (modulo missing
pieces). I also added a hack (with pre‑ and postprocessor) for 8-bit/UTF-8
support, but that’s nowhere near mature.

> I only ported nroff, not troff (since nobody has the hardware it drives any
more),

That wouldn't be DWB 3.3 troff, then, because people do still have PostScript
devices.

https://github.com/n-t-roff/DWB3.3/tree/master/postscript/

[...]
> With the exception of terminfo(5)¹ I use this exclusively to build
catmanpages, but I use groff with custom fonts to build PDF manpages for the
website for the “portable subprojects” like mksh.

I hope that's a labor of love, because it sounds like punishment to me. 
(Which is no doubt what some people think of some of _my_ avocations...)

> ① “Too many text block diversions”, which probably means this cannot
be rendered with tbl(1) at all and needs GNU tbl, if I understand this
correctly.

Yes.

_tbl_(1) from groff 1.23.0:


  GNU tbl enhancements
    In addition to extensions noted above, GNU tbl removes constraints
    endured by users of AT&T tbl.

    • Region options can be specified in any lettercase.

    • There is no limit on the number of columns in a table, regardless
      of their classification, nor any limit on the number of text
      blocks.

    • All table rows are considered when deciding column widths, not
      just those occurring in the first 200 input lines of a region.
      Similarly, table continuation (.T&) tokens are recognized outside
      a region’s first 200 input lines.

    • Numeric and alphabetic entries may appear in the same column.

    • Numeric and alphabetic entries may span horizontally.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64018>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]