I use zotero and export to bibtex; then pandoc-citeproc runs over the references. I usually thought everything works well, until editors and supervisors complained about the incorrect citation style.
To make it compliant with APA, for now I run pandoc with `--biblatex` command so that it turns the [@cite1234] into latex citations, and then compile it with latexmk. Luckily, there is shell scripts to take care of that, so my workflow does not change too much. I just cannot use the word-output 'correctly' anymore then. On Fri, 2017-10-06 at 10:51 -0400, Sebastian Karcher wrote: > what reference manager are you using? Pandoc? E.g. in Zotero that > whole idea doesn't exist. You'd have to write out the narrative > reference in the text. Which has its own downsides, e.g. won't adapt > to et al. rules if the citation moves. > > I do think we'll need to handle this. It's one of the most frequent > complaints on Zotero and as Malte notes, it cause reference managers > that try to implement "narrative" citations to render incorrect > citations. > > Since it's a relative big change, I'd not expect this to happen fast, > though. > > > On Fri, Oct 6, 2017 at 10:46 AM, Malte Roedl <malte.ro...@postgrad.mb > s.ac.uk> wrote: > > Thanks for your quick reply, Bruce. > > > > I have created a github issue, but I could unfortunately not tag it > > as > > "wontfix" myself. > > > > https://github.com/citation-style-language/schema/issues/140 > > > > In my case, I will probably use latex (biblatex-apa) for this, as > > the > > journal is very picky about their citations. > > > > In case anyone is interested, another option to solve this is to > > use > > and="symbol" and use a regex for post-processing. > > This one works: > > "([&])(?=\s+(?:[\w-]+ ){1,3}[(])" -> "and" > > (unless there are punctuation characters in between the ampersand > > and > > the year, e.g. for first names, or there is random ampersands > > followed > > by brackets in the text) > > > > On Fri, 2017-10-06 at 10:31 +0000, Bruce D'Arcus wrote: > > > CSL has no concept of a "narrative citation," which would explain > > why > > > there's no way to distinguish formatting based on it. > > > There's been discussions about it, but am not remembering where > > we > > > ended up. > > > If we don't already have it, we should have a general issue > > ticket on > > > GitHub for the broader feature, and include a note about this > > > particular detail there. > > > Even if we label it "won't fix," at least we have the > > documentation > > > in one place. > > > > > > On Fri, Oct 6, 2017, 5:44 AM Malte Roedl <malte.ro...@postgrad.mb > > s.ac > > > .uk> wrote: > > > > Hello everyone, > > > > > > > > according to the APA style guidelines, which have many > > adoptions in > > > > various CSL-styles, it is mandatory to have 'and' connecting > > > > authors in > > > > narrative, and '&' connecting authors in parenthetical > > > > citations[1]. > > > > > > > > None of the styles I tried were accommodating for this rule. > > > > > > > > So then I've tried to build a if-else-control structure to > > identify > > > > whether it is a narrative or a parenthetical citation, but it > > seems > > > > that the processor would do that automatically by using > > "prefix" > > > > and > > > > "suffix"? > > > > Is there any way to identify in the csl-file what type of > > citation > > > > is > > > > calling the evaluation? > > > > Or even better, is there already an existing style that > > > > accommodates > > > > for my issue (I could not find one, but that may be because of > > very > > > > vague and ubiquitous search terms). > > > > > > > > Many thanks! > > > > Malte > > > > > > > > > > > > [1] e.g. https://en.wikipedia.org/wiki/APA_style#In-text_citati > > ons > > > > ------------------------------------------------------------- > > ---- > > > > ------------- > > > > Check out the vibrant tech community on one of the world's most > > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > > > > xbiblio-devel mailing list > > > > xbiblio-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > > > > > > --------------------------------------------------------------- > > ---- > > > ----------- > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > xbiblio-devel mailing list > > > xbiblio-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > > ----------------------------------------------------------------- > > ------------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > xbiblio-devel mailing list > > xbiblio-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > > > > ------------------------------------------------------------------- > ----------- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > xbiblio-devel mailing list > xbiblio-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
