Peter Rolf wrote:
.
http://wiki.contextgarden.net/Cropping_text
Best wishes, Peter
.
The link to the wiki gives indeed a clear description of the cropping
feature. Just great, it works nicely when applying it to my list of
figures! Thanks for your help!
Regards,
Gerard
--
Hi
in a thread Page numbers at empty pages in the beginning of
September I got a solution for the empty pages. But if I want empty
headers at the beginning of the chapter it does not function:
\setuphead[chapter][header=empty]
\setuphead
[chapter]
[page=yes,
I need to produce an lengthy itemization of the form:
1.
1.1
1.2
2.
2.1
I can get:
1.
1
2
2.
1
easily enough, but how can I get the main division number to repeat
in the subitem numeration?
Alan
2007/9/30, Alan Bowen [EMAIL PROTECTED]:
I need to produce an lengthy itemization of the form:
1.
1.1
1.2
2.
2.1
I can get:
1.
1
2
2.
1
easily enough, but how can I get the main division number to repeat in the
subitem numeration?
On Sun, 30 Sep 2007, Alan Bowen wrote:
I need to produce an lengthy itemization of the form:
1.
1.1
1.2
2.
2.1
I can get:
1.
1
2
2.
1
easily enough, but how can I get the main division number to repeat
On 9/26/07, Hans Hagen [EMAIL PROTECTED] wrote:
1) Why we need to set almost all in setuptex.bat, while the same vars
(except Windows' PATH) are already set in texmf.cnf?
well, this is not recent, but has aways been the case; in setuptex i
make sure that no conflicts can arise between
Joel C. Salomon wrote:
On 9/26/07, Hans Hagen [EMAIL PROTECTED] wrote:
1) Why we need to set almost all in setuptex.bat, while the same vars
(except Windows' PATH) are already set in texmf.cnf?
well, this is not recent, but has aways been the case; in setuptex i
make sure that no conflicts
Thanks, Wolfgang. This is good start. The problem now is that
with
\def\firstlevelnumber#1{\xdef\thefirstlevelnumber{#1}#1}
\defineconversion[firstlevelnumber][\firstlevelnumber]
\def\secondlevelnumber#1{\thefirstlevelnumber.#1}
\defineconversion[secondlevelnumber][\secondlevelnumber]
\starttext
Thanks, Aditya, I have adapted this as follows—
\startbuffer
\item item 1
\startitemize[n,stopper={},width=1em]
\item item 1.1
\item item 1.2
\item item 1.3
\stopitemize
\item item 2
\startitemize[n,stopper={},width=1em]
\item item 2.1
\item item 2.2
\item item 2.3
Hello,
So what environment variables can I set globally to avoid the need for
running setuptex.bat?
Personally I came to the following set of vars (for luatex):
PATH = G:\rsync\windows\texmf-mswin\bin;
OSFONTDIR = %WINDIR%\Fonts
TEXMF = {g:\rsync\windows\texmf,g:\rsync\windows\texmf-local}
On 9/30/07, Hans Hagen [EMAIL PROTECTED] wrote:
So what environment variables can I set globally to avoid the need for
running setuptex.bat? My first guess is:
snip
SETUPTEX=done
CTXMINIMAL=yes
not if setuptex is not used
CTXMINIMAL is also not needed?
TEXPATH=C:\...whatever the
Joel C. Salomon wrote:
CTXMINIMAL is also not needed?
depends on if it used, not if you go real minimal (more for calling scripts)
But setuptex still sets these. What does it mean, that TEXPOOL al.
aren't needed for luatex/xetex? Does MKII need them?
not related to mkiv/mkii but to
On Sun, 30 Sep 2007, Alan Bowen wrote:
Thanks, Aditya, I have adapted this as follows—
\startbuffer
\item item 1
\startitemize[n,stopper={},width=1em]
\item item 1.1
\item item 1.2
\item item 1.3
\stopitemize
\item item 2
\startitemize[n,stopper={},width=1em]
\item item 2.1
So, to sum up: The tex engines should be accessible via PATH,
OSFONTDIR is really handy; other than that only TEXPATH and TEXMF* are
needed, since pool files (whatever they are) are on the way out.
Seems straightforward enough, if that's complete.
Is there any real point to creating an NSIS or
14 matches
Mail list logo
