On 12/8/2018 14:50, Alan Braslau wrote:
On Sat, 8 Dec 2018 12:43:34 -0500 Rik Kabel
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
The purpose is to reduce entry effort, prevent simple errors, ensure consistency across instances in the same and additional documents, and encourage reuse. Or are you suggesting that a document like the paper I cited does not benefit from a bibliographic support subsystem? -- Rik