From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Cc: aldis@bsdroot.lv
Subject: Re: groff `Lk' badness
Date: Mon, 09 Aug 2010 02:22:05 +0200 [thread overview]
Message-ID: <4C5F4A2D.9040506@bsd.lv> (raw)
In-Reply-To: <20100808193700.GC28837@usta.de>
>> mandoc formats its output as "foo: bar baz xyzzy",
>
> I think this is wrong, and
>
> "bar baz xyzzy: foo"
>
> would be better.
I just committed a fix for this. Thanks!
> The real mess is here:
>
> schwarze@rhea $ /usr/local/bin/groff --version | head -n1
> GNU groff version 1.20.1
> schwarze@rhea $ /usr/local/bin/groff -mdoc -Thtml link.in
> [...]
> NetBSD:</i> <b>http://www.netbsd.org/</b> <i><br>
> OpenBSD:</i> <b>http://www.openbsd.org/</b></p>
>
> Groff doesn't even attempt to produce real hyperlinks
> in -Thtml mode. Is this true?
groff passes only style bits via groff_out(7). So it can't by design do
anything more. Run groff -Z -mandoc to see for yourself.
grohtml in general is pretty useless (even Werner has said so). Another
part of the design of troff: it was never built for hierarchical output.
> I think we should have something similar to:
>
> <a href="http://www.netbsd.org/">NetBSD</a>:
> <b>http://www.netbsd.org/</b>
Ours simply formats as <a href="LINK">LINK-NAME</a> if a link name is
specified, else just <a href="LINK">LINK</A>. I generally think that
writing an entire URI in a browser is superfluous as it usually shows up
someplace, e.g., the status bar. I'm not married to this behaviour, I
guess. If anybody else also thinks this should be changed, I'll do it.
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-08-09 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 18:52 Kristaps Dzonsons
2010-08-08 19:37 ` Ingo Schwarze
2010-08-09 0:22 ` Kristaps Dzonsons [this message]
2010-08-09 19:24 ` Ingo Schwarze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5F4A2D.9040506@bsd.lv \
--to=kristaps@bsd.lv \
--cc=aldis@bsdroot.lv \
--cc=discuss@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).