Re: [NTG-context] mkii to mkiv - section numbering with minimal example

2019-06-23 Thread Duncan Hothersall
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}
> \chapter{Chapter}
> \section{Section}
> \subsection{Subsection}
> \stoptext
>
> I hope it helps,
>
> Pablo
> --
> http://www.ousia.tk
>
>
> Belated thanks Pablo, I get the digest so I had posted my discovery of
this precise solution before I saw you supplying that answer. Apologies! It
works well.

Duncan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv - section numbering with minimal example

2019-06-23 Thread Duncan Hothersall
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:

\setuphead[section][sectionsegments=section]
\setuphead[subsection][sectionsegments=section:subsection]

which sets up sections to just be numbered with the section number instead
of the part, chapter and section number, and sets up subsections to just be
numbered with the section and subsection number.

Now that I know how to do it I see mkiv is much cleaner on this code and
the change gets reflected in tables of contents etc. This was much harder
in mkii. Thanks again.

Duncan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv - section numbering with minimal example

2019-06-23 Thread Pablo Rodriguez
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 not to prefix the part and chapter
> numbering, giving me this output:
>
> Part 1
> Chapter 1.1
> Section 1
> Subsection 1.1

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}
\chapter{Chapter}
\section{Section}
\subsection{Subsection}
\stoptext

I hope it helps,

Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv - section numbering with minimal example

2019-06-23 Thread Hans Hagen

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 to prefix the part and chapter 
numbering, giving me this output:


Part 1
Chapter 1.1
Section 1
Subsection 1.1

The line that used to achieve this result was

\setupsection[section-3][previousnumber=no]

and there was also

\setuphead[section][partnumber=no,chapternumber=no]

but neither of these seems to work in mkiv


Minimal example:

\setupsection[section-3][previousnumber=no]
\setuphead[section][partnumber=no,chapternumber=no]

\starttext
\part{Part}
Part
\chapter{Chapter}
Chapter
\section{Section}
Section
\subsection{Subsection}
Subsection
\stoptext

Many thanks for any pointers.
in the test suite there are all kind of examples (zip can be downloaded 
from the website)


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] mkii to mkiv - section numbering with minimal example

2019-06-23 Thread Duncan Hothersall
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 this output:

Part 1
Chapter 1.1
Section 1
Subsection 1.1

The line that used to achieve this result was

\setupsection[section-3][previousnumber=no]

and there was also

\setuphead[section][partnumber=no,chapternumber=no]

but neither of these seems to work in mkiv


Minimal example:

\setupsection[section-3][previousnumber=no]
\setuphead[section][partnumber=no,chapternumber=no]

\starttext
\part{Part}
Part
\chapter{Chapter}
Chapter
\section{Section}
Section
\subsection{Subsection}
Subsection
\stoptext

Many thanks for any pointers.

Duncan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv - what an ancient user needs to know

2019-06-12 Thread Hans Hagen

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-related left in some of the commands.


I will work on a minimal example over the next few days and - if I don't 
solve it myself in the process - I'll post it.

sometimes if you define you rown macros, like

  \def\foo{...}

you should use

  \unexpanded\def\foo{...}


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv - what an ancient user needs to know

2019-06-12 Thread Duncan Hothersall
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 a minimal example over the next few days and - if I don't
solve it myself in the process - I'll post it.

Thanks again,

Duncan

On Wed, 12 Jun 2019 at 08:07, Hans Hagen  wrote:

> 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 the fonts
> > handling, but I am getting a few other problems with things like
> > chapter/sectioning setups that I can't see mentioned in
> > https://www.contextgarden.net/MkIV_Differences
> >
> > I was wondering if there exists a comprehensive "what you have to change
> > in your sources to move from mkii to mkiv" document anywhere or, failing
> > that, if anyone can offer guidance on what has changed in the
> > chapter/sectioning setups code between the two.
> >
> > Apologies for not supplying an example of code - I'm not yet at the
> > point that that's possible.
> >
> > Any help much appreciated. And hello to anyone who remembers me from
> > fifteen plus years ago!
> Do you get errors? There should be no real fundamental differences
> betwene mkii and mmkiv wrt the interfac, but because font encodings are
> gone and input is utf8 by default that might need to be changed.
> Structure has more options. I think the biggest conceptual change in the
> setups has been the way footnotes are configured. Of course there are
> new commands too.
>
> So, a small example triggering the issue would help,
>
> Hans
>
> ps. Of course the biggest change is that luatex is used instead of
> pdftex/xetex.
>
> -
>Hans Hagen | PRAGMA ADE
>Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
>
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv - what an ancient user needs to know

2019-06-12 Thread Hans Hagen

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 the fonts 
handling, but I am getting a few other problems with things like 
chapter/sectioning setups that I can't see mentioned in 
https://www.contextgarden.net/MkIV_Differences


I was wondering if there exists a comprehensive "what you have to change 
in your sources to move from mkii to mkiv" document anywhere or, failing 
that, if anyone can offer guidance on what has changed in the 
chapter/sectioning setups code between the two.


Apologies for not supplying an example of code - I'm not yet at the 
point that that's possible.


Any help much appreciated. And hello to anyone who remembers me from 
fifteen plus years ago!
Do you get errors? There should be no real fundamental differences 
betwene mkii and mmkiv wrt the interfac, but because font encodings are 
gone and input is utf8 by default that might need to be changed. 
Structure has more options. I think the biggest conceptual change in the 
setups has been the way footnotes are configured. Of course there are 
new commands too.


So, a small example triggering the issue would help,

Hans

ps. Of course the biggest change is that luatex is used instead of 
pdftex/xetex.


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] mkii to mkiv - what an ancient user needs to know

2019-06-11 Thread Duncan Hothersall
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 problems with things like
chapter/sectioning setups that I can't see mentioned in
https://www.contextgarden.net/MkIV_Differences

I was wondering if there exists a comprehensive "what you have to change in
your sources to move from mkii to mkiv" document anywhere or, failing that,
if anyone can offer guidance on what has changed in the chapter/sectioning
setups code between the two.

Apologies for not supplying an example of code - I'm not yet at the point
that that's possible.

Any help much appreciated. And hello to anyone who remembers me from
fifteen plus years ago!

Duncan
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkii to mkiv, setting the fonts for my project

2015-03-01 Thread Wolfgang Schuster

> 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,mono] [hanging] [normal]
> \starttypescript [sans,serif] [optima] [texnansi,ec]
> \definefontsynonym [Optima-Regular] [\typescriptthree-OptimaRegular]
> [encoding=\typescriptthree]
> \definefontsynonym [Optima-Italic] [\typescriptthree-OptimaItalic]
> [encoding=\typescriptthree]
> \definefontsynonym [Optima-Bold] [\typescriptthree-OptimaBold]
> [encoding=\typescriptthree]
> \definefontsynonym [Optima-BoldItalic] [\typescriptthree-OptimaBoldItalic]
> [encoding=\typescriptthree]
> \definefontsynonym [Optima-ExtraBlack] [\typescriptthree-OptimaExtraBlack]
> [encoding=\typescriptthree]
> \stoptypescript
> \starttypescript [sans,serif] [optima] [name]
> \setups[font:fallback:\typescriptone]
> \definefontsynonym [\typescriptprefix\typescriptone] [Optima-Regular]
> \definefontsynonym [\typescriptprefix\typescriptone Italic] [Optima-Italic]
> \definefontsynonym [\typescriptprefix\typescriptone Bold]   [Optima-Bold]
> \definefontsynonym [\typescriptprefix\typescriptone BoldItalic]
> [Optima-BoldItalic]
> \definefontsynonym [\typescriptprefix\typescriptone Black] [Optima-ExtraBlack]
> \stoptypescript
> \definetypeface[allsans][rm][serif][optima][default][encoding=texnansi]
> \definetypeface[allsans][ss][sans][optima][default][encoding=texnansi]
> \loadmapfile [gtamacfonts.map]
> \setupbodyfont[allsans,10pt]
> 
> In gtamacfonts.map, I find:
> 
> % Optima
> 
> ec-raw-OptimaRegular Optima-Regular 4  ec-raw-OptimaBold Optima-Bold 4  ec-raw-OptimaBoldItalic Optima-BoldItalic 4  ec-raw-OptimaExtraBlack Optima-ExtraBlack 4  ec-raw-OptimaItalic Optima-Italic 4  
> ts1-OptimaRegular Optima-Regular 4  ts1-OptimaBold Optima-Bold 4  ts1-OptimaBoldItalic Optima-BoldItalic 4  ts1-OptimaExtraBlack Optima-ExtraBlack 4  ts1-OptimaItalic Optima-Italic 4  ts1-OptimaRegular Optima-Regular 4  
> texnansi-OptimaBold Optima-Bold 4 < OptimaBold.ttf texnansi.enc
> texnansi-OptimaBoldItalic Optima-BoldItalic 4 < OptimaBoldItalic.ttf 
> texnansi.enc
> texnansi-OptimaExtraBlack Optima-ExtraBlack 4 < OptimaExtraBlack.ttf 
> texnansi.enc
> texnansi-OptimaItalic Optima-Italic 4 < OptimaItalic.ttf texnansi.enc
> texnansi-OptimaRegular Optima-Regular 4 < OptimaRegular.ttf texnansi.enc


There is no need for a serif font in your document but you should always set a 
math font.

\starttypescript [sans] [optima]
\setups[font:fallback:sans]
\definefontsynonym [Sans]   [file:optima.ttc(Optima Regular)]
\definefontsynonym [SansItalic] [file:optima.ttc(Optima Italic)]
\definefontsynonym [SansBold]   [file:optima.ttc(Optima Bold)]
\definefontsynonym [SansBoldItalic] [file:optima.ttc(Optima Bold 
Italic)]
\stoptypescript

\definetypeface [optima] [ss] [sans] [optima] [default] [features=default]
\definetypeface [optima] [mm] [math] [modern] [default]

\setupbodyfont[optima,10pt]

\starttext
Optima {\it Optima} {\bf Optima} {\bi Optima}
\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] mkii to mkiv, setting the fonts for my project

2015-03-01 Thread 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,mono] [hanging] [normal]
\starttypescript [sans,serif] [optima] [texnansi,ec]
\definefontsynonym [Optima-Regular] [\typescriptthree-OptimaRegular]
[encoding=\typescriptthree]
\definefontsynonym [Optima-Italic] [\typescriptthree-OptimaItalic]
[encoding=\typescriptthree]
\definefontsynonym [Optima-Bold] [\typescriptthree-OptimaBold]
[encoding=\typescriptthree]
\definefontsynonym [Optima-BoldItalic] [\typescriptthree-OptimaBoldItalic]
[encoding=\typescriptthree]
\definefontsynonym [Optima-ExtraBlack] [\typescriptthree-OptimaExtraBlack]
[encoding=\typescriptthree]
\stoptypescript
\starttypescript [sans,serif] [optima] [name]
\setups[font:fallback:\typescriptone]
\definefontsynonym [\typescriptprefix\typescriptone] [Optima-Regular]
\definefontsynonym [\typescriptprefix\typescriptone Italic] [Optima-Italic]
\definefontsynonym [\typescriptprefix\typescriptone Bold]   [Optima-Bold]
\definefontsynonym [\typescriptprefix\typescriptone BoldItalic]
[Optima-BoldItalic]
\definefontsynonym [\typescriptprefix\typescriptone Black] [Optima-ExtraBlack]
\stoptypescript
\definetypeface[allsans][rm][serif][optima][default][encoding=texnansi]
\definetypeface[allsans][ss][sans][optima][default][encoding=texnansi]
\loadmapfile [gtamacfonts.map]
\setupbodyfont[allsans,10pt]

In gtamacfonts.map, I find:

% Optima

ec-raw-OptimaRegular Optima-Regular 4 http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] MkII to MkIV

2010-02-25 Thread Hans Hagen

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 2000 \footnotes or 
\index or reference marks, what is meant?


hard to see without small example; it probably means that some reference 
is not flushed


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] MkII to MkIV

2010-02-24 Thread Steffen Wolfrum
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 attribute 69
!backends   : unable to resolve destination attribute 70
!backends   : unable to resolve destination attribute 71
!backends   : unable to resolve destination attribute 72
!backends   : unable to resolve destination attribute 74
!pages  : flushing realpage 13, userpage 17
!backends   : unable to resolve destination attribute 75
!backends   : unable to resolve destination attribute 76
!backends   : unable to resolve destination attribute 83
!backends   : unable to resolve destination attribute 80
!backends   : unable to resolve destination attribute 81
!pages  : flushing realpage 14, userpage 18
!backends   : unable to resolve destination attribute 82
!backends   : unable to resolve destination attribute 85
!backends   : unable to resolve destination attribute 86
!backends   : unable to resolve destination attribute 91
!backends   : unable to resolve destination attribute 89
!backends   : unable to resolve destination attribute 90



... what does this mean? As that project did not even have 2000 \footnotes or 
\index or reference marks, what is meant?

Paragraphs???


Steffen
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___