public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: 'Marek Stepanek' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Print footnote at the end of each chapter
Date: Sun, 17 Jul 2022 14:27:58 +0000	[thread overview]
Message-ID: <YtQcboo3XHZ3xln1@localhost> (raw)
In-Reply-To: <2f1b62af-3a08-487e-9a44-3e8ed0d3cd5en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Have you tried to use a dedicated LaTeX package such as endnotes (https://ctan.org/pkg/endnotes)?

Le Sunday 17 July 2022 à 02:01:15AM, 'Marek Stepanek' via pandoc-discuss a écrit :
> Some more explanations, to provoke an answer. I need inline References, wich
> are collected at the end of each article. I tried with [1] or [(1)]  or [1]
> [Fn:1]  etc
> 
> But in my section:
> 
> ## References and sources 
> 
> [1]: First Footnote 
> [(1)]: First Footnote
> [Fn:1]: First Footnote
> 
> is printed nothing. In the pdf-file the anchor seems to be linked, but on click
> leading to nothing.
> 
> in my Header includes is also 
> 
> ___
> 
> - \usepackage{hyperref}
> - \hypersetup{pdftitle={Articles 22022},pdfauthor={myself},pdfsubject=
> {Subjects}}
> 
> ___
> 
> Are these informations sufficient to help me out?
> 
> I would be very grateful for any hint in the right direction
> 
> 
> marek
> 
> 
> 
> 
> 
> On Saturday, July 16, 2022 at 10:20:50 AM UTC+2 Marek Stepanek wrote:
> 
> 
>     I am compiling with pandoc markdown with documentclass scrartcl over LaTeX
>     to pdf. I have several articles in one file and would like to print the
>     footnotes at the end of each article.
> 
>     I tried pandoc-crossref, but apparently it is not supporting footnotes and
>     needs in the anchor a leading keyword like `@fig:` or `@sec:` `@lst:`. But
>     footnotes are not supported (please correct me).
> 
>     I tried with `--reference-location=block|section|document` in my Makefile
>     like follows:
> 
>     ```
>     all: save typeset open
> 
>     .PHONY: all
>     save:
>         w
> 
>     typeset:
>         pandoc                                                    \
>           --from         markdown                                 \
>           --to           latex                                        \
>           --out             articles.pdf                               \
>           --pdf-engine      pdflatex                                 \
>           --bibliography articles.bib                             \
>           -F pandoc-crossref                                     \
>           --reference-location=section                             \
>           --citeproc                                              \
>           --csl          csl/din-1505-2-numeric-alphabetical.csl \
>           --lua-filter   pandoc-gls.lua                              \
>           articles.md
> 
>     open:
>         open articles.pdf
>     ```
> 
>     Probably wrong idea. Perhaps somebody could point me to the right direction
> 
>     marek
> 
> --
> 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 view this discussion on the web visit [2]https://groups.google.com/d/msgid/
> pandoc-discuss/2f1b62af-3a08-487e-9a44-3e8ed0d3cd5en%40googlegroups.com.
> 
> References:
> 
> [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [2] https://groups.google.com/d/msgid/pandoc-discuss/2f1b62af-3a08-487e-9a44-3e8ed0d3cd5en%40googlegroups.com?utm_medium=email&utm_source=footer

-- 
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/YtQcboo3XHZ3xln1%40localhost.


  parent reply	other threads:[~2022-07-17 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16  8:20 'Marek Stepanek' via pandoc-discuss
     [not found] ` <aefe7d21-3dbd-4a08-acb7-0f8154d6712en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-17  9:01   ` 'Marek Stepanek' via pandoc-discuss
     [not found]     ` <2f1b62af-3a08-487e-9a44-3e8ed0d3cd5en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-17 14:27       ` Bastien DUMONT [this message]
2022-07-17 18:34         ` 'Marek Stepanek' via pandoc-discuss
     [not found]           ` <53b53720-9cfc-449f-a3a9-e7948c7b3f21n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-17 19:36             ` Bastien DUMONT
2022-07-17 20:44               ` 'Marek Stepanek' via pandoc-discuss
     [not found]                 ` <4af3664b-3552-4f66-b86e-b63bad2d59e9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-17 20:58                   ` Bastien DUMONT
2022-07-18  5:08                     ` 'Marek Stepanek' via pandoc-discuss

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=YtQcboo3XHZ3xln1@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).