Am 16.01.2010 um 23:08 schrieb Andreas Harder:
>> can you try \convertedstructurecounter[chapter][type=last]
>
> Hello Wolfgang,
>
> I tried, but it only outputs nothing visible.
Sorry, my fault. Section numbering use their own system to save and get the
numbers.
What you can do is to save t
Am 17.01.2010 um 09:13 schrieb Wolfgang Schuster:
>
> Am 16.01.2010 um 23:08 schrieb Andreas Harder:
>
>>> can you try \convertedstructurecounter[chapter][type=last]
>>
>> Hello Wolfgang,
>>
>> I tried, but it only outputs nothing visible.
>
> Sorry, my fault. Section numbering use their own
Am 17.01.2010 um 13:06 schrieb Andreas Harder:
> Nonetheless the needed information is already present even more if one uses a
> table of contents …
The table of contents needs two passes too but only Hans can say (or provide
a command like \convertedstructurecounter for section numbers) how yo
The joinedup parameter in \startitemize is meant to close the gap
between the list and the preceding material. The margin parameter is
for horizontal movement of the list, is I understand it. However,
addition of a margin to the \startitemize disables the joinedup. Is
this expected behaviou
Am 17.01.2010 um 13:46 schrieb Hans van der Meer:
> The joinedup parameter in \startitemize is meant to close the gap between the
> list and the preceding material. The margin parameter is for horizontal
> movement of the list, is I understand it. However, addition of a margin to
> the \starti
Risking that, like my previous question, this one too will be posed
the Nth time, I nevertheless ask.
Typesetting a numbered list I tried a lot of paramaters on the itemize
macros, but always the code:
\startitemize[][start=8]
\item a
\item b
\item c
\item d
\stopitemize
results in:
8. a
9.
Tricked by the mail program editor! Of course I meant to accomplish
(with | for the left edge):
| 8. a
| 9. b
|10. c
|11. d
Hans van der Meer
On 17 jan 2010, at 14:51, Hans van der Meer wrote:
Risking that, like my previous question, this one too will be posed
the Nth time, I nevertheless
Am 17.01.2010 um 15:06 schrieb Hans van der Meer:
> Tricked by the mail program editor! Of course I meant to accomplish (with |
> for the left edge):
>
> | 8. a
> | 9. b
> |10. c
> |11. d
\startitemize[fit][start=8,itemalign=flushright]
Wolfgang
__
Thanks.
'itemalign' seems absent from the original ConTeXt-manual I have in
use (but that is fairly old, of course).
Your code results in very tight item labels:
1.start-of-item-text
I managed to get
1. start-of-item-text
by using [stopper={.~}] But is there a more general way to enlarge the
Am 17.01.2010 um 15:28 schrieb Hans van der Meer:
> Thanks.
> 'itemalign' seems absent from the original ConTeXt-manual I have in use (but
> that is fairly old, of course).
itemalign is a newer option (was added about 2 years ago)
> Your code results in very tight item labels:
> 1.start-of-ite
On Sun, Jan 17 2010, Hans van der Meer wrote:
> But is there a more general way to enlarge the
> item's width? Using [width=dimension] seemed no help
Hello Hans,
It works here:
\starttext
\startitemize[width=5em]
\item bla
\stopitemize
\stoptext
My version: 2010.01.15 15:49
Cheers, Peter
--
Am 17.01.2010 um 15:49 schrieb Peter Münster:
> On Sun, Jan 17 2010, Hans van der Meer wrote:
>
>> But is there a more general way to enlarge the
>> item's width? Using [width=dimension] seemed no help
>
> Hello Hans,
>
> It works here:
>
> \starttext
> \startitemize[width=5em]
> \item bla
>
On Sun, Jan 17 2010, Wolfgang Schuster wrote:
>
> That's not the problem, what did not work is
>
> - 'itemalign=...' in combination with 'width=' and
> - 'fit' in combination with 'distance='
Bug or feature? Should we add it to the tracker?
Cheers, Peter
--
Contact information: http://pmrb.f
Am 17.01.2010 um 16:17 schrieb Peter Münster:
> On Sun, Jan 17 2010, Wolfgang Schuster wrote:
>>
>> That's not the problem, what did not work is
>>
>> - 'itemalign=...' in combination with 'width=' and
>> - 'fit' in combination with 'distance='
>
> Bug or feature? Should we add it to the trac
> Can you make a minimal example or should we waste our time to write
> one for you?
>
> Wolfgang
Sorry, here it is:
\starttext
>From texshow-web
{
\setuphead[section-3][bodypartconversion=Characters]
\section{One}
}
but this does not work. I deleted the 's' from Characters
{
\setuphead[section-
Hello all,
when i place a footnote in a naturalTABLE the output at the bottom is always
multiplied by four per footnotemarker.
In normal tables it works normal (see minimal example in attachment). Is this a
bug or make i something wrong?
footnotetest.tex
Description: Binary data
footnotet
On 16-1-2010 22:58, Andreas Schneider wrote:
Wolfgang Schuster wrote:
This can't work because TeX collects mote material than it needs for the
current page and the same happens with the footnotes, the only thing you
can do is to use two pass data
Wolfgang
Is there not even some event in Lua
Hans Hagen wrote:
> It depends on your document. We have workflows where we can do with one
> pass in which case we run with --once (--runs=2 or so)
>
> Future versions of context mkiv might need one run less (in some cases)
> or one perceived run (which saves startup cycles) but as Wolgangs
> exp
On 17-1-2010 22:16, Andreas Schneider wrote:
I would be very grateful if you could point me in a direction I can work
forward from - I can only guess that there are similar mechanisms in the
already existing MkIV code ... although the \pagenumber problem seems to
indicate that it might be near t
On 17-1-2010 19:21, Bernhard Rosensteiner wrote:
Hello all,
when i place a footnote in a naturalTABLE the output at the bottom is always
multiplied by four per footnotemarker.
In normal tables it works normal (see minimal example in attachment). Is this a
bug or make i something wrong?
sort
> dealing with multipass data in mkiv is completely different from mkii
> and at some point there will be a proper api for users (makes no sense
> now as i might as well change internals along with luatex developments)
>
> in mkiv we store info in tables and much is available during a document
> r
2010/1/17 Andreas Schneider :
> What I need would be a precise page break handling. Currently ConTeXt seems
> to process a whole paragraph as one object, and then breaks it down to
> individual pages. That leads to a problem however:
This is how TeX works. :-)
Best
Martin
On 17-1-2010 13:36, Wolfgang Schuster wrote:
Am 17.01.2010 um 13:06 schrieb Andreas Harder:
Nonetheless the needed information is already present even more if one uses a
table of contents …
The table of contents needs two passes too but only Hans can say (or provide
a command like \converte
On 17-1-2010 23:13, Andreas Schneider wrote:
dealing with multipass data in mkiv is completely different from mkii
and at some point there will be a proper api for users (makes no sense
now as i might as well change internals along with luatex developments)
in mkiv we store info in tables and mu
On Sat, Jan 16, 2010 at 10:41 PM, Aditya Mahajan wrote:
> On Sat, 16 Jan 2010, paul morgan wrote:
>
> Thank you again Aditya and Khaled for getting ConTeXt working here. One
>> more
>> question for the list:
>>
>> Under MacTex or TexLive, not sure which one, on my 10.4.11 system, my
>> setup
>>
25 matches
Mail list logo
