public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Jeffrey T <jefftreistman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: LaTeX footnote citations parentheses
Date: Sun, 16 May 2021 12:41:54 -0700	[thread overview]
Message-ID: <m2tun2fou5.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <b1d2d845-7dd8-4b3d-a059-9562bfb89d2fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Sorry, I'd mistakenly assumed you were using pandoc markdown;
if you're using LaTeX, my comment doesn't apply.

Jeffrey T <jefftreistman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hi John,
>
> Thank you for the reply!
>
> I'm admittedly unfamiliar with @cite or [@cite] commands, but from my *very* 
> limited familiarity I believe these commands are related to markdown and 
> not LaTeX? Can I simply enter these commands in LaTeX and allow Pandoc to 
> somehow do the work? Alternatively, does this suggest I need to first 
> convert my LaTeX file to markdown, then markdown to Word?
>
> Thanks!
>
>
> On Saturday, May 15, 2021 at 7:53:59 PM UTC-4 John MacFarlane wrote:
>
>>
>> Try using the @cite form rather than the [@cite] form inside the
>> footnote.
>>
>> Jeffrey T <jefftr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > Hi all,
>> > I'm new to the group and Pandoc and would greatly appreciate your 
>> > assistance. I'm attempting to convert my LaTeX book manuscript into a 
>> Word 
>> > doc for my editor. Using a test .tex file, I have successfully converted 
>> > the file using the following command in Mac Terminal : 
>> > pandoc --citeproc Test.tex --bibliography=testref.bib 
>> > --csl=chicago-fullnote-bibliography-short-title-subsequent.csl -o 
>> test.docx
>> > It works wonderfully, however, the only issue concerns the \cite 
>> contained 
>> > within \footnote. In particular, the resulting citation is now placed 
>> > within parentheses which my editor has asked me to remove. Is there some 
>> > sort of solution to my dilemma? Given the length of the book I fear it 
>> will 
>> > be quite tedious to find/remove the offending parentheses manually. 
>> > Thank you in advance!
>> >
>> > -- 
>> > 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/f4c18da4-6145-4f93-8779-fe2bd2816c38n%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/b1d2d845-7dd8-4b3d-a059-9562bfb89d2fn%40googlegroups.com.


      parent reply	other threads:[~2021-05-16 19:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 19:13 Jeffrey T
     [not found] ` <f4c18da4-6145-4f93-8779-fe2bd2816c38n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 22:04   ` Bastien DUMONT
2021-05-16  1:58     ` Jeffrey T
2021-05-16  3:34     ` Jeffrey T
     [not found]       ` <26bec817-c8b4-4d63-ad5d-436aa281c0d7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-16 16:53         ` Bastien DUMONT
2021-05-19  2:21           ` Jeffrey T
     [not found]             ` <f787dab5-f3ce-41cf-815c-21f24727b781n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-19  7:54               ` Bastien DUMONT
2021-05-21  2:19                 ` Jeffrey T
     [not found]                   ` <deac7562-7f50-4699-9cc6-90a0de0d1b3bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-21  6:00                     ` Bastien DUMONT
2021-05-25 21:27                       ` Jeffrey T
2021-07-19 18:48                 ` Jeffrey T
     [not found]                   ` <7c5a2709-9b84-40b4-a77e-bd3dc5acb50cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-20 16:19                     ` John MacFarlane
     [not found]                       ` <m27dhl5568.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-07-20 17:44                         ` Jeffrey T
     [not found]                           ` <daaa9fdd-787c-4a51-bde0-c307396fd835n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-02  9:59                             ` Bastien DUMONT
2021-08-02 14:25                     ` Bastien DUMONT
2021-05-15 23:53   ` John MacFarlane
     [not found]     ` <m2k0nzmu47.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-16  2:05       ` Jeffrey T
2021-05-16  2:37       ` Jeffrey T
     [not found]         ` <b1d2d845-7dd8-4b3d-a059-9562bfb89d2fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-16 19:41           ` John MacFarlane [this message]

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=m2tun2fou5.fsf@MacBook-Pro.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=jefftreistman-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).