discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Humm <hummsmith42@gmail.com>
To: discuss@mandoc.bsd.lv
Subject: \h in PostScript and PDF output
Date: Sun, 9 Jan 2022 13:59:25 +0000	[thread overview]
Message-ID: <YdrqPTQzT+5F+E1+@beryllium.local> (raw)

Consider the input

	.TH A 1
	.SH S
	a\h'1u'b

For ASCII and UTF-8 output, in the output there is

	ab

In PDF and PostScript output, the “b” is way too far to the right.  
The PostScript for it is

	87.274 687.599(a)s
	166.408(b)c

That scales up: With \h'1n', the “b” is already off the page and thus 
not visible.  For `a\h'1n'b c`, there is a line break before “c”.

roff(7) does mention: (COMPATIBILITY)

>Support for explicit movement requests and escapes is limited.

I’m using Alpine Linux’s build of mandoc 1.14.6.

---

The context is the way the (-)man page generator scdoc
( https://git.sr.ht/~sircmpwn/scdoc ) handles lists: A list item

	- a

becomes

	.RS 4
	.ie n \{\
	\h'-04'\(bu\h'+03'\c
	.\}
	.el \{\
	.IP \(bu 4
	.\}
	a
	.RE

apparently for the looks.

-- 
Humm
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


             reply	other threads:[~2022-01-09 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 13:59 Humm [this message]
2022-01-10  7:37 ` Ingo Schwarze
2022-01-10 16:45   ` Humm
2022-01-10 18:50     ` 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=YdrqPTQzT+5F+E1+@beryllium.local \
    --to=hummsmith42@gmail.com \
    --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).