On Sun, 23 Jun 2019 at 19:08, wrote:
>
> Hi Duncan,
>
> I guess this may be what you want to do:
>
> \setuphead[part][placehead=yes]
> \setuphead[section][sectionsegments=section]
> \setuphead[subsection][sectionsegments=section:subsection]
> \starttext
> \part{Part}
> \ch
On Sun, 23 Jun 2019 at 11:00, Hans Hagen wrote:
>
> in the test suite there are all kind of examples (zip can be downloaded
> from the website)
>
>
Thanks Hans. After some searching in the test suite I found the answer,
which I'll put here in case someone else is searching for it, which is:
\setu
On 6/23/19 10:26 AM, Duncan Hothersall wrote:
> Further to my previous query about updating from mkii to mkiv, I have
> solved some of the issues by trial and error but am beginning to
> identify the ones I can't resolve. My first minimal example is below.
>
> I want the sections and subsections no
On 6/23/2019 10:26 AM, Duncan Hothersall wrote:
Further to my previous query about updating from mkii to mkiv, I have
solved some of the issues by trial and error but am beginning to
identify the ones I can't resolve. My first minimal example is below.
I want the sections and subsections not t
Further to my previous query about updating from mkii to mkiv, I have
solved some of the issues by trial and error but am beginning to identify
the ones I can't resolve. My first minimal example is below.
I want the sections and subsections not to prefix the part and chapter
numbering, giving me t
On 6/12/2019 10:32 AM, Duncan Hothersall wrote:
Thanks Hans, that's good to know. I was seeing issues which seemed to be
related to setupheader statements using command=, which are in heavy use
in our system because we use this to externalise styles. But it could
easily have been something font
Thanks Hans, that's good to know. I was seeing issues which seemed to be
related to setupheader statements using command=, which are in heavy use in
our system because we use this to externalise styles. But it could easily
have been something font-related left in some of the commands.
I will work
On 6/12/2019 5:22 AM, Duncan Hothersall wrote:
Hi all.
Long-time user but haven't posted in a long while...
**
After many happy years of running a mkii set up I am finally facing the
fact that time has moved on and upgrading to mkiv.
I understand the biggest change needed to my sources is in
Hi all.
Long-time user but haven't posted in a long while...
After many happy years of running a mkii set up I am finally facing the
fact that time has moved on and upgrading to mkiv.
I understand the biggest change needed to my sources is in the fonts
handling, but I am getting a few other prob
> Am 01.03.2015 um 11:20 schrieb Gerben Wierda :
>
> I’m trying to get my project from mkii to mkiv. I’m running into a font
> issue. I’m using the Optima font from OS X on the Mac. My current setup is as
> added below. Can someone tell me how to do that in mkiv?
>
> \usetypescript[serif,sans
I’m trying to get my project from mkii to mkiv. I’m running into a font issue.
I’m using the Optima font from OS X on the Mac. My current setup is as added
below. Can someone tell me how to do that in mkiv?
\usetypescript[serif,sans,mono] [hanging] [normal]
\starttypescript [sans,serif] [optima
On 24-2-2010 22:32, Steffen Wolfrum wrote:
Hi,
typesetting an old MkII written project with MkIV today gives more then 2000 "unable
to resolve" warnings, like these ...
!backends : unable to resolve destination attribute 90
what does this mean? As that project did not even have 20
Hi,
typesetting an old MkII written project with MkIV today gives more then 2000
"unable to resolve" warnings, like these ...
!pages : flushing realpage 12, userpage 16
!backends : unable to resolve destination attribute 67
!backends : unable to resolve destination attribu
13 matches
Mail list logo
