Jan Stary writes: > On Feb 26 09:54:18, anth...@cathet.us wrote: > > Jan Stary writes: > > > What do? I understand groff(1) is a legacy, > > > > I wouldn't call the groff package legacy. Using groff for manpages may be > > on the way out (as mandoc gets more feature-complete), but some people do > > use groff for other typesetting purposes. > > Please excuse my ignorance: what would be an example > of a serious typesetting done decidedly in (g)roff > these days?
Plenty of people still use troff instead of LaTeX for personal documents, letters, etc. I do it from time to time also. If you're interested, check out the groff mailing list. > Index: pkg/DESCR > =================================================================== > RCS file: /cvs/ports/textproc/groff/pkg/DESCR,v > retrieving revision 1.3 > diff -u -p -r1.3 DESCR > --- pkg/DESCR 4 Dec 2011 15:41:26 -0000 1.3 > +++ pkg/DESCR 26 Feb 2013 21:36:37 -0000 > @@ -6,3 +6,9 @@ The groff distribution includes: > * postprocessors for various output devices, including character > terminals, X terminals, PostScript, HTML and XHTML, and TeX DVI; > * and many utility programs. > + > +Some traditional groff companions are intentionally not pulled in > +as dependencies. For example, graphics/grap and graphics/ImageMagick > +that are needed by groff's eqn2graph, grap2graph and pic2graph > +are available as separated packages. Since we encourage people to install packages rather than compile ports themselves, it would make more sense to only list package names here, not full port paths.
