unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23647@debbugs.gnu.org
Subject: bug#23647: 25.1.50; In man pages, links on hyphenated words don't work
Date: Mon, 30 May 2016 03:22:58 +0300	[thread overview]
Message-ID: <83vb1wwg0t.fsf@gnu.org> (raw)
In-Reply-To: <878tys31i6.fsf@gmx.net> (message from Stephen Berman on Mon, 30 May 2016 01:09:21 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 23647@debbugs.gnu.org
> Date: Mon, 30 May 2016 01:09:21 +0200
> 
> > Is it only the ASCII hyphen/minus, or could there be other characters
> > (e.g., if Groff/troff are invoked with some exotic -Tfoo switch)?
> 
> That possibility didn't occur to me but according to Wikipedia, groff
> also outputs soft hyphens (octal 255) and indeed I see that the function
> Man-build-references-alist, which also removes hyphenation (in a more
> complicated way that doesn't seem to be needed in the present case),
> also takes the soft hyphen into account.  That can be done here too by
> changing the above string-match regexp to "[-­]".  If someone knows of
> other possibilities allowed by [gt]roff, maybe the regexp could be
> further extended, or the condition reformulated as required.  What do
> you think?

I'm not enough of a roff expert to tell, but how about asking on the
Groff list?





  reply	other threads:[~2016-05-30  0:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29  9:52 bug#23647: 25.1.50; In man pages, links on hyphenated words don't work Stephen Berman
2016-05-29 14:42 ` Eli Zaretskii
2016-05-29 23:09   ` Stephen Berman
2016-05-30  0:22     ` Eli Zaretskii [this message]
2016-05-30 13:55       ` Stephen Berman
2016-06-04 15:35         ` Eli Zaretskii
2016-06-05 11:17           ` Stephen Berman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vb1wwg0t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23647@debbugs.gnu.org \
    --cc=stephen.berman@gmx.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).