[Groff] Grohtml not building?

The CVS isn't building grohtml. I deleted src/devices/grohtml and updated, no difference. Here's a listing of the directory (after making), if that helps at all: % l src/devices/grohtml/ CVS/grohtml.n html-text.cpp output.cpp post-html.o Makefile.dephtml-table.cpp h

[Groff] tbl: text blocks vs. centering

tand that, but it obviously isn't. The tbl(1) manpage says that text in cells is vertically centered unless you use the T or D specifiers. That doesn't seem to be the case here either. Can anyone shed some light here? -- Larry Kollar k o l l a r @ a l l t e l .

Re: [Groff] tbl: text blocks vs. centering

Werner LEMBERG wrote... >> The text in the first column should be centered, but is left- >> justified. > > The crucial part of explaining the behaviour is this sentence from > tbl.man: > > The default length of a text block is given by LC/(N+1), where `L' > is the current line length, `C' t

[Groff] mm patch

ne is not indented). ChangeLog entry: 2006-09-10 Larry Kollar<[EMAIL PROTECTED]> * contrib/mm/m.tmac: Modified the 'nP' macro to conform to Bell System Practices style when the 'BSP' register is defined. Modified the 'H' macro

[Groff] Re: mm patch

If you haven't committed the mm patch I sent in, don't. I've uncovered a couple of bugs that need to be fixed. I'll resubmit later today or tomorrow morning. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Rev

Re: [Groff] empty line before .TH in man page produces sometimesanempty page

> ABSOLUTELY NO LINES, other than genuine troff/groff comment lines > should appear in a man page file before the .TH line. My first thought upon reading Bernd's report was "put an .ig XX at the end of tmac.man, and turn it off in .TH" but that would break the zillions of manpages out there that

Re: [Groff] OpenDocument to troff converter

Gunnar Ritter wrote: > I announce the availability of an import filter to convert > OpenDocument files to troff input. I have released it as > part of my Heirloom Documentation Tools package, but since > it is not actually specific to a troff variant, it may be > useful with groff as well. This

Re: [Groff] groff v. TeX

from FrameMaker. It takes one or two minutes to produce PDFs for a 4-volume set of documents running over 750 pages, a job that literally took an entire afternoon on my old computer running Frame & would still need nearly an hour to complete on the new computer. -- Larry Kollar k o

[Groff] Pic macros for flow charts?

Does anyone have any pic code that would make drawing flow charts a little smoother? I've been presented with a flow chart (done in Visio) and think it would be easier to recode it in pic than it would to get a decent EPS from Visio. -- Larry ___ G

[Groff] pic - drawing a line back to the beginning

I got busy learning pic today, since there was only a tantalizing reference to a utility that doesn't seem to exist anymore. :-) Turns out that pic is a fairly simple way to produce flowcharts... mostly. I was surprised at how quickly I got something that just needed some tweaking, not havi

Re: [Groff] Pic macros for flow charts?

aphic editor that uses pic as a file format: http://se.uwaterloo.ca/~dberry/wd-pic.html Or go straight to the tarball: http://se.uwaterloo.ca/~dberry/COURSES/ full.year.lab/wd-pic/wd-pic.tar.Z -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Rev

Re: [Groff] RTF

r OSX or 'Doze... which isn't such a limitation, seeing that you need one or the other to run Weird anyway. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Revival" http://unixtext.org/

Re: [Groff] http://unixtext.org/ (broken links)

(the second edition) soon; I've had some issues keeping me from starting sooner, and October is a $&@#! month for free time anyway. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: &quo

Re: [Groff] pic - drawing a line back to the beginning

Ted Harding wrote: If you have a designation of a point (such as "1st box .w") then you can get its x and y coordinates using ".x" and ".y". ... line up ( 1st box .w .y - last box .w .y ); arrow to 1st box .w; That worked - thanks much! -- Larry Kollar

Re: [Groff] Using pic/groff/gs to produce gif/jpeg

t temporarily, change "groff" in the above pipeline to "groff -P-pletter" -- you can also change it permanently by editing the .../groff//font/devps/DESC file to contain the line "papersize letter" and removing any other "papersize" line in the file.

Re: [Groff] multiple EPS images placed on a page

several rows down on a standard page, although it is less likely that files will be missed or duplicated. Huh? Oh, PSPIC. I'd use tbl for this; Werner suggested hdtbl, which would probably work as well. I should probably start migrating my work stuff toward hdtbl. Eventually. :-) --

[Groff] grohtml hanging on PSPIC

Putting a PS file before the '.TL' in a -ms file causes grohtml to hang at the beginning of generating HTML. This used to work, but I think it broke between 1.19.1 and 1.19.2. Here's an example file: .\" begin \& .sp 2i .tm output = \*[.T] .PSPIC logo.eps 1i .TL .ie '\*[.T]'html' .HTML

Re: [Groff] grohtml hanging on PSPIC

Gaius Mulley wrote: > > Putting a PS file before the '.TL' in a -ms file causes grohtml to hang at the > > beginning of generating HTML. This used to work, but I think it broke > > between 1.19.1 and 1.19.2. > > > > $ awk -f htbl.awk test.ms | groff -ms -mtrace -mwww -Thtml -P-n -P-r - >

[Groff] grohtml - "too many open files"

This is partly groff, and partly a utilities issue. I'm well along the way to getting grohtml output to work with OmniHelp, an LGPL'ed "HTML help" viewer [http://www.omsys.com/dcl/omnihelp.htm]. I have one last snag to work out, which is related to a large manual containing hundreds of commands

[Groff] Modifying hyphenation rules?

The documentation I maintain references literally hundreds of MIB variables, with names like "pktcMtaDevRealmTable" (and that's one of the shorter ones). Groff tried to make educated guesses at hyphenating these things when they hit the end of the line (as they do far too often), but often break

Re: [Groff] Re: Simplifying groff documentation

> ... I agree with your assessment of *roff and TeX (I used both > extensively). However, I did write a 10 page technical > document (34 with the appendices that simply include the > files) in DocBook-XML. I have turned away in disgust and > never looked back. I'll use Zvezdan's example here as

Re: [Groff] Re: Simplifying groff documentation

Eric S. Raymond wrote: I would say a program that claims to read manual pages is broken enough to be irrelevant if it cannot at least handle .br .fi .nf .sp .ig .in .ti Doclifter might fail that test. It ignores .in and .ti, because I don't know any way to extract structural informat

Re: [Groff] The case against the case against .EX/.EE & .DS/.DE

> We definitely need a good guide for writing man pages, based on our > discussion -- something like a man-to-html.howto. This guide should > contain (as an appendix) those macro definitions which a man writer > can then simply copy and paste. That was one of the thrusts of my "Writing Effective

Re: [Groff] Mom/Mac OSX strangeness

> In the 1.5 version of the mom macros, I added some definitions to > facilitate the drawing of common graphical objects (rules, boxes, > ellipses). All of them use the \D escape. > > ... Recently, a user wrote me saying the macros *don't* work on his Mac > box (OSX) with groff 1.19.1. That's b

Re: [Groff] ESR in manpages versus the WEB

code in them. Otherwise, the job of doclifter quickly becomes as impossible as that of grohtml. I agree with this. It's always best to minimize or eliminate raw *roff requests, and not just in manpages. Repeated use of raw requests probably indicate the need for a macro. -- Larry Kollar k

Re: [Groff] doclifter on groffer.man

e it to the interchange format. I hope that helps to clear up any misunderstandings. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Revival" http://unixtext.org/ ___ Groff mailing list

Re: [Groff] Re: Simplifying groff documentation

I've asked this question before on XML fora and have not heard a satisfactory answer. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Revival" http://unixtext.org/ ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Status of the portability work, and plans for the future

vocal. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Revival" http://unixtext.org/ ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Status of the portability work, and plans for the future

converters, as we did until now. Actually, this discussion *is* leading toward our mutual goal of better accessibility. We have to take into account both the strengths and limitations of the manpage format along the way. -- Larry Kollar k o l l a r @ a l

Re: [Groff] Progress report on the portability audit -- and what to do about URLs?

ter, already do this. Urk. Sounds like a step backwards. I need a quick decision about this, because it will affect the set of cleanup patches I turn in. Of the feasible choices, I would pick (2). -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Proce

Re: [Groff] Choosing a portability target

to their writers whether they want to support Elder Troff. I don't have an opinion either way on Target 3. Personally, I think Target 2 is adequate. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text Processing: "UTP Revival" http://unixtext.org/ _

Re: [Groff] Choosing a portability target

insert conditionals in your master file as well. Remember that the current version of -man gives you a lot of control over the output, if you need to mimic a particular style for your Windows documentation. -- Larry Kollar k o l l a r @ a l l t e l . n e t Unix Text

Re: [Groff] How to do Multipage tables?

> According to page 6 of the document "tbl - A program to Format Tables" > by M.E. Lesk, tbl is supposed to handle:- > > .TS H > page heading text > .TH > > How do I get this to work? I keep getting:- > > ...:2: unrecognised format 'p' > ...:2: giving up on this table I was about to ask you fo

Re: [Groff] tbl problems in man

Eric S. Raymond wrote: >>> The only problem with using w is that the number that needs to go to >>> go next to it is brittle -- it may break if the table indent >>> changes, or if the the point size changes, or if the margins change. >> >> I fully agree. It can make such man pages ugly to read.

Re: [idea] troff -Troff

I’m a little late to the party, but I’ve read Alex’s original post over several times, and I have to wonder if everyone is over-thinking this. > On Feb 16, 2024, at 10:21 AM, Alejandro Colomar wrote: > > Hi Branden! > > I've been thinking about a suggestion I've done in the past. I wanted a >

Re: Macro package loading best practices

> Dave Kemper wrote: > > On 2/22/24, G. Branden Robinson wrote: >> I've come to think that a set of "best practice" for *roff document >> composition is to: >> >> A. Load your desired full-service macro package (if any) on the command >>line with `-m`. >> B. Load any auxiliary macro pac

Re: Kemper notectomy spreads, thousands of bytes saved

> On Feb 26, 2024, at 12:13 AM, G. Branden Robinson > wrote: > > Maybe Dave got it written up in the Journal of the American Documenter's > Association? ;-) > > https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=9b6c25510bdb54b4f7f9abbfaf6d136c65202d99 Bravo to Dave! — Larry

Re: [Groff] adding non-native font directories [Was: fontconfig]

Having “.fam OCR” fail doesn’t surprise me, because it would expect fonts OCRR, OCRI, OCRB, and OCRBI. But “.ft OCRAExtended” should have worked. Has anyone else successfully used site-font? I admit that I’ve always dumped custom fonts into the regular fonts directory. — Larry > On Mar 7, 2015

Re: [Groff] OT: PubCSS: Library of CSS and HTML for Academic PDF and HTML.

> Ralph Corderoy wrote: > > Thought this might be of interest to some of the list, despite involving > XML! > >https://github.com/thomaspark/pubcss/#readme > >PubCSS is a library of CSS stylesheets and HTML templates for formatting >academic publications for print and the web. > >

Re: [Groff] Lack of professionalism ....

> Tadziu Hoffmann wrote: > >> [...] that this is yet another instance of ungainly galloping >> gnus departing from Unix's original path of simplicity and >> transparency. > > Not really. Unix nroff had an option to create a "compacted" > version of a macro package, which was used because the c

Re: [Groff] groff ms: Is there an order to setting PS and VS versus PO and LL

(Ted Harding) wrote: > The ms macros have a somewhat deeply hidden mechanism of > storing the existing values of page-offset, line-length > and the like which can cause the kind of effect that Dorai > observes. > > If I intend a non-default page offset (e.g. 0.75i) to be in > force from the ver

Re: [Groff] Typesetting Markup Language (TML) - a Superset of Groff

> Steffen Nurpmeso wrote: > >> Or plain SGML that i think could use > like/. I think plain SGML is still an interesting language, much >> better than what XML made of it. Aha, I was trying to remember that in SGML. XML explicitly removed all the shortcuts, and introduced the concept of “well-

Re: [Groff] Typesetting Markup Language (TML) - a Superset of Groff

> Steve Izma wrote: > > Larry Kollar wrote: >> Subject: Re: [Groff] Typesetting Markup Language (TML) - a Superset of Groff >> >> ... Markdown, and most XML-based systems, deliberately >> kick the formatting can down the road so you can focus on your content.

Re: [Groff] pdfmark XN help

> Anton Shterenlikht wrote: > > I discovered pdfmark macro today. > I like it, and would like to use it's > facilities for hyperlinking and automatic > table of contents. > > However, pdfmark.pdf included in groff-1.22.2 > stops just at this point. > Section 3.1.1.1. "The XN Macro" is empty, >

Re: [Groff] bad QE in -ms

> Doug McIlroy wrote: > > The -ms macro QE typically draws a misleading diagnostic, "unbalanced QE". > This breaks old documents that expect QP-QE (quoted paragraph) to narrow > the text and then restore it. The groff QE does not restore. > > In fact, QE is aliased to RE, which means it will ca

Re: [Groff] bad QE in -ms

> Carsten Kunze wrote: > > Doug McIlroy wrote: >> Bad case I: [...] > > It neither works in groff nor in heirloom roff as specified (in original -ms > specification). > > I suggest to make .QS, .QE, .QP work as specified for traditional -ms without > any warnings. Then there may be some re

Re: [Groff] groff performance in respect to hardware platform

> Steve Izma wrote: > > I'm wondering how CPU configurations affect groff processing > speed. On a 2007 MacBook Pro, groff would produce a 900-page manual with a few graphics in 2-3 minutes. That was two groff runs to get cross-refs right, including index generation, followed by a ps2pdf run.

Re: [Groff] .if !dTS - GNU extension?

I’ve looked through this thread and Ingo’s presentation, and several things stand out: * I guess one of the primary issues here is that Groff is GPL, and a BSD distribution wants BSD licenses. That’s valid, if you’re willing to live with the corner-cases. Then again, using something like XHTML

Re: [Groff] Still No Luck Accessing Characters From Zapf Dingbats (Or Any Other Strange Font)

> On May 8, 2016, at 6:27 PM, Henry McGilton > wrote: > > So I am on El Capitan, and I am using the groff which comes installed > with El Capitan, GNU groff version 1.19.2 > > Invoking groff as suggested by Werner: > > groff -k -Tps foo.tr > foo.ps > > groff: invalid option -- k I’ve just

[Groff] Tines 1.10, an outliner/planner/organizer/notebook

At the end of last year, I forked the moribund console-based hnb outliner code and launched Tines. I’ve mostly focused on improving its planner capabilities… and why am I nattering about this on the Groff list? Version 1.10 has an option to export to groff -ms (or Markdown) through XSLT. You ha

Re: [Groff] Converting basic units to inches in PostScript

> John Gardner wrote: > > I'm using the dl register to set page indent with .in, which works fine in > nroff, but generates absurdly large sizes in groff. For instance, a > diversion with a width of 624 in TTY output becomes 286946 in PostScript. > > I'm aware this is connected to the matter of

Re: [Groff] Converting basic units to inches in PostScript

> Damian McGuckin wrote: > > On Wed, 3 Aug 2016, Larry Kollar wrote: > >> Is there some reason you can?t use device-independent units like inches or >> ens? >> >> .in 1i \? One inch indent on all devices >> .in 6n \? Six ens, (1 en is roughly the

Re: [Groff] colorized man pages

> Steffen Nurpmeso wrote: > > |still working with a text terminal, I'd expect escape codes to > |be your daily bread and butter, not something to scoff at. > |(Unless I'm missing the good-natured, approving irony here?) > > Yah! It seems control codes won't go away, Unicode adds > some

Re: [Groff] groff developments - query about any interest?

> Peter Schaffter wrote: > > On Tue, Nov 15, 2016, John Gardner wrote: >> ...I've decided the project *will *be named on NPM as *nroff*, >> with the human-readable title being "Node-Roff". Since any >> *reasonable* person can see why that's an appropriate name for a >> *node-based roff* generat

Re: [Groff] Inappropriate info page!

> Werner LEMBERG wrote: > > Whilst reading the info pages on Groff I came upon the following >>> >>> What following? You have forgotten to add a quote. >> >> He refers to doc/groff.texi line 5060. The wording is questionable >> indeed. > > Oh. I would have never expected that Larry K

Re: [Groff] Regarding HTML rendering

Ingo Schwarze wrote: > > ... > > Converting markdown into acceptable > roff input is just not feasible - not only because there is no tool > to do it, but also because markdown is just not powerful enough, > even if you were willing to write a new program to do that. > > Besides, i hate the myt

Re: [Groff] grops:signatur.eps:15: not an integer

> mikkel meinike wrote: > > The eps I used was generated with > > sam2p > > Now I tryed to generat it with gimp and I don't get the error massag from > using that file I remember this happening with some other tool I used to create EPS files. The same tool could produce EPSF files, and they

Re: [Groff] It is time to modernise "groff"

Modernizing is all well and good, but many people use groff to typeset legacy documents. Indeed, one could argue that groff has done an excellent job of walking that line between modernizing and backward compatibility. We have long names, HTML output (however crude), and a lot of people on this

Re: [Groff] Elegant -ms and -mpdfmark documents

> Kristaps Dzonsons wrote: > > Hello groffers, > > I have a survey question regarding -ms and -mpdfmark documents. … > > To wit, I > wonder if anybody who uses -ms and -mpdfmark has any suggestions on > settings to improve the legibility of produced documents. I used ms + pdfmark extensively

Re: [Groff] parallel text processing ; vertical and horizontal mode

E. Hoffmann wrote: > > Hello *roffers. > > Excuse me if this question has been answered zillions of time, > or if it is all absurd, but I don't find an answer ... > > I want to typeset parallel texts, like a translation, the original > *always* in the left column, the translation *always* rig

Re: [groff] [Groff] What does the "-u" in ".tmac-u" mean?

> Werner LEMBERG wrote: > > It's not about saving disk space. Remember that groff is an > interpreted language *without* a translation to an internal > representation.[*] This means, for example, that a comment within a > loop with 1000 repeats gets parsed a thousand times, again and again. >

Re: [groff] Unintended impact of strip.sed on om.tmac-u?

> Ralph Corderoy wrote: > >* The body of a 'while' request is treated like the body of a > 'de' request: 'gtroff' temporarily stores it in a macro that > is deleted after the loop has been exited. It can > considerably slow down a macro if the body of the 'while' > reque

Re: [groff] [UTROFF] About fonts

> Pierre-Jean wrote: > > Hello alls, > > > Heirloom Troff can mount OpenType fonts like any other font. It > can also define all kind of ligatures, adapt the kerning, and > enables the OpenType features, as follow. > >.fp 1 R LinLibertine_R otf >.flig R ct \[c_t] st \[s_t] >.featur

Re: [groff] A typo on fsf groff wiki page, and question about releasing

> John Gardner wrote: > > I'm wondering how many people here might react if I suggested porting the > entire Geoff codebase to JavaScript… LOL go for it! I often joked that nothing useful was ever written in Javascript. That hasn’t been true for a while, but it would be cool to see how you han

Re: [groff] Compilation of 1.22.3 doesn't work properly

Robert Marks wrote: > I have twice downloaded 1.22.3 and compiled it, following the INSTALL > instructions. > > Seems to compile correctly. > Then I install it. > > Then try to process a file (which works fine on another Mac Book Air of > mine). > I get the following error messages on processi

Re: [groff] Macros in their own package ...

> John Gardner wrote: > > Apropos of compatibility outside `groff`... > > Does anybody know of an exhaustive list of *roff implementations still in > common use? (Including legacy repositories of historical interest) > > The current Roff interpreters I'm aware of are: > > 1. *GNU Troff

Re: [groff] Macros in their own package ...

> John Gardner wrote: > >> There are been attempts (doclifter and -Thtml being two of the most >> ambitious) to make *roff output interchangeable with the rest of the world > I have something planned. But it's so ruthlessly absurd nobody would take > it seriously without proof. =) Hence why I'

Re: [groff] Macros in their own package ...

> Ralph Corderoy wrote: > >> I’m typesetting entire books out of Markdown (specifically, > >> MultiMarkdown). > > And that's the problem. Markdown is ill specified, poorly thought out, > and in consequence there are many dialects of Markdown. I always find it amusing when someone on a *roff

Re: [groff] groff as the basis for comprehensive documentation?

Nate Bargmann wrote: > I have long been involved with a project that has lacked good > documentation for nearly all of its existence. We've had documentation, > but it isn't in a good format for generating man, HTML, or PDF versions. > > Long ago I started with Docbook and then that got to a po

Re: [groff] groff as the basis for comprehensive documentation?

John Gardner wrote: > It's easier than you think.You just have to separate presentational > semantics from structural and content-related ones. I’m fond of saying ‘All you have to do is…’ is one of the biggest lies ever told. ;-D > I've seen grohtml's complexity and was bewildered. Hence why

Re: [groff] groff as the basis for comprehensive documentation?

Ingo Schwarze wrote: > So yeah, even though proportional font is slowly becoming more > widely used, you may be right: The legacy of Wolfram Schneider's > FreeBSD man.cgi is still pretty widespread and even motivated Michael > Stapelberg to use a fixed width font for Debian, even though the > r

Re: [groff] groff as the basis for comprehensive documentation?

John Gardner wrote: > It's ironic how this convention of unconventional formatting has stuck > around since the beginning, but in over 40 years of writing manpages, > nobody's been able to agree on a consistent way of hyphenating the damn > word. > > Manpages, man-pages, or man\(empages? I’ve

Re: [groff] groff as the basis for comprehensive documentation?

Some of this is really cool, and ties in with a couple things I’ve tried in the past. John Gardner wrote: > *1. Handling semantics* > We all know you can't draw semantics from cold, low-level formatting > commands. But for certain contexts - hierarchically sorted documents, > consistently inden

Re: [groff] Now online: gropdf / grops previewer

John Gardner wrote: > Well, here it is: > > https://rawgit.com/Alhadis/Roff.js/web-demo/index.html > Oh, cool. It’s like a web version of xditview(1). If it can update live, I’d use it as a previewer. Larry

Re: [groff] Spooky action at a distance in line adjustment...sometimes

> Ancient history: when I wrote BCPL roff, I immediately noticed the > page-level density gradient from thick on the left to thin on the > right if padding spaces were inserted from the right. I next tried > randomly distributing the padding. This was even worse because it > led one to perceive

Re: [groff] Groff & tbl as a report generator

Blake McBride wrote: > Thanks. I've seen a tool or two that converts HTML to PDF in the past but > I immediately shied away from them for the following reasons. > > 1. I figured HTML was just too loosey-goosey with the layout. I wanted > better control. > > 2. I figured HTML didn't deal with

Re: [groff] Creating a numbered list without macros

> Ralph Corderoy wrote: > > We're not entirely sure what he wants. ... Perhaps troff syntax, even with > mainly light-noise macros, would be off-putting to his users and so he's > wanting a pre-processor that produces troff. The input language could > be largely based on indentation, for exa

Re: [groff] Inexplicable error using tbl(1) 1.19.2 on macOS

> John Gardner wrote: > > Now, we all know Apple are clueless and continue to ship the most ancient > versions of software fathomable, but I find it impossible to believe that > at some point in Groff's history, there was a published tbl(1) release > whose only purpose was to spit confusing er

Re: [groff] Bold v Italics: Dawn of Justice

> Ingo Schwarze wrote: > >> Use italics > >> for environment variables, >> for enumeration or preprocessor constants in C, > > I don't particularly like that, and i also don't particularly like > Werner's alternative suggestion of setting them in bold; i'd prefer > roman, even though that al

Re: [groff] man-page fixes

Ingo Schwarze wrote: > Doug McIlroy wrote on Thu, Nov 15, 2018 at 08:40:14PM -0500: > >> Regardless of standards considerations, if there's any advice >> that needs to be hammered into man authors, it's to be concise >> and accurate, but not pedantic. As Will Strunk commanded, >> "Omit needle

Re: [groff] man-page fixes

> Damian McGuckin wrote: > > In what seems like a gazillion years ago, both DEC and IBM wrote manuals > using a subset of English to make their manuals easy to read for those for > whom English was not a native language. I would love to be able to find the > rules which governed the writing

Re: [groff] Release Candidate 1.22.4.rc3

Ingo Schwarze wrote: > While i'm well aware that what i'm saying here is a commitment to > a huge project, i'm willing to translate the whole groff texinfo > documentation into groff_mdoc(7). That’s going to be an impressive undertaking. I’m trying to visualize the results—would you make each

Re: [groff] Release Candidate 1.22.4.rc3

Ingo Schwarze wrote: >> * My semantic macro package extending groff_man(7), if I can get it >> where I'm happy with it and folks on the list don't bleed from the >> eyes about it. > > That would be a HUGE step backwards, making the groff manual pages > even less portable (they are already am

Re: [groff] Release Candidate 1.22.4.rc3

Ingo Schwarze wrote: > >> Being a fan of semantic markup myself, I'd normally agree. >> On the other hand, wouldn't the groff manpages always come >> with a groff formatter? > > Don't FreeBSD manual pages always come with FreeBSD and Linux manual > pages always with Linux? No, they dont't, i

Re: [groff] Regularize (sub)section cross references.

> On Dec 14, 2018, at 2:13 PM, Ingo Schwarze wrote: > > G. Branden Robinson wrote on Fri, Dec 14, 2018 at 10:46:57AM -0500: > >> […] >> . >> -See the >> -.B BUGS >> -section below. >> +See section \(lqBugs\(rq below. > > ... but i disagree with this particular change s/BUGS/Bugs/. > > There

[groff] Work-related rants

They have some groff-relevance, so I thought I’d share. Both have to do with our recent move to DITA at work. Rant the First: conditional page breaks = Like *roff, making a PDF from DITA involves going straight from source through a formatting processor to PDF. Unli

Re: [groff] mom: blockquotes lose indent across page breaks

Ingo Schwarze wrote: > Peter Schaffter wrote on Tue, Dec 18, 2018 at 01:41:45PM -0500: >> On Tue, Dec 18, 2018, Ingo Schwarze wrote: >>> Peter Schaffter wrote on Mon, Dec 17, 2018 at 08:55:04PM -0500: > I've updated mom-2.4.tar.gz on mom's website, > >>> Never change tarballs after they

Re: [groff] GNU troff version 1.22.4

> Bertrand Garrigues wrote: > > After a last commit (copyright year displayed on 'groff --version'), > I've created tag 1.22.4 and pushed the official package on GNU ftp. > Below is the annoucement done on the GNU info mailing list. Bravo to all who participated in the release! Too bad we cou

Re: [groff] Problems with -Thtml

Blake McBride wrote: > Greetings, > > I composed a user manual with MM. Looks great. I now need an HTML > version. I tried: > > groff -Thtml -mm build-manual.mm >build-manual.html > > The HTML file I got is unusable. It has the following problems: > > 1. The escape sequence '\s0' does

Re: [groff] 04/05: {g, n}roff.1.man: Give assistance to pager users.

> On Jul 2, 2019, at 8:20 PM, John Gardner wrote: > >> *There were 24 lines per page unless over-ridden on the command line.* >> *The tool was real unix tool, lean and mean with only a few arguments.* >> *It was far less functional than either 'more' or 'less' but it did**let >> you page throu

Re: Looking for informations

Ingo Schwarze wrote: > Writing good documentation requires good understanding of the source > code of the program. While writers documenting free software often > have that, translators almost never have it. Translated documentation > is almost always of much lower quality than the real thing

Re: GNUism in groff tests, was: pic anomalies

G. Branden Robinson wrote: > A rock star cowboy with a smoke machine to conceal the spit and bailing > wire in his implementation is hailed as a genius. > > An engineer who spends effort building a robust system is regarded as a > cost center. Can I steal these quotes (with attribution)? The

Re: Do you use the test-groff script?

Ingo Schwarze wrote: >> If you use test-groff, > > *Please don't!* I find it useful for checking a new version before I do “make install.” If you meant “don’t use it as your usual way to run groff,” I’d agree. But for testing? It does what I think it should.

Re: weird \s

Doug McIlroy wrote: > > I've been writing the ugly \s360 since ancient times. Groff still thinks > this means a 36-point 0. But man 7 groff says it means a 3-point 60: > > \s±N Set/increase/decrease the point size to/by N scaled points; N is > a one-digit number in the range

Re: Future of groff Texinfo manual (was: documentation of hyphenation)

G. Branden Robinson wrote: > > Hmm! It seems the ms stuff in our Texinfo manual may have started life > as an ms document after all. > > IIRC, Larry Kollar is sometimes seen on this list. Maybe he'd be > willing to share a copy of the ms sources so we don't have t

Re: Groff vs Heirloom troff (was Re: Quick question: how to do .index in groff?)

> It's not a question of which implementation has the bigger market > share, but which has the richer feature set. Currently each of them > can do things the other can't. There’s `.if [.g]` and `.if [.neat]` to test for a Groff or Neatroff environment, respectively. Presumably, Heirloom has a si

Re: \: re-enables hyphenation--should it?

It’s a space, which I would presume ends a word. A zero-width space, by definition, but still a space. I think I’ve run into the same issue, and put \% after the space to prevent hyphenation without thinking much about it. — Larry > On Jul 24, 2020, at 11:40 PM, G. Branden Robinson > wrote: >

Re: Groff vs Heirloom troff (was Re: Quick question: how to do .index in groff?)

Dave Kemper wrote: > On 7/31/20, Steve Izma wrote: >> I found that the TeX paragraph-at-a-time justification had to >> be scrutinized and adjusted just as much as my groff work. The >> trade-off to getting better word spacing was that often TeX just >> failed and overset lines. > > Do you kno

Re: \: re-enables hyphenation--should it?

On Jul 31, 2020, at 6:41 PM, Dave Kemper wrote: > > On 7/31/20, Larry Kollar wrote: >> It’s a space, which I would presume ends a word. A zero-width space, >> by definition, but still a space. > > I suppose that depends where you're getting your definition. Th

Re: Description of the naming conventions for variables, macros, etc in MS?

T. Kurt Bond wrote: > Is there a description of the naming conventions used in the groff ms > macros for variables, macros, and so forth? An * seems to mean > internal and ! seems to mean array, for instance. What does @ mean? I think it’s an internal destination-like thing. For example, a l

<    1   2   3   4   >