From: Alan Braslau <braslau.list@comcast.net>
To: Rik Kabel <context@rik.users.panix.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Issues using publications subsystem for non-bibliographic database
Date: Sat, 8 Dec 2018 12:50:09 -0700 [thread overview]
Message-ID: <20181208125009.3ebd1368@comcast.net> (raw)
In-Reply-To: <8eb8c7f4-6a69-05d9-b8a5-0813707a5dab@rik.users.panix.com>
On Sat, 8 Dec 2018 12:43:34 -0500
Rik Kabel <context@rik.users.panix.com> wrote:
> It is also quite
> useful in earlier stages of larger projects where it is important to
> document sources (for circulation copies) but one is not ready to tackle
> the design and generation of more formal backmatter.
In my incremental development, I place a bibliography at the end of a chapter, part, or even section - there is no need for this to be backmatter. Using modes, these then can remain or not be rendered as design advances.
Again, what is the point of pulling references if they do not refer to anything? In the Latex/bibtex workflow, the list is generated by bibtex, and this can, and does, lead to de-synchronization in a partial development process as you describe. Here, the list is generated and exists in lua, and we take great pains to insure that it remains synchronized.
Alan
___________________________________________________________________________________
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 19:50 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
2018-12-08 5:03 ` Alan Braslau
2018-12-08 17:43 ` Rik Kabel
2018-12-08 19:50 ` Alan Braslau [this message]
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=20181208125009.3ebd1368@comcast.net \
--to=braslau.list@comcast.net \
--cc=context@rik.users.panix.com \
--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).