From: olivier appere <olivier.appere-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Footnotes not numbered, asterix and other werid character instead
Date: Mon, 15 Jul 2019 12:42:32 -0700 (PDT) [thread overview]
Message-ID: <659fef19-8f68-4894-aa2a-68254685a2bc@googlegroups.com> (raw)
In-Reply-To: <50ee7dc6-384e-4271-8abe-f887eca99abc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1505 bytes --]
And I try to add
*\renewcommand{\thefootnote}{\arabic{footnote}} *
in the template but still no differences
Le lundi 15 juillet 2019 21:34:33 UTC+2, olivier appere a écrit :
>
> Hi,
>
> I am struggling with footnotes rendering with pandoc and PDF generation
> I have this kind of footnotes in Markdown:
>
> plans are review according to SVP with **independence**[^airbus].
>
> [^airbus]: {{ABD0100110}} chapter 13.2.2 Independence and Plans
>
> When I render in HTML footnotes are numbered as expected but when I am
> rendering in PDF I have no numbers
> but characters like * or || etc.
>
> I use xelatex (defaut engine render the same)
>
> Is someone get a clue ?
>
> PS:
>
> In intermediate latex file I have:
>
> according to SVP with
> \textbf{independence}\footnote{ABD0100.1.10 G chapter 13.2.2
> Independence and Plans}.
>
> Is this a problem of latex or pdf rendering ?
>
>
--
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/659fef19-8f68-4894-aa2a-68254685a2bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2341 bytes --]
next prev parent reply other threads:[~2019-07-15 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 19:34 olivier appere
[not found] ` <50ee7dc6-384e-4271-8abe-f887eca99abc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-07-15 19:42 ` olivier appere [this message]
[not found] ` <659fef19-8f68-4894-aa2a-68254685a2bc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-07-15 19:54 ` BP Jonsson
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=659fef19-8f68-4894-aa2a-68254685a2bc@googlegroups.com \
--to=olivier.appere-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).