Hi all (in particular Hans and Alan...),
I'm finishing a book project where I'm using the new bibliographic
system. Everything is working as it should, but I have two problems with
line breaks:
1. Page numbers in ranges are separated by an n-dash (as in: 234–567).
It looks as though ConTeXt
The point is not that I am without options for a practical solution here.
My point is that the difference between \typebuffer and \typefile breaks the
strict and so much appreciated congruence between like macro calls.
Therefore my post must rather be seen as a plea to the maintainer(s) of these
On 04/24/2016 10:31 AM, dr. Hans van der Meer wrote:
> Why is there a difference in syntax between typing buffers and typing files?
> For files enclosure in {} for buffers in [], for files optional
> parameters, for buffers not.
> Is it possible to make the syntax of these two the same, because
Dear list,
I have the following sample:
\startbuffer[buffer:inside]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\setupbodyfont[mainface, 17pt]
\starttext
\input zapf
\stoptext
\stopbuffer
\starttext
\typesetbuffer[buffer:inside]
Why is there a difference in syntax between typing buffers and typing files?
For files enclosure in {} for buffers in [], for files optional parameters, for
buffers not.
Is it possible to make the syntax of these two the same, because their usage
parallels each other?
Example code:
