Fixed.
Fabrice
2010/6/27 Taco Hoekwater t...@elvenkind.com
Hi Fabrice,
On 06/27/2010 09:13 AM, Peter Münster wrote:
On Mon, Jun 07 2010, Taco Hoekwater wrote:
Is it possible, to get email on every commit to
http://foundry.supelec.fr/gf/project/contextman ?
Sure. Subscribe to the
On 06/27/2010 11:14 AM, Vedran Miletić wrote:
Hi,
upon compiling s-pre-02 with TL2010 ConTeXt, I get the attached file
which is very narrow and text gets cut off (at least when viewed in
Evince). Is this a bug?
Yeah, I would say so. Same thing happens in the latest beta context.
Best wishes,
Am 28.06.2010 um 07:45 schrieb Steffen Wolfrum:
But the example file that is mentioned in that link don't produce anything
with MkII either:
TeXExec | no ctx file found
TeXExec | nothing to process
Ahh! There was a space in the file's name, thus...
Now it works.
Steffen
Hi,
is there a way to avoid bookmark entries like this?
With language is german and encoding utf8 MkII compiles this ...
\section{Test~–~Nummer §\,613\,a}
... to:
TestCCC:4:126 dochar {123}CCC:4:126 Nummer elax $unhbox vo...@x hbox
{$mathsurround z@ mathchar 278$}$ extormathspace +
Am 20.01.2009 um 16:19 schrieb Arthur Reutenauer:
Tagged PDF is indeed a problem
for the moment, but it's clearly not the feature your printer asks for,
and as a rule, you can be sure that if some functionality is essential
to publishers, it will be added quickly to ConTeXt :-)
Hi Hans,
--- Original message ---
Subject: Tagged PDF
From: Steffen Wolfrum cont...@st.estfiles.de
To: mailing list for ConTeXt users ntg-context@ntg.nl
Cc: Hans Hagen pra...@wxs.nl
Date: Monday, 28/06/2010 7:17 AM
Am 20.01.2009 um 16:19 schrieb Arthur Reutenauer:
Tagged PDF is indeed a
On Monday 28/06/2010 at 4:50 am, Steffen Wolfrum wrote:
Hi,
is there a way to avoid bookmark entries like this?
With language is german and encoding utf8 MkII compiles this ...
\section{Test~–~Nummer §\,613\,a}
\startsection[...,bookmark=]
\numstr seems to work fine in the body of text but errors out as if #1 was
not a number when it is used in chapter start loc. Here is an example:
%\numstr begins here
\unprotect
\def\numstring#1{\expandaft...@numstring\csname c...@#1\endcsname}
Hi all,
Is it possible to tell columnsets which column is the first one?
I use columnset in MKII to typeset Arabic text in a multicolumn layout
and the text starts in the left column. Is there a nice way to force the
text to start in the right column? Something like
Am 28.06.10 17:59, schrieb Tom:
\numstr seems to work fine in the body of text but errors out as if #1 was
not a number when it is used in chapter start loc. Here is an example:
[...]
\setuphead[chapter]
[command=\MyChapterCommandA] %change A to B to eliminate \substr call
Try
Am 28.06.10 18:39, schrieb Jelle Huisman:
Hi all,
Is it possible to tell columnsets which column is the first one?
I use columnset in MKII to typeset Arabic text in a multicolumn layout
and the text starts in the left column. Is there a nice way to force
the text to start in the right column?
Am 28.06.10 17:59, schrieb Tom:
\numstr seems to work fine in the body of text but errors out as if #1 was
not a number when it is used in chapter start loc. Here is an example:
[...]
\setuphead[chapter]
[command=\MyChapterCommandA] %change A to B to eliminate \substr call
Try
Am 28.06.10 23:03, schrieb Tom:
Making the following changes resulted in ! Missing Number, treated as zero.
I’m lazy:
\defineconversion[numstring][One,Two,Three,Four,Five,Six,Seven,Eight,Nine,Ten,...]
\setuphead[chapter][conversion=numstring]
\starttext
\dorecurse{11}{\chapter{Chapter
On Mon, Jun 28 2010, Aditya Mahajan wrote:
On Mon, 28 Jun 2010, Jason Earl wrote:
In my defense, part of the reason that I did not think of putting in a
manual page break before the section is that my real context documents
are generated from a script, and I did not want to have to process
14 matches
Mail list logo
