public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Deri <deri@chuzzlewit.myzen.co.uk>
To: Paul Eggert <eggert@cs.ucla.edu>, groff@gnu.org
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	Time zone mailing list <tz@iana.org>,
	linux-man <linux-man@vger.kernel.org>, groff <groff@gnu.org>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Doubts about a typo fix
Date: Sat, 26 Nov 2022 12:33:24 +0000	[thread overview]
Message-ID: <3226872.5fSG56mABF@pip> (raw)
In-Reply-To: <20221126035253.pli53qzgfx6tbax5@illithid>

On Saturday, 26 November 2022 03:52:53 GMT G. Branden Robinson wrote:
> Some distributors do violence to the man.local file.  But I am not a PDF
> expert; for this I'll have to turn as I often do to Deri James, who also
> wrote the gropdf output driver.  Deri, what's a good way to root-cause
> the issue Paul describes?


Whenever there is a query about the "look" of a pdf it is important to rule 
out any vagaries in the particular fonts used by the pdf viewer used, so 
please repeat your tests adding "-P-e" to the command.

As regards the cut and paste of MINUS SIGN as a hyphen, this can be turned off 
by including -P-u as well. Note this will also affect the treatment of 
ligatures (ff/fi/ffi) in that cut and paste will not return them to their 
individual characters. It also affects string searching within the pdf, the 
troff input "\-b" would not be found by entering -b in the pdf viewer's search 
widget. Tested on Branden's minus-and-hyphen.man, with -P-u it finds -baz, 
without it finds both -bar and -baz.

Cheers 

Deri




  reply	other threads:[~2022-11-26 12:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 19:31 Doubts about a typo fix Alejandro Colomar
2022-11-23 21:40 ` G. Branden Robinson
2022-11-26  2:18   ` Paul Eggert
2022-11-26  3:20     ` [tz] " Russ Allbery
2022-11-26  3:50       ` Paul Eggert
2022-11-26 20:44         ` G. Branden Robinson
2022-11-26  3:52     ` G. Branden Robinson
2022-11-26 12:33       ` Deri [this message]
2022-11-26 21:01       ` Paul Eggert
2022-11-26 21:56         ` G. Branden Robinson
2022-11-27  1:58           ` Deri
2022-11-27  2:32           ` Paul Eggert
2022-12-13 19:24             ` G. Branden Robinson
2022-12-25 22:07               ` Lennart Jablonka
2022-12-25 23:21                 ` G. Branden Robinson
2022-11-26 21:20       ` Steffen Nurpmeso
2022-11-26 22:07         ` G. Branden Robinson

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=3226872.5fSG56mABF@pip \
    --to=deri@chuzzlewit.myzen.co.uk \
    --cc=alx.manpages@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=tz@iana.org \
    /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