discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Bullets everywhere
Date: Mon, 10 Jan 2011 23:11:10 +0100	[thread overview]
Message-ID: <20110110221110.GJ23329@acme.spoerlein.net> (raw)

Hello,

prompted by some gratuitous differences in groff vs mandoc output, I
wanted to ask for the rationale here (if any).

.Bl -bullet
.It 
one
.El

will print the following raw output:

mandoc:            o^Ho   one
groff[1] -Tascii:  +^H+^Ho^Ho   one
groff[1] -Tutf8:   ·^H·   one
groff[2] -Tascii:  ^[[1m+^Ho   ^[[22mone

[1] is groff 1.19.2 (the last GPLv2 release)
[2] is groff 1.20.1

HTML output of groff is kinda ridiculous:

<p style="margin-left:14%;">one</p>
<p style="margin-top: 1em" valign="top"><b>&bull;</b></p>

It's not even using <h1> for the document title ...

HTML for mandoc 1.10.9:

<ul style="margin-top: 0.00em;margin-bottom: 0.00em;" class="list list-bul">
<li class="list-bul" style="margin-top: 1.00em;">
one</li>

Not that bad, except that I think one shouldn't use multiple <h1> in one
document, but that's not the point of this email.

Postscript!

groff's output is nice (the old one, newer groff has an mdoc error
trying to produce postscript, might be my port is broken ...). The
bullets are Postscript bullets and `--' dashes also use the correct font
symbol.

Mandoc however is producing bold `o's as bullets for Postscript ...
yuck.

So what I'm mostly interested about is the +/o overprinting that groff
is trying to do. This won't work on my xterm, obviously. Was this
something that older printers could be coaxed into? Or teletypes, of
course?

Regards,
Uli
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2011-01-10 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 22:11 Ulrich Spörlein [this message]
2011-01-23 14:40 ` Ingo Schwarze
2011-01-23 17:22   ` Ulrich Spoerlein
2011-01-24 15:07     ` Kristaps Dzonsons
2011-01-25 14:35       ` Ulrich Spörlein

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=20110110221110.GJ23329@acme.spoerlein.net \
    --to=uqs@spoerlein.net \
    --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).