[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Citations, continued
From: |
Rasmus |
Subject: |
Re: [O] Citations, continued |
Date: |
Tue, 10 Feb 2015 11:36:18 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Nicolas Goaziou <address@hidden> writes:
>> So, the (opinionated) useful defaults in biblatex are:
>> cite(s), parencite(s), footcite(s), texcite(s), fullcite,
>> footfullcite, nocite
>
> Isn't footcite/footfullcite a choice made at the document's level
> instead of per citation? If that's the case, it could go in a keyword,
> e.g.,
>
> #+LATEX_CITATION: :style footcite
I guess you'd distinguish between fullcite and footfullcite then? I have
only ever used fullcite for illustrative purposes, e.g. demonstrating the
citation style. And I guess footcite is an alternative to
{textcite, parencite}.
>> Citation types for extracting parts:
>> citeauthor, citetitle, citeyear, citedate, citeurl,
>
> Can't this be attached to the key, as a filter?
Do you mean an ox-filter here or the slash "/"? It's more complex and but
probably also prettier. "address@hidden/author]" looks nice. I haven't seen
"/" in
bibtex keys.
In any case, an ox-filter is no good. You sometimes need it for
constructing sentences, e.g. I like to keep out the year when it's obvious
to ease reading::
A (Y) showed foo. Note that A assumed that ...
> Then what about
>
> [cite:command: common pre; pre1 @key1 post1; ... ; common post]
Could work.
> where command is anything matching is constituted of alphanumeric
> characters only (this is just a guess, a proper regexp is yet to be
> determined).
>
> LaTeX back-end will see "command" and less advanced back-ends "cite", so
> that the same document can be exported through multiple back-ends.
OK. But what if I want to use, say, my "genitive" citation, "A's (Y)", in
html? This is perhaps a question of whether we'll manage to find a tool
to handle this for us, or we'll have to do it lisp.
> However, this syntax doesn't handle in-text citation for other back-ends
> than LaTeX. Hence the address@hidden post] proposal, or even @key [post],
> which
> I find more elegant than
>
> [citet: ...] / [citep: ...]
So address@hidden post] is equivalent to [cite:default_command: @key post].
Does
it scale to an arbitrary length of keys, e.g. address@hidden post1; ⋯; @kN
postN]?
Could [@: pre1 @k1 post1; ⋯; preN @kN postN] be used if you need prenotes?
Or only [cite:⋯].
Would you "expand" all short citations in the early ox parsing?
I don't care for "@key [post]"
>> The default bibtex.el style generates keys like "%A%y:%t", so I think ":"
>> is no good, appealing as it is.
>
> Then "/" (filter) or "|" (pipe).
Why do you write "filter" after the slash? Am I supposed to think about
ox-filters?
—Rasmus
--
Governments should be afraid of their people
- Re: [O] Citations, continued, (continued)
- Re: [O] Citations, continued, Nicolas Goaziou, 2015/02/08
- Re: [O] Citations, continued, Rasmus, 2015/02/08
- Re: [O] Citations, continued, Nicolas Goaziou, 2015/02/08
- Re: [O] Citations, continued, Rasmus, 2015/02/09
- Re: [O] Citations, continued, Nicolas Goaziou, 2015/02/08
- Re: [O] Citations, continued, Rasmus, 2015/02/08
- Re: [O] Citations, continued, John Kitchin, 2015/02/09
- Re: [O] Citations, continued, Nicolas Goaziou, 2015/02/10
- Re: [O] Citations, continued, Rasmus, 2015/02/10
- Re: [O] Citations, continued, Nicolas Goaziou, 2015/02/10
- Re: [O] Citations, continued,
Rasmus <=
- Re: [O] Citations, continued, Andreas Leha, 2015/02/10
- Re: [O] Citations, continued, John Kitchin, 2015/02/10
- Re: [O] Citations, continued, Rasmus, 2015/02/10
- Re: [O] Citations, continued, John Kitchin, 2015/02/10
- Re: [O] Citations, continued, Richard Lawrence, 2015/02/10
- Re: [O] Citations, continued, Stefan Nobis, 2015/02/10
- Re: [O] Citations, continued, Richard Lawrence, 2015/02/10
- Re: [O] Citations, continued, Stefan Nobis, 2015/02/11
- Re: [O] Citations, continued, Richard Lawrence, 2015/02/11
- Re: [O] Citations, continued, Matt Price, 2015/02/12