Re: [org-cite, oc-csl] print_bibliography options

2021-05-31 Thread Bruce D'Arcus
On Mon, May 31, 2021 at 2:11 PM András Simonyi  wrote:
>
> Dear All,
>
> I think a useful default/baseline for handling the occurrence of
> multiple #+print_bibliography keywords  would be to implement the
> "chapter use case", which, for each #+print_bibliography, would
> collect only the citations occurring after to previous
> #+print_bibliography (if there is one) and before the current one, and
> print out an independent bibliography corresponding to the citations.
> All citations in this section would refer to this bibliography, and
> would be disambiguated accordingly.

This would have two advantages:

1) add support for the "per section/chapter" use case András notes to oc-csl
2) avoid duplicate bibliographies in the example I raised; what we
might call "multi-section bibliography" use case; then if and when
citeproc-el adds support this, the documents would be gracefully
enhanced

Bruce



Re: [org-cite, oc-csl] print_bibliography options

2021-05-31 Thread András Simonyi
Dear All,

I think a useful default/baseline for handling the occurrence of
multiple #+print_bibliography keywords  would be to implement the
"chapter use case", which, for each #+print_bibliography, would
collect only the citations occurring after to previous
#+print_bibliography (if there is one) and before the current one, and
print out an independent bibliography corresponding to the citations.
All citations in this section would refer to this bibliography, and
would be disambiguated accordingly.

This could be implemented without any dedicated support on the
processor's side, the basic processor could support this as well.
Sectioned bibliographies, on the other hand, seem to be more
complicated, and require processor-side support.

best regards,
András



Re: [org-cite, oc-csl] print_bibliography options

2021-05-29 Thread Nicolas Goaziou
"Bruce D'Arcus"  writes:

> So two duplicate lists.
>
> Does that clarify?

Indeed, thanks.

> The other common case I am familiar with is a bibliography per section
> of a document.
>
> It may not be practical to do anything other than current behavior,
> but I was hoping some biblatex experts might have some thoughts.
>
> And, of course, wanting to flag this for András to think about, since
> ideally citeproc-el would support this.

OK. I'll let experts discuss the topic.

Regards,



Re: [org-cite, oc-csl] print_bibliography options

2021-05-29 Thread Bruce D'Arcus
On Sat, May 29, 2021 at 11:15 AM Nicolas Goaziou  wrote:
>
> Hello,
>
> "Bruce D'Arcus"  writes:
>
> >> Bibliography is printed using "\printbibliography" command.  Additional
> >> options may be passed to it through a property list attached to the
> >> "print_bibliography" keyword.  E.g.,
> >>
> >>#+print_bibliography: :section 2 :heading subbibliography
>
> > I don't believe citeproc-el currently supports any of these features,
> > and it looks like the citeproc-el API doesn't even have an optional
> > parameter to put details like these.
> >
> > As a consequence, if one adds an example like the above, so that one
> > has two print_bibliography lines, one will get two, duplicate
> > bibliography lists outside of oc-biblatex.
>
> I don't understand how you reach that consequence… If the citation
> processor does not understand the properties, it simply ignores them,
> but obeys to "print_bibliography" directive anyhow.
>
> Have you tried it? I'm not sure to understand your concern.

Yes.

I think we're saying the same thing, but maybe I need to clarify the
implications better?

See below.

Let me illustrate with a full example, where the @einstein entry has a
"keyword" field of "primary."

The use case is a user wanting a bibliography with two sections, which
is a common case for this feature.

Note that I am unsure of the exact invocation to achieve this with
biblatex (as in, it's probably wrong), but I don't think that matters
to illustrate the point.

>
#+language: en
#+bibliography: test.bib
#+cite_export: csl

1. simple: [cite:@latexcompanion]
2. primary source: [cite:@einstein]
3. affixes: [cite/text:see @latexcompanion chapter 2 p.23]
4. quote, punctuation: “my quote” [cite/text/caps:@latexcompanion].

* Bibliography
** Primary Sources
#+print_bibliography: :keyword primary :title "Primary Sources"
** Secondary Sources
#+print_bibliography: :title "Secondary Source"
<

Here's the output from oc-csl:

>
1. simple: (Goossens, Mittelbach, and Samarin 1993)
2. primary source: (Einstein 1905)
3. affixes: (see Goossens, Mittelbach, and Samarin 1993, chaps. 2 p.23)
4. quote, punctuation: “my quote” (Goossens, Mittelbach, and Samarin
   1993).


1 Bibliography
══

1.1 Primary Sources
───

  Einstein, Albert. 1905. “Zur Elektrodynamik Bewegter Körper. (German)
  [on the Electrodynamics of Moving Bodies].” /Annalen Der Physik/ 322
  (10):891–921.

  Goossens, Michel, Frank Mittelbach, and Alexander Samarin. 1993. /The
  LaTeX Companion/. Reading, Massachusetts: Addison-Wesley.


1.2 Secondary Sources
─

  Einstein, Albert. 1905. “Zur Elektrodynamik Bewegter Körper. (German)
  [on the Electrodynamics of Moving Bodies].” /Annalen Der Physik/ 322
  (10):891–921.

  Goossens, Michel, Frank Mittelbach, and Alexander Samarin. 1993. /The
  LaTeX Companion/. Reading, Massachusetts: Addison-Wesley.
<

So two duplicate lists.

Does that clarify?

The other common case I am familiar with is a bibliography per section
of a document.

It may not be practical to do anything other than current behavior,
but I was hoping some biblatex experts might have some thoughts.

And, of course, wanting to flag this for András to think about, since
ideally citeproc-el would support this.

Bruce



Re: [org-cite, oc-csl] print_bibliography options

2021-05-29 Thread Nicolas Goaziou
Hello,

"Bruce D'Arcus"  writes:

>> Bibliography is printed using "\printbibliography" command.  Additional
>> options may be passed to it through a property list attached to the
>> "print_bibliography" keyword.  E.g.,
>>
>>#+print_bibliography: :section 2 :heading subbibliography

> I don't believe citeproc-el currently supports any of these features,
> and it looks like the citeproc-el API doesn't even have an optional
> parameter to put details like these.
>
> As a consequence, if one adds an example like the above, so that one
> has two print_bibliography lines, one will get two, duplicate
> bibliography lists outside of oc-biblatex.

I don't understand how you reach that consequence… If the citation
processor does not understand the properties, it simply ignores them,
but obeys to "print_bibliography" directive anyhow.

Have you tried it? I'm not sure to understand your concern.

Regards,
-- 
Nicolas Goaziou



[org-cite, oc-csl] print_bibliography options

2021-05-29 Thread Bruce D'Arcus
Nicolas, András,

I wanted to pull this example out from oc-biblatex for consideration in oc-csl:

On Tue, May 18, 2021 at 11:45 AM Nicolas Goaziou  wrote:

> Bibliography is printed using "\printbibliography" command.  Additional
> options may be passed to it through a property list attached to the
> "print_bibliography" keyword.  E.g.,
>
>#+print_bibliography: :section 2 :heading subbibliography
>
> Values including spaces must be surrounded with double quotes.  If you need
> to use a key multiple times, you can separate its values with commas, but
> without any space in-between:
>
>#+print_bibliography: :keyword abc,xyz :title "Primary Sources"

This is a great addition for that module, but I'm wondering what to do
with documents written using this in oc-csl.

I don't believe citeproc-el currently supports any of these features,
and it looks like the citeproc-el API doesn't even have an optional
parameter to put details like these.

As a consequence, if one adds an example like the above, so that one
has two print_bibliography lines, one will get two, duplicate
bibliography lists outside of oc-biblatex.

So two questions:

1. Do you have any interest in adding support for this in citeproc-el
at some point András?
2. Is the current behavior acceptable? If not, any better options? I'm
not sure there is, but thought I'd ask anyway. Biblatex users familiar
with this feature might have some ideas on this?

I guess I just want to call your attention to this, in the event you
had any thoughts on if and how to support this going forward.

Bruce