public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Rik Kabel <amphiboly-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: non-breaking space after citeproc locator abbreviations (p., pp, ...)
Date: Thu, 25 May 2017 12:36:05 -0700 (PDT)	[thread overview]
Message-ID: <e35d2da1-8c23-41fc-b11d-bd5aa4fd56d1@googlegroups.com> (raw)
In-Reply-To: <20170525152323.GC41849-TBBfCjvid+N7tZpUiIuOPD9KD7QXpuGTrnkq01ZRSOQ@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2939 bytes --]

That works for me. I may not have got all of them, but I got the one that 
is causing the ugliness.

Thank you for the pointer on where to look for it.

WRT issue 3659, I would expect it has to done after citeproc processing. If 
not, you have some abbreviations processed and some not.

(And now to create a system to remember what was done and make it easier to 
do when the CSL file is updated.)

-- 
Rik

On Thursday, May 25, 2017 at 11:23:39 AM UTC-4, John MacFarlane wrote:
>
> You can always modify your csl file so that it uses suffix="&#160;" 
> 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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To post to this group, send email to 
> >   [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   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 <javascript:> 
> >   2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   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 
>
>

-- 
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 pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e35d2da1-8c23-41fc-b11d-bd5aa4fd56d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 6419 bytes --]

      parent reply	other threads:[~2017-05-25 19:36 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
     [not found]     ` <20170525152323.GC41849-TBBfCjvid+N7tZpUiIuOPD9KD7QXpuGTrnkq01ZRSOQ@public.gmane.org>
2017-05-25 19:36       ` Rik Kabel [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=e35d2da1-8c23-41fc-b11d-bd5aa4fd56d1@googlegroups.com \
    --to=amphiboly-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).