The roff(7) contains broken links.
Namely, http://cm.bell-labs.com doesn't even exist any more.
The archive of the Bell Labs Journal and the technical reports
seem to be available at https://www.alcatel-lucent.com/bell-labs-journals
but I didn't go through the indiviudual references. (I did once,
The page "History of UNIX Manpages" http://manpages.bsd.lv/history.html
is more comprehensive than troff.org, contains links to the old material
and correspondence with the actual authors.
Jan
diff --git a/man/roff.7.man b/man/roff.7.man
index a9a62e3..512c323 100644
--- a/man/roff.7.man
On Nov 15 20:00:09, gardnerjo...@gmail.com wrote:
> > *"There is a reason I am keeping these ramblings off-list."*
>
> Well you haven't stated the reason, so I'll assume it's fear of opprobrium.
Exactly. Shudder to think.
I just don't think this is much relevant to groff itself.
> *"What hope d
Hi all,
the link to "mission-statement-strings.mom" on the groff title page,
i.e. https://www.gnu.org/software/groff/groff-mission-strings.mom
is broken.
Jan
This is groff 1.22.3 as installed by the OpenBSD port.
Below please find a short manpage written in mdoc(7),
which I am trying to process into html with
groff -Thtml -mdoc rtpdump.1 > rtpdump.html
One point where it seems to fail is
.Oo Ar address Oc Ns / Ns Ar port
- the html
ping
On Dec 07 16:41:01, h...@stare.cz wrote:
> This is groff 1.22.3 as installed by the OpenBSD port.
>
> Below please find a short manpage written in mdoc(7),
> which I am trying to process into html with
>
> groff -Thtml -mdoc rtpdump.1 > rtpdump.html
>
> One point where it seems to fa
Hi Ingo,
>
> Jan Stary wrote on Mon, Feb 12, 2018 at 03:32:47PM +0100:
>
> > This is groff 1.22.3 as installed by the OpenBSD port.
> >
> > Below please find a short manpage written in mdoc(7),
> > which I am trying to process into html with
> >
On Feb 17 08:58:04, mbian...@foveal.com wrote:
> On Sun, Feb 16, 2020 at 07:55:31PM -0800, Larry McVoy wrote:
> > I *hate* info. It has made Linux less available to a lot of people.
>
> BUT info sometimes has information that man(1) lacks.
AFAIK, it is quite usual in GNU to maintain a texinfo do
On Apr 12 20:44:31, schwa...@usta.de wrote:
> generally speaking, most software delivered with Mac OS X is totally
> outdated, usually by several years, sometimes by more than a decade,
$ groff --version
GNU groff version 1.19.2
Copyright (C) 2004 Free Software Foundation, Inc.
That's macOS 10.15
On Apr 13 06:07:51, pengyu...@gmail.com wrote:
> But my question is how to make the GNU groff the same as the original
> Mac groff. I don't think all of you answer this question.
There is no "original mac groff".
groff is GNU roff, by definition.
Mac just ships with an ancient version of that.
>
On Apr 21 22:24:11, g.branden.robin...@gmail.com wrote:
> > Then again, the whole contrib/groffer directory is an abomination
> > that i suggest should be deleted outright, without any replacement.
>
> Does anyone object to just deleting groffer?
Please kill it, along with its manpage
that makes
On Jun 14 15:50:13, hacke...@member.fsf.org wrote:
> Hi!
>
> I've been writing up a lengthy man page using -mdoc and it's been
> great so far. I love that I can also easily create a beautiful PDF
> document using groff -Tpdf. But there is one problem I haven't solved:
> How can I make links which
On Jun 16 02:36:40, hacke...@member.fsf.org wrote:
> Ingo Schwarze wrote:
>
> > >> You say mdoc; shouldn't the links be Lk?
> >
> > In mdoc(7): yes, absolutely.
> > Use .Lk in mdoc(7), .UR is not supported by mdoc(7) at all.
>
> Thank you, Ingo, for letting me know that. I'll use Lk if I can fi
On Jun 16 19:02:50, hacke...@member.fsf.org wrote:
> Jan Stary wrote:
>
> > Attached please see the PDF output of groff 1.22.4 and mandoc 1.14.5;
> > neither of them adds a newline before or after the clickable link.
>
> What is the groff command line you are using? I t
> > - don't set the URL at all in the body of the text but use a
> > footnote or endnote marker and set the URL in the footnote or
> > endnote, since these are usually set in a smaller point size
> > and gives you more flexibility for fitting on lines; if a text
> > contains a lot of URLS,
On Jun 19 06:08:44, hacke...@member.fsf.org wrote:
> Jan Stary (or anyone): would you please post the output of 'groff -Z
> -mdoc -Tpdf' for the example input which converted Lk to hyperlinks?
> I'd like to paste it into Alhadis's Roff.js and see where my groff is
&g
On Jun 19 13:45:14, hacke...@member.fsf.org wrote:
>
> > This is my output (diff to your output follows):
>
> Thank you, Jan Stary. I am a bit confused because the intermediate
> output you sent doesn't have any PDF hypertext information in it.
>
> When I use &#
> While I agree that a shorter line length is more readable, I frequently
> exit a manpage, maximise the terminal window, then reopen it when my
> goal is to quickly scan the page for a relevant option.
I don't get it: how does a wider text window help you find an option?
> I find argument lists
On Oct 05 11:43:33, jklow...@schemamania.org wrote:
> On Sun, 4 Oct 2020 20:46:20 +0200
> Ingo Schwarze wrote:
>
> > You are discussing a problem that has been solved years ago, and
> > the solution has proven very successful in practical use: mdoc(7)
> > style is that you *never* specify the cla
On Oct 07 14:58:31, jklow...@schemamania.org wrote:
> On Mon, 5 Oct 2020 18:48:27 +0200
> Jan Stary wrote:
>
> > In the mdoc source, it's .Sh DESCRIPTION; that's it.
> > if Sh sections get turned into h1's (which is a decision in itself),
> > all this do
> > We're starting from an mdoc document, right?
>
> In my example, yes.
>
> > Therefore every h1 is generated from Sh,
>
> I'm not sure where the mapping from mdoc macros
> to html elements is described (beside the code),
> but Ingo surely will know.
>
> > so every h1 is . What, then, is the
On Oct 14 12:41:35, pe...@schaffter.ca wrote:
> What difficulties do you have entering UTF8 directly into the
> source? I've produced groff documents in most of the Western
> European and Scandinavian languages with direct UTF8 input. Are
> your troubles with languages other than those?
For inst
Hi Branden,
as an author of manpages for command-line utilities,
I want to type e.g. `this' into a manpage source like `this'
because that's exactly what you type on the cmdline
and that's what I want the user to read in the manpage.
To be sure: are you proposing that manpage authors
type somethi
On Nov 01 15:37:39, g.branden.robin...@gmail.com wrote:
> At 2020-10-31T15:58:00+0100, Jan Stary wrote:
> > Hi Branden,
> >
> > as an author of manpages for command-line utilities, I want to type
> > e.g. `this' into a manpage source like `this' because th
On Nov 02 12:09:45, schwa...@usta.de wrote:
> Hi,
>
> Werner LEMBERG wrote on Mon, Nov 02, 2020 at 09:42:35AM +0100:
>
> > To summarize: It seems that there is only a single platform left today
> > that by default uses a bitmap font for terminals with symmetric ` and
> > ' characters. This sort-
> >>> What options are needed to make GNU groff behave the same as
> >>> Mac OS X groff?
Roll back 16 years:
groff --version
GNU groff version 1.19.2
Copyright (C) 2004 Free Software Foundation, Inc.
On Nov 15 16:23:38, schwa...@usta.de wrote:
> Some people argue for a third level of conciseness vs.
> completeness, e.g. the --help option. I consider that detrimental
> because it adds a larger amount of text than the SYNOPSIS for
> a lesser gain (because you already have both ve
On Nov 15 18:26:16, schwa...@usta.de wrote:
> > Implementing the -h or --help option mostly becomes calling usage(),
>
> Not usually.
>
> The usage() output ideally corresponds to the synopsis:
>
>$ man -h groff
> groff [-abcegijklpstzCEGNRSUVXZ] [-d cs] [-D arg] [-f fam] [-F dir]
>
> > The problem with symlinks is that they need to be updated to match
> > manpage compression. `.so` works with any compression used for the
> > manpage.
That's not a problem with symlinks,
but a problem with manpage compression.
Why would anyone compress manpages?
How much space does that save
29 matches
Mail list logo
