public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jeffrey T <jefftreistman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: LaTeX footnote citations parentheses
Date: Tue, 25 May 2021 14:27:16 -0700 (PDT)	[thread overview]
Message-ID: <dd806b11-4b4f-46e7-9acc-7233828107adn@googlegroups.com> (raw)
In-Reply-To: <YKdMfbS2kSXj+hIJ@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 9079 bytes --]

Sounds good!

Thank you again for all your help! 

On Friday, May 21, 2021 at 2:01:04 AM UTC-4 Bastien Dumont wrote:

> Hi,
>
> To see wether the script will work or not, you can convert your file or a
> sample to Pandoc Markdown. The citation key must always appear inside 
> brackets,
> wether it be in a footnote or not. So in the following example:
>
> pandoc -t markdown -f latex <<< '\cite{key} \autocite{key}
> \footnote{\cite{key} \autocite{key}}'
>
> [@key] [@key] [^1]
>
> [^1]: [@key] [@key]
>
> you can see that all the conditions are met. Pandoc makes no difference 
> between
> \cite and \autocite.
>
> As long as it works, you don't have to modify the filter. Changing "cite" 
> to
> "autocite" won't do anything, it's only an arbitrary variable name that 
> point
> to an object of type "Cite" in Pandoc's internal representation of the
> document.
>
> The script is only concerned with removing parentheses around citations. In
> order to convert your footnotes to endnotes and to reset the numeration, 
> you
> will have to use Word's utilities. To my knowledge, Pandoc itself makes no
> distinction between footnotes and endnotes and handles notes as footnotes 
> by
> default.
>
>
> Le Thursday 20 May 2021 à 07:19:55PM, Jeffrey T a écrit :
> > Hi Bastien,
> > 
> > Wonderful! The good news is your script appears to work if I use 
> \autocite in
> > body or \autocite in footnotes which is actually perfect because I have 
> a few
> > other documents that use this citation method! That said, assuming I 
> need to
> > make the change from \cite to \autocite for footnotes, I would change 
> Cite =
> > function(cite) to Cite = function(autocite) in the Lua script?
> > 
> > Meanwhile, this script has been extremely helpful but I wonder if it can 
> be
> > extended to document class "reports" with both chapters and endnotes? 
> I'm on
> > two grant projects with multiple faculty members and this Lua script 
> could be
> > extremely helpful assuming we need to convert our work into a Word 
> document.
> > I've attached a minimal working example of a report. Unfortunately the 
> Pandoc
> > conversion doesn't quite turn out as desired: (1) it doesn't appear to 
> read the
> > footnotes as endnotes, and (2) the number of endnotes doesn't restart 
> after a
> > new chapter. Being new to Pandoc I'm not sure where the problem lies? I 
> suppose
> > it's not a major issue because we could always use your script on each
> > individual LaTeX chapter, then piece them all together manually into 
> Word?
> > 
> > On Wednesday, May 19, 2021 at 3:55:21 AM UTC-4 Bastien Dumont wrote:
> > 
> > Unless you modify it in order to produce nuclear bombs, do as you wish!
> > However, I must warn you that I adapted it to work with the use case
> > that you provided only: there are no checks that would prevent it to run
> > into errors if other conditions are met. Ensure that you stick to \cite
> > in footnotes and \autocite in the body text, or modify the script
> > accordingly.
> > 
> > Le Tuesday 18 May 2021 à 07:21:54PM, Jeffrey T a écrit :
> > >
> > > Hi Bastien,
> > >
> > > Thank you very much! This script with Pandoc is an absolute game 
> changer
> > in
> > > terms of my workflow! Do you mind if I share your script with others?
> > >
> > > Again, thank you!
> > > On Sunday, May 16, 2021 at 12:54:24 PM UTC-4 Bastien Dumont wrote:
> > >
> > > You're welcome, I already had done much of the work for myself, so I am
> > > happy if
> > > it could be useful for others as well.
> > >
> > > I had'nt anticipatĕd that you would also use \autocite in the body. I
> > > restricted
> > > the scope of the filter to the footnotes, so you should not have errors
> > > anymore
> > > provided that all your use cases are documented in the text file. I
> > > supposed that
> > > you don't want the output of \autocite to be changed. Please try the 
> file
> > > attached.
> > >
> > > Le Saturday 15 May 2021 à 08:34:22PM, Jeffrey T a écrit :
> > > > Hi Bastien,
> > > >
> > > > Oh my, thank you very much for taking the time to assist! I 
> downloaded
> > > your Lua
> > > > filter (I didn't realize that filters were possible with Pandoc!) and
> > > included
> > > > it in my Pandoc command:
> > > >
> > > > pandoc --citeproc --lua-filter=remove-parentheses-from-cite.lua
> > Test.tex
> > > > --bibliography=testref.bib --csl=
> > > > chicago-fullnote-bibliography-short-title-subsequent.csl -o test.docx
> > > >
> > > > It worked perfectly for the \cite commands contained within 
> \footnote.
> > > > Unfortunately the remainder of my book manuscript uses \autocite for
> > > references
> > > > outside of footnotes. When \autocite is included, I received an error
> > > message:
> > > > "bad argument #1 to 'gsub' (string expected, got nil)"
> > > >
> > > > If helpful, I've attached the test .tex file I'm using? Your 
> assistance
> > > is much
> > > > appreciated!
> > > >
> > > >
> > > > On Saturday, May 15, 2021 at 6:05:21 PM UTC-4 Bastien Dumont wrote:
> > > >
> > > > I had a similar problem that I resolved with the attached Lua filter
> > > > (slightly
> > > > modified to adapt it to your needs). I hope that it will work for 
> you.
> > > > Simply
> > > > call it after --citeproc.
> > > >
> > > > Note that it will throw an error if you have \cite commands outside
> > > > footnotes.
> > > > If that it the case, please let me know.
> > > >
> > > > Le Saturday 15 May 2021 à 12:13:37PM, Jeffrey T a écrit :
> > > > >
> > > > > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > > > To view this discussion on the web visit 
> https://groups.google.com/d/
> > > msgid/
> > > > pandoc-discuss/26bec817-c8b4-4d63-ad5d-436aa281c0d7n%
> 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/f787dab5-f3ce-41cf-815c-21f24727b781n%
> 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/deac7562-7f50-4699-9cc6-90a0de0d1b3bn%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/dd806b11-4b4f-46e7-9acc-7233828107adn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 13829 bytes --]

  reply	other threads:[~2021-05-25 21:27 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 [this message]
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

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=dd806b11-4b4f-46e7-9acc-7233828107adn@googlegroups.com \
    --to=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).