public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Michael Becker
	<michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Superscript footnotes in MD to docx converation
Date: Thu, 27 May 2021 16:30:52 -0700	[thread overview]
Message-ID: <m2fsy7rbyr.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <8b5d7348-1e42-414b-a6e2-0b393658541dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


I suggest you first try it without the reference doc.
If the problem goes away, then most likely it's because
of something in your reference doc.
If not, try upgrading pandoc. Your version is quite old.

Michael Becker <michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org> writes:

> Oh, and yes, I'm using a reference doc. 
>
> On Thursday, May 27, 2021 at 12:55:39 PM UTC-7 Michael Becker wrote:
>
>> Pandoc 2.1. MSFT Word for Mac, Ver 16.49.
>>
>> On Thursday, May 27, 2021 at 10:01:46 AM UTC-7 Bastien Dumont wrote:
>>
>>> What version of pandoc are you using? I just tested it with 2.13, and I 
>>> don't have this problem. I opened it with both Word 2010 and LibreOffice 
>>> 7.1.3.2. 
>>>
>>> Le Thursday 27 May 2021 à 08:25:21AM, Michael Becker a écrit : 
>>> > Yes, but pandoc does NOT appear to be applying this styple wihen 
>>> converting 
>>> > markdown footnotes to docx. 
>>> > 
>>> > On Thursday, May 27, 2021 at 8:21:42 AM UTC-7 Bastien Dumont wrote: 
>>> > 
>>> > There is a style for footnote references in Word. 
>>> > 
>>> > Le Thursday 27 May 2021 à 07:42:25AM, Michael Becker a écrit : 
>>> > > Hey there, I've created well formed markdown for foot notes, e.g. 
>>> [^1], 
>>> > and 
>>> > > pandoc is almost converting them perfectly. The problem is that the 
>>> > footnote 
>>> > > number is not being formated as a superscript, it is just coming 
>>> through 
>>> > as a 
>>> > > number, e.g. footnote1 rather than footnote<sup>1</sup>. 
>>> > > 
>>> > > Is there anything that can be done? 
>>> > > 
>>> > > -- 
>>> > > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 
>>> > > To view this discussion on the web visit https://groups.google.com/d/ 
>>> > msgid/ 
>>> > > pandoc-discuss/b5be73f0-7fab-4333-818f-7559b730f766n%
>>> 40googlegroups.com. 
>>> > 
>>> > 
>>> > -- 
>>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ 
>>> > pandoc-discuss/08384785-a229-461a-bbc7-91135519351dn%40googlegroups.com. 
>>>
>>>
>>>
>
> -- 
> 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/8b5d7348-1e42-414b-a6e2-0b393658541dn%40googlegroups.com.

-- 
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/m2fsy7rbyr.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2021-05-27 23:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 14:42 Michael Becker
     [not found] ` <b5be73f0-7fab-4333-818f-7559b730f766n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-27 15:21   ` Bastien DUMONT
2021-05-27 15:25     ` Michael Becker
     [not found]       ` <08384785-a229-461a-bbc7-91135519351dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-27 16:58         ` John MacFarlane
2021-05-27 17:01         ` Bastien DUMONT
2021-05-27 19:55           ` Michael Becker
     [not found]             ` <f037c968-7143-4fa0-9441-31a7ea2190e5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-27 19:56               ` Michael Becker
     [not found]                 ` <8b5d7348-1e42-414b-a6e2-0b393658541dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-27 23:30                   ` John MacFarlane [this message]
     [not found]                     ` <m2fsy7rbyr.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-05-28  3:23                       ` Michael Becker
2021-05-28 12:36                       ` Michael Becker

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=m2fsy7rbyr.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@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).