From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: non-breaking space after citeproc locator abbreviations (p., pp, ...)
Date: Thu, 25 May 2017 17:23:24 +0200 [thread overview]
Message-ID: <20170525152323.GC41849@ucbvpn-208-196.vpn.berkeley.edu> (raw)
In-Reply-To: <23bd041f-70d5-45c5-ae73-c03b97a5c7f9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
You can always modify your csl file so that it uses suffix=" "
instead of suffix=" " after a short-form locator. (You'll probably
have to modify this in several locations.)
See issue #3659 on github. If we go this way, we could in
principle run this typographic transformation after all
user-contributed transformations, so it would cover
pandoc-citeproc's contributions. I'm not sure I like that
idea, though.
+++ Rik Kabel [May 25 17 05:41 ]:
> Is there an option for pandoc/pandoc-citeproc to generate non-breaking
> spaces after the abbreviations citeproc generates for standard locators
> (p., pp., vol., ...)? Something similar to what is done with --smart,
> and possibly tied to --smart would be good.
> --
> Rik
>
> --
> You received this message because you are subscribed to the Google
> Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/23bd041f-70d5-45c5-
> ae73-c03b97a5c7f9%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/23bd041f-70d5-45c5-ae73-c03b97a5c7f9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-05-25 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 12:41 Rik Kabel
[not found] ` <23bd041f-70d5-45c5-ae73-c03b97a5c7f9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-25 15:23 ` John MacFarlane [this message]
[not found] ` <20170525152323.GC41849-TBBfCjvid+N7tZpUiIuOPD9KD7QXpuGTrnkq01ZRSOQ@public.gmane.org>
2017-05-25 19:36 ` Rik Kabel
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=20170525152323.GC41849@ucbvpn-208-196.vpn.berkeley.edu \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).