From: Ian Cornelius <ircornelius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: separating citations in md
Date: Mon, 8 May 2023 05:25:20 -0700 (PDT) [thread overview]
Message-ID: <3ba766cb-b261-4576-8e12-a43496a5bc8fn@googlegroups.com> (raw)
In-Reply-To: <8a80881f-a26a-48e4-be33-3492910aa752n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1724 bytes --]
Use the option --reference-links. See here:
https://pandoc.org/MANUAL.html#option--reference-links
On Sunday, May 7, 2023 at 2:54:47 PM UTC-5 Mark Pinsley wrote:
> I have attached three files
>
> First.md
> First.HTML
> Updated.md
>
> I wrote First.Md
> it looks like this:
>
> Test my reference
> [Dermamed]
> [yahoo]
> [MultiMarkdown]
> [MarkDown]
>
> This is a [Link](www.usatoday) where the url is directly next to the word
> link in markdown
>
> <!-- Citations -->
> [Dermamed]: https://www.dermamedsolutions.com
> [yahoo]: https://www.yahoo.com
> [MultiMarkdown]: https://fletcherpenney.net/multimarkdown/
> [Markdown]: https://daringfireball.net/projects/markdown/
>
>
> What I am doing is keeping the URL citations at the bottom to keep the
> text clean looking. Sometimes I have some pretty long URLs
>
> In Pandoc I used the command
> 'pandoc -s "First.md" -o First.html
>
> The HTML comes out as expected
> Then I used the Pandoc command
> 'pandoc -s First.html -o updated.md
>
> When you look at the new updated.md file. You will see that all links are
> on the same line as the text (rather than at the bottom). I was looking for
> a command to create all these links at the bottom rather than inline. Is
> there a way to do that?
>
>
--
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/3ba766cb-b261-4576-8e12-a43496a5bc8fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3461 bytes --]
next prev parent reply other threads:[~2023-05-08 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 19:54 Mark Pinsley
[not found] ` <8a80881f-a26a-48e4-be33-3492910aa752n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-08 12:25 ` Ian Cornelius [this message]
[not found] ` <3ba766cb-b261-4576-8e12-a43496a5bc8fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-08 12:37 ` Mark Pinsley
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=3ba766cb-b261-4576-8e12-a43496a5bc8fn@googlegroups.com \
--to=ircornelius-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).