From: Rik Kabel <context@rik.users.panix.com>
To: Alan Braslau <braslau.list@comcast.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Issues using publications subsystem for non-bibliographic database
Date: Fri, 7 Dec 2018 23:34:58 -0500 [thread overview]
Message-ID: <665d42dc-b0c8-1076-78f0-90e9a9244cb8@rik.users.panix.com> (raw)
In-Reply-To: <20181207205147.496f8a88@zoo>
On 12/7/2018 22:51, Alan Braslau wrote:
> You can place references rendered as you need, not necessarily in one
> single bibliography list, but they must be rendered somewhere,
> otherwise numbering and cross-referencing is meaningless. In the case
> of footnote references, each footnote contains a rendering (not a
> citation) of a fragment of the list.
>
> You are thinking too much in a standard frame, and I'm not sure what
> you want to accomplish.
>
> One "other use" case that I make is a catalog of hundreds of
> mesophases. I "cite" them and their various properties throughout the
> text, an my "list rendering" has become an index.
>
> Alan
>
I would like simply to prepare a paper structured like the one found at
https://tannerlectures.utah.edu/Greenblatt%20Lecture.pdf. There is no
biblography; there are bibliographic references in footnotes. There is
no interaction. The only cross-references are the footnote indices.
If I could in addition pull in blocks of text from a secondary database,
that is lagniappe. Neither function requires rendering in a separate
list or lists.
Certainly ConTeXt's bibliographic subsystem should be capable of
supporting such a basic format as that, but I can see no way to get it
to do so.
--
Rik
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-12-08 4:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 4:00 Rik Kabel
2018-12-07 22:19 ` Rik Kabel
2018-12-07 23:01 ` Alan Braslau
2018-12-08 3:36 ` Rik Kabel
2018-12-08 3:51 ` Alan Braslau
2018-12-08 4:34 ` Rik Kabel [this message]
2018-12-08 5:03 ` Alan Braslau
2018-12-08 17:43 ` Rik Kabel
2018-12-08 19:50 ` Alan Braslau
2018-12-08 20:11 ` Thomas A. Schmitz
2018-12-08 20:30 ` Alan Braslau
2018-12-08 20:11 ` Rik Kabel
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=665d42dc-b0c8-1076-78f0-90e9a9244cb8@rik.users.panix.com \
--to=context@rik.users.panix.com \
--cc=braslau.list@comcast.net \
--cc=ntg-context@ntg.nl \
/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).