From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-cite and org-citeproc
Date: Thu, 02 Apr 2015 20:26:38 +0100 [thread overview]
Message-ID: <olusiciwcup.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87wq1uef9f.fsf@berkeley.edu
Hi,
Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> Hi Eric and all,
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Wednesday, 1 Apr 2015 at 08:49, Andreas Leha wrote:
>>
>> [...]
>>
>>> I am a happy biblatex user for all my 'own' documents. But (as was
>>> mentioned previously) scientific journals that accept latex submissions
>>> will require bibtex and won't support biblatex. So, I'd say that one of
>>> the other methods (preferably bibtex) is still necessary.
>>
>> Ahhh, yes, I'd forgotten that journals expect bibtex. This is a key
>> requirement for me as well therefore.
>
> Can someone suggest how a parenthetical citation with common prefix and
> suffix data, like
>
> [(cite): For more on this topic, see:; @Work1 for a review; @Work2;
> and references therein.]
>
> should map to plain BibTeX? Maybe there is no general answer to this
> question, but what would a reasonable default be? Maybe this?
>
> (For more on this topic, see: \cite{Work1} for a review, \cite{Work2},
> and references therein.)
>
> That is, just place the prefix and suffix data in the surrounding text,
> inserting commas after the part for each individual work, and wrapping
> the whole thing in parentheses?
>
To me that seems a reasonable thing to do. At least I would write it
probably in such a way.
Depending on the citation style ("author, year") I might add a comma
after the citation, so that it becomes
(For more on this topic, see: Max Mustermann, 2015, for a review,
The Internet Consortium, 2014, and references therein.)
compared to
(For more on this topic, see: Max Mustermann, 2015 for a review,
The Internet Consortium, 2014 and references therein.)
But:
- I am no native English speaker and comma placement in English
is very unclear to me
- my citation requirements are quite low, I guess...
Best,
Andreas
next prev parent reply other threads:[~2015-04-02 19:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 18:53 org-cite and org-citeproc Richard Lawrence
2015-03-31 8:16 ` Eric S Fraga
2015-03-31 19:13 ` Richard Lawrence
2015-03-31 19:34 ` Nick Dokos
2015-03-31 20:29 ` Thomas S. Dye
2015-03-31 21:57 ` Richard Lawrence
2015-04-01 0:41 ` Thomas S. Dye
2015-04-01 15:42 ` Richard Lawrence
2015-04-01 19:41 ` Thomas S. Dye
2015-04-02 15:57 ` Richard Lawrence
2015-04-02 16:45 ` Thomas S. Dye
2015-03-31 21:12 ` Eric S Fraga
2015-04-01 7:49 ` Andreas Leha
2015-04-02 14:29 ` Eric S Fraga
2015-04-02 15:11 ` Richard Lawrence
2015-04-02 19:26 ` Andreas Leha [this message]
2015-03-31 22:03 ` Rasmus
2015-04-01 14:39 ` Richard Lawrence
2015-04-02 0:08 ` Rasmus
2015-04-02 15:26 ` Richard Lawrence
2015-04-02 15:51 ` Aaron Ecay
2015-04-02 17:38 ` Richard Lawrence
2015-04-06 18:51 ` Richard Lawrence
2015-06-16 19:36 ` Matt Price
2015-06-18 22:44 ` Richard Lawrence
2015-04-02 19:17 ` Rasmus
2015-04-03 2:56 ` Richard Lawrence
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=olusiciwcup.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.