discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: \l with negative (leftward) length broken
Date: Sun, 25 Sep 2022 18:18:26 +0200	[thread overview]
Message-ID: <20220925161826.mkpuxk43bckq2zxa@tarta.nabijaczleweli.xyz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

Hi!

  zupsko\l'-\w'zupsko'u\(ul'
is rendered as 
  zupsko______________________________________________________________________________
(i.e. to the right margin) by all mandocs I have in -Tutf8
and as absolutely nothing in -Thtml.

Conversely, groff renders it as underlined zupsko in all modes.

The mandoc output is the same if the width is -3n;
again, groff renders it as zups\b_k\b_o\b_.

More worryingly,
  zupsko\l'|0\(ul'
does nothing on mandoc, instead of correctly underlining the whole line.

In the final case I'm happy to say that mandoc is straight-up broken,
since that /exact/ spelling I encountered in 4BSD tty(4), which uses
  .de Ul
  .ie t \\$1\l'|0\(ul'
  .el \fI\\$1\fP
  ..
to delineate subheadings (McKusick's The CSRG Archives CD#1,
4.0/usr/man/man4/tty.4)
(an equivalent macro appears in the troff user's manual;
 ibid., 3bsd/usr/doc/troff/m3,
 but not in the pages themselves).

The same appears in fsck(8) and and at increasing frequency in manuals
up to 4.3BSD; \l with negative (leftward) distance doesn't seem to've
been used.

Best,
наб

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2022-09-25 16:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220925161826.mkpuxk43bckq2zxa@tarta.nabijaczleweli.xyz \
    --to=nabijaczleweli@nabijaczleweli.xyz \
    --cc=discuss@mandoc.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).