I have set up:
\setuppublications[numbering=short]
\setupcite[short]
but the \cite commands show (Author, Year) and not the short code and the
\placepublications does not indent the entries enough, hence the item entry’s
first column (the short code) overlaps with the actual entry.
How do I
On 26 Aug 2014, at 10:34, Gerben Wierda gerben.wie...@rna.nl wrote:
I have set up:
\setuppublications[numbering=short]
\setupcite[short]
but the \cite commands show (Author, Year) and not the short code and the
\placepublications does not indent the entries enough, hence the item
While trying to make a longer document with ConTeXt I stumbled into a
strange error with the latest beta (I spotted it for the first time some
time ago). For the following file:
\setupinteraction[state=start,focus=standard]
\placebookmarks[part,chapter][part,chapter][number=no]
\starttext
Context is moving toward accepting XML input,
although the filtering process is necessarily
complex. But what is also needed is a version
of Context that produces well formed XML as an
output. That would be a step toward producing a
dual purpose document with Context, for print
and for e-book use.
Am 26.08.2014 um 17:07 schrieb john Culleton j...@wexfordpress.com:
Context is moving toward accepting XML input,
although the filtering process is necessarily
complex. But what is also needed is a version
of Context that produces well formed XML as an
output. That would be a step toward
Am 2014-08-26 um 21:10 schrieb Wolfgang Schuster schuster.wolfg...@gmail.com:
Am 26.08.2014 um 17:07 schrieb john Culleton j...@wexfordpress.com:
Context is moving toward accepting XML input,
although the filtering process is necessarily
complex. But what is also needed is a version
of
On 8/26/2014 7:08 PM, Henning Hraban Ramm wrote:
Creating ePub from ConTeXt is still tedious - you need to tag everything (even
paragraphs) with \start/\stop, the resulting export.xml is still missing a root
node if you use project structure (components), and you need to tinker a lot
with
On 8/26/2014 5:07 PM, john Culleton wrote:
Context is moving toward accepting XML input,
although the filtering process is necessarily
complex. But what is also needed is a version
of Context that produces well formed XML as an
output. That would be a step toward producing a
dual purpose
On 26 Aug 2014, at 20:04, Hans Hagen pra...@wxs.nl wrote:
Context users have invested time, often years, in
learning how to write Context code. Writing XML is
a whole other skillset, comparable to writing xhtml.
It's not so different if you're accustomed to structure.
To chime in: xml
Suppose I want to make a fully classical flat text without interaction (no
clickable links in the PDF). How do I get this? If I use \in or \at, ConTeXt
turns them into clickable links. That is not my problem so much, but it also
changes font to bold and colour to green, and I do not want that.
Am 26.08.2014 um 21:06 schrieb Gerben Wierda gerben.wie...@rna.nl:
Suppose I want to make a fully classical flat text without interaction (no
clickable links in the PDF). How do I get this? If I use \in or \at, ConTeXt
turns them into clickable links. That is not my problem so much, but it
11 matches
Mail list logo
