From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc/citeproc issues: multiple bibliographies, nocite, citeonly
Date: Tue, 23 Nov 2010 11:02:11 -0800 [thread overview]
Message-ID: <20101123190210.GA16682@protagoras.phil.berkeley.edu> (raw)
In-Reply-To: <68cb6920-d51b-4139-913b-4ca4e96e160c-LFpOzkg5VSKSsatCSt0dimB/v6IoIuQBVpNB7YpNyf8@public.gmane.org>
+++ Bruce [Nov 23 10 10:39 ]:
>
>
> On Nov 23, 5:04 am, Nathan Gass <xa...-8UOIJiGH10pyDzI6CaY1VQ@public.gmane.org> wrote:
> > On 23.11.10 07:30, John MacFarlane wrote:
> >
> > > +++ Andrea Rossato [Nov 23 10 00:21 ]:
> > >> On Sun, Nov 21, 2010 at 11:32:29AM -0800, John MacFarlane wrote:
> >
> > >> What about parsing the markdown text for the reference field, if
> > >> present read the source file with the bibliographic data and then
> > >> parse the actual markdown text?
> >
> > > This could be done, but there'd be a significant performance
> > > penalty, so I'd rather avoid it.
> >
> > Do you have any benchmarks for pandoc? Performance seems to be a very
> > important concern for you, while in my usage it never was an issue. Of
> > course I neither have large documents to parse nor use pandoc in any
> > high-traffic web environment, but I would be interested in which region
> > pandoc currently is and how big this penalties are compared to that.
> >
> > >> There would be also some specific needs for bibliographic formatting
> > >> to be taken into account, like second field alignment or per-author
> > >> listing. See more about it here:
> > >>http://citationstyles.org/downloads/specification.html#id73
> >
> > >> I must admit I didn't have yet the time to dig into those issues and
> > >> I'd prefer to leave them for future enhancements. I think we should
> > >> focus on getting the citation part right, first, since it involves
> > >> syntax modification. The bibliography, instead, is a matter which does
> > >> not affect the way documents are written.
> >
> > > Yes, it seems fine to wait on refining the formatting of the
> > > bibliography. But we ought to settle the issues above about how
> > > a writer indicates where the bibliography goes, what its source
> > > is, etc.
> >
> > For whats it worth, in my opinion the formatting of the bibliography
> > belongs into the style, or some separate pandoc configuration, and not
> > in the document itself.
>
> FWIW from the CSL perspective, there are some areas over overlap
> between the domain of CSL and the domain of, say, a document styling
> system (line-spacing, some font details, even whether you call a
> reference list a "Bibliography" or "Works Cited"). We cover what we
> can (say line spacing between bib entries), but defer otherwise.
>
> As a user of pandoc particularly interested in(X)HTML, I'd consider it
> valuable at least if the bib was wrapped in a div that I can style.
My current plan will make this happen.
The plan is to introduce a new Bibliography block element. This will carry
information about the bibliography source file, excludes & includes (see
Andrea's earlier message), and a formatted Block list produced by citeproc.
Writers can do what they like with it. If the writer is producing latex using
natbib, for example, it will just write "\bibliography{foo}" or something like
that. The default, though, will be to write the formatted blocks produced
by citeproc. In the HTML writer, these can be put in a div with class
"bibliography".
John
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.
prev parent reply other threads:[~2010-11-23 19:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 19:32 John MacFarlane
[not found] ` <20101121193229.GB25657-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-21 21:46 ` Bruce
[not found] ` <0ebd5c02-7660-4f20-8da0-ee93a034850a-bhUrjG+0PUy4o898BNfOI1YGCWtFR9XvQQ4Iyu8u01E@public.gmane.org>
2010-11-22 16:02 ` Nathan Gass
[not found] ` <4CEA93FE.8070502-8UOIJiGH10pyDzI6CaY1VQ@public.gmane.org>
2010-11-22 16:36 ` John MacFarlane
2010-11-21 23:26 ` Tillmann Rendel
[not found] ` <4CE9AABB.1070705-jNDFPZUTrfTbB13WlS47k8u21/r88PR+s0AfqQuZ5sE@public.gmane.org>
2010-11-24 1:29 ` Nathan Gass
[not found] ` <4CEC6A61.1000309-8UOIJiGH10pyDzI6CaY1VQ@public.gmane.org>
2010-11-24 3:33 ` John MacFarlane
[not found] ` <20101124033315.GC25133-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-24 5:06 ` John MacFarlane
[not found] ` <20101124050631.GA28014-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-24 20:51 ` Andrea Rossato
[not found] ` <20101124205114.GB23284-j4W6CDmL7uNdAaE8spi6tJZpQXiuRcL9@public.gmane.org>
2010-11-25 7:42 ` John MacFarlane
[not found] ` <20101125074240.GC12387-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-25 8:09 ` Andrea Rossato
[not found] ` <20101125080907.GD23284-j4W6CDmL7uNdAaE8spi6tJZpQXiuRcL9@public.gmane.org>
2010-11-27 15:23 ` John MacFarlane
[not found] ` <20101127152352.GB535-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-27 19:01 ` Andrea Rossato
[not found] ` <20101127190139.GE32527-j4W6CDmL7uNdAaE8spi6tJZpQXiuRcL9@public.gmane.org>
2010-11-27 19:34 ` John MacFarlane
2010-11-29 23:45 ` Nathan Gass
[not found] ` <4CF43B30.9050400-8UOIJiGH10pyDzI6CaY1VQ@public.gmane.org>
2010-12-01 3:25 ` John MacFarlane
[not found] ` <20101201032556.GA28952-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-12-01 13:03 ` Andrea Rossato
[not found] ` <20101201130317.GI10338-j4W6CDmL7uNdAaE8spi6tJZpQXiuRcL9@public.gmane.org>
2010-12-01 16:00 ` John MacFarlane
[not found] ` <20101201160037.GC3038-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2017-07-27 8:18 ` siram.berlin-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <9802cbc1-fa98-43f9-b42b-b7781066f375-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-30 20:57 ` John MacFarlane
2020-11-19 13:14 ` Pranesh Prakash
[not found] ` <19e3868a-6e4e-42a3-8636-75a95e925946n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-20 8:50 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
2010-11-22 23:21 ` Andrea Rossato
[not found] ` <20101122232135.GG13438-j4W6CDmL7uNdAaE8spi6tJZpQXiuRcL9@public.gmane.org>
2010-11-23 6:30 ` John MacFarlane
[not found] ` <20101123063011.GD8500-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2010-11-23 10:04 ` Nathan Gass
[not found] ` <4CEB91AA.5050801-8UOIJiGH10pyDzI6CaY1VQ@public.gmane.org>
2010-11-23 15:58 ` John MacFarlane
2010-11-23 18:39 ` Bruce
[not found] ` <68cb6920-d51b-4139-913b-4ca4e96e160c-LFpOzkg5VSKSsatCSt0dimB/v6IoIuQBVpNB7YpNyf8@public.gmane.org>
2010-11-23 19:02 ` John MacFarlane [this message]
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=20101123190210.GA16682@protagoras.phil.berkeley.edu \
--to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).