Re: Citations, continued

[Erik Hetzner <egh@e6h.org>]

Hi Richard,

On Tue,  3 Feb 2015 at 08:11:19 PST,
Richard Lawrence <richard.lawrence@berkeley.edu> wrote:
> 

[…]

> 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?

I’m not entirely sure what you mean. The authors of citeproc have come
up with a huge number of styles which seem to satisfy people’s needs.
What appears in the in-text citation is configurable, see:

  http://citationstyles.org/downloads/specification-csl101-20120903.html#citation

> The +title@doe 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).  

The only advantage of it is that it doesn’t break existing cite keys,
which can contain :, and it is closer to existing syntax. But for the
time being it’s something I wouldn’t worry about.

> 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.

I concentrated on getting the parser to recognize valid citations
first. I have now finished this part (excepting any bugs, of course :)
and will need to add code to generate a proper parse tree. Then it can
be integrated into org-element.el.

best, Erik
--
Sent from my free software system <http://fsf.org/>.