Re: [O] Citations, continued

[Richard Lawrence]

Hi Erik and all,

Erik Hetzner <address@hidden> writes:

> On Mon,  2 Feb 2015 at 20:41:06 PST,
> Richard Lawrence <address@hidden> wrote:

>> The only reason I proposed anything else was that it seemed like other
>> people already know that they need more than the Pandoc syntax provides.
>> I think the main realistic cases are those where, in LaTeX, you'd use
>> commands like \citetitle, \citedate, or \citejournal -- citation
>> commands that pull in just a particular field from the reference,
>> because that is what the context around the citation requires.  I don't
>> see a way to do that in the Pandoc syntax.  (But am I missing
>> something?)  Hence my proposed field-selectors extension.
>
> If this is needed (and I still have a hard time seeing the use cases,
> but I am not an academic) perhaps it could mimic the address@hidden (suppress
> author) syntax already used in pandoc (e.g. address@hidden). But
> citeproc-js/hs only support suppress author or author only, so these
> would not work in a pandoc export, nor any other that might depend on
> citeproc-js.

Yes.  I'll have to take a look at the Pandoc citeproc code and see how
easy it would be to add support for something like this.  If there are
Org people that need citation types that select specific fields, I
imagine there are Pandoc people who do as well.  The ideal would be if
citeproc would take care of proper formatting of all such citation
types, given just an ordered list of the fields that should appear.  I
don't know if CSL supports this, though; do you?

The address@hidden syntax would work, but I don't personally think that's
any easier to read (or parse) than @doe:title, or @doe+title (which
actually is another option I had thought of, given the +/- syntax for
tag matching in Org).  

> Again, this is great. I really do appreciate your getting this
> proposal out there. I hope that I can finish porting my pandoc parser
> to elisp within a week or so, so we can have an implementation to
> start with.

Thanks for taking the first step on this!  I had a brief look at your
parser code when you posted it the other day.

I don't know if you are familiar with Org's parser, in org-element.el.
The important thing will be to have a parser for citations return a data
structure in the format used by org-element.  In the language of
org-element, I think a citation is an object (as opposed to an element).
I am somewhat (but not super-) familiar with org-element and Elisp, so
if you want some help with this, let me know.

Best,
Richard