public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Tonkins <mtonkins-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: References in pandoc
Date: Mon, 16 May 2022 10:38:03 -0700 (PDT)	[thread overview]
Message-ID: <25cf7c0d-8665-45e6-8fc3-ea06e0fabe4en@googlegroups.com> (raw)
In-Reply-To: <867e8a95-27b5-4335-b199-722396668edd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

This is a great question, and I would like to know what people think? 

On Thursday, 15 March 2018 at 13:35:23 UTC J wrote:

> It seems to me from googling that pandoc-crossref is good for 
> cross-references in markdown. Would you consider pandoc-crossref to be 
> added ? Or would you consider pandoc-fignos better for the task ?
>
>
> On Sunday, March 4, 2018 at 4:44:34 AM UTC+8, John MacFarlane wrote:
>
>> I've sometimes thought of including pandoc-fignos, just as 
>> we now include pandoc-citeproc.  That might be a good move 
>> until we have better native reference handling. 
>>
>> +++ Alexandre Bergel [Mar 03 18 09:11 ]: 
>> >   Hi! 
>> >   I spent a few hours looking for a better way to make references in 
>> >   Pandoc. Why the pandoc-fignos filter is not part of the default 
>> pandoc 
>> >   distribution? I was really about to stop using pandoc because of the 
>> >   poor handling of references. 
>> >   I guess there is a pretty good reason why not doing so... which is? 
>> >   Cheers, 
>> >   Alexandre 
>> > 
>> >   -- 
>> >   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...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 
>> >   To post to this group, send email to 
>> >   [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 
>> >   To view this discussion on the web visit 
>> >   [3]
>> https://groups.google.com/d/msgid/pandoc-discuss/7a642901-09bd-4fd4- 
>> >   b529-568d79d17b7b%40googlegroups.com. 
>> >   For more options, visit [4]https://groups.google.com/d/optout. 
>> > 
>> >References 
>> > 
>>
> >   1. mailto:pandoc-discuss+unsub...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
>> >   2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
>> >   3. 
>> https://groups.google.com/d/msgid/pandoc-discuss/7a642901-09bd-4fd4-b529-568d79d17b7b-/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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/25cf7c0d-8665-45e6-8fc3-ea06e0fabe4en%40googlegroups.com.

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

  parent reply	other threads:[~2022-05-16 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 17:11 Alexandre Bergel
     [not found] ` <7a642901-09bd-4fd4-b529-568d79d17b7b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-03-03 20:44   ` John MacFarlane
     [not found]     ` <20180303204417.GA30811-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-03-15 13:35       ` J
     [not found]         ` <867e8a95-27b5-4335-b199-722396668edd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-16 17:38           ` Matt Tonkins [this message]
     [not found]             ` <25cf7c0d-8665-45e6-8fc3-ea06e0fabe4en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-17  6:33               ` krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2018-03-04 16:01   ` Alexandre Bergel

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=25cf7c0d-8665-45e6-8fc3-ea06e0fabe4en@googlegroups.com \
    --to=mtonkins-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).