public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Nicolas Hillegeer
	<nicolashillegeer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to turn off hyphenation when writing roff/man pages? Variables nor metadata works
Date: Sun, 07 Jul 2019 08:47:51 -0700	[thread overview]
Message-ID: <87lfx9g82g.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CACqJ-1e6EMt2z2P_k9SkFYrDEaHathk-N0-9nCZrAhmH6uBjDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Nicolas Hillegeer <nicolashillegeer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Is there perhaps some other way to prevent hyphenation of either:
>
>   - A section.
>   - "Words" that have been marked a certain way (like bolded or in code
> blocks). I tried a number of things but nothing seemed to take effect in
> that sense. I would've expected code blocks to do it (as in, they would be
> verbatim).

You can turn off groff hyphenation at any point in the
document, I think, by doing

.nh

and then re-enable it with

.hy

So one option would be to insert

```{=man}
.nh
```

before your table, and

```{=man}
.hy
```

after it.  These will be passed through to man output.

It would be nice to make this more automatic for code,
but I don't see a way to do that other than using a
custom macro for code, which would make pandoc's
output a little more brittle.


      parent reply	other threads:[~2019-07-07 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 20:16 Nicolas Hillegeer
     [not found] ` <fbaf534c-daf9-49fe-8a20-190663a88c33-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-07-04 17:24   ` John MacFarlane
     [not found]     ` <874l41n25d.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-07-05 22:22       ` Nicolas Hillegeer
     [not found]         ` <CACqJ-1e6EMt2z2P_k9SkFYrDEaHathk-N0-9nCZrAhmH6uBjDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-07-07 15:47           ` John MacFarlane [this message]

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=87lfx9g82g.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=nicolashillegeer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).