Closed katrin-berkenbusch closed 2 years ago
Any chance of someone to look into this issue within the next week or so? maybe @richardmansfield ?
For once it was easy! It's running now, and will be in dragonflyscience/dragonverse-22.04:2022-08-02 soon.
On Tue, 2 Aug 2022 at 15:43, Katrin Berkenbusch @.***> wrote:
Any chance of someone to look into this issue within the next week or so? maybe @richardmansfield https://github.com/richardmansfield ?
— Reply to this email directly, view it on GitHub https://github.com/dragonfly-science/mpi-latex-templates/issues/40#issuecomment-1201980531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACXXTAG4ZQ2GGJHYMMFNJDVXCKOPANCNFSM54QMOHPA . You are receiving this because you were mentioned.Message ID: @.***>
Out of curiosity:
@richardmansfield , does the sortcites=false
approach mean that the user is responsible for putting the citations into chronological order in their code?
@katrin-berkenbusch I assume this was another of the ongoing minor tweaks that MPI seem to be requesting each report submission (i.e., rather than defining the required format completely once and for all?)
@dmiddleton Hi there, no, having the references in consecutive order in the text has remained consistent and was included again in the MPI template update this year.
awesome.
On 2/08/2022, at 6:42 AM, Richard Mansfield @.***> wrote:
For once it was easy! It's running now, and will be in dragonflyscience/dragonverse-22.04:2022-08-02 soon.
On Tue, 2 Aug 2022 at 15:43, Katrin Berkenbusch @.***> wrote:
Any chance of someone to look into this issue within the next week or so? maybe @richardmansfield https://github.com/richardmansfield ?
— Reply to this email directly, view it on GitHub https://github.com/dragonfly-science/mpi-latex-templates/issues/40#issuecomment-1201980531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACXXTAG4ZQ2GGJHYMMFNJDVXCKOPANCNFSM54QMOHPA . You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
@dmiddleton Hi there, no, having the references in consecutive order in the text has remained consistent and was included again in the MPI template update this year.
Thanks - looking back I see it was the update to 22.04 when this changed to alphabetical sorting in the FAR example. Good spotting!
So does "consecutive" mean "chronological" here, or not? In my mind those words have different meanings. Damn, github lost one of my email replies.
So does "consecutive" mean "chronological" here, or not? In my mind those words have different meanings. Damn, github lost one of my email replies.
That was my interpretation. But I may be wrong ... @katrin-berkenbusch will confirm!
Yes,
Sorry, I should’ve been clearer, “chronological" is the word.
Here’s an example of how references look in a FAR PDF at the moment: "Brander et al. 2013, Jutfelt et al. 2018, Lefevre 2016, Lefevre et al. 2018”, but they should be listed in this order: "Brander et al. 2013, Lefevre 2016, Jutfelt et al. 2018, Lefevre et al. 2018”.
[Hm, that’s a tricky example with the alphabetical 2018 reference-ordering thrown in, although it seems to apply automatically if the bib reference is entered correctly].
On 3/08/2022, at 12:00 AM, David Middleton @.***> wrote:
So does "consecutive" mean "chronological" here, or not? In my mind those words have different meanings. Damn, github lost one of my email replies.
That was my interpretation. But I may be wrong ... @katrin-berkenbusch will confirm!
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.
The sample doc works for me now, finally. @katrin-berkenbusch, give dragonflyscience/dragonverse-22.04:2022-08-04
a try when you're ready.
Weirdly enough, APA is using slightly different sorting orders for citations and the reference list. The very newest biblatex now has some support for that. I tried to backport that stuff to the version in ubuntu 22.04, but it was just too hard :(. Instead I have overridden \printbibliography
. It works on the sample FAR but might have some side effects I guess.
Thanks @richardmansfield that sounds great, I'll give it a try. Hopefully I'll catch any side effects. :-)
it worked like a treat, I haven't found any side effects yet. Thank you @richardmansfield
Oh sorry, yes I guess I just removed sorting. That's just me not realising that consecutive == chronological.
On Tue, 2 Aug 2022 at 16:55, David Middleton @.***> wrote:
Out of curiosity:
@richardmansfield https://github.com/richardmansfield , does the sortcites=false approach mean that the user is responsible for putting the citations into chronological order in their code?
@katrin-berkenbusch https://github.com/katrin-berkenbusch I assume this was another of the ongoing minor tweaks that MPI seem to be requesting each report submission (i.e., rather than defining the required format completely once and for all?)
— Reply to this email directly, view it on GitHub https://github.com/dragonfly-science/mpi-latex-templates/issues/40#issuecomment-1202016642, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACXXTEB6N3BKDPOV3PCAN3VXCS5FANCNFSM54QMOHPA . You are receiving this because you were mentioned.Message ID: @.***>
It seems that
\citep{}
puts the references in alphabetical not consecutive order in the PDF. This change may be due to APA style, but needs to be swapped to have them in consecutive order.