fundamental problem with headings

fundamental problem with headings

[Steffen Wolfrum]

Hi,

there seems to be a fundamental problem with headings - or at least I have :(

Each kind of "emphasizing" - like \it \bf \cap \sc etc. - lets the respective phrase fall back to the documents bodyfont (see example below).


How can I avoid this bug? Do I use wrong code?


Thank you,

Steffen


\starttext

\def\Textit{\groupedcommand\it\/}
\definefont[SectionFont][Serif at 20pt]
\def\SectionStyle{\SectionFont\setupinterlinespace[line=30pt]}
\setuphead[section]
[alternative=paragraph,style=\SectionStyle]

text

\section{heading \Textit{italic} heading}

text

\stoptext

Re: fundamental problem with headings

[Taco Hoekwater]

Steffen Wolfrum wrote:
> Hi,
>  
> Each kind of "emphasizing" - like \it \bf \cap \sc etc. - 
 > lets the respective phrase fall back to the documents
 > bodyfont (see example below).
> 
> How can I avoid this bug? 

not a bug, this is the expected behaviour of \definefont.

> Do I use wrong code?

Yes. \definefont defines a single font (hence it's name).

What you actually need is a full-blown bodyfont switch:

   \def\SectionStyle{%
     \switchtobodyfont[rm,20pt]
     \setupinterlinespace[line=30pt]
   }

Greetings, Taco

Re: fundamental problem with headings

[Willi Egger]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Hi Steffen,

I used your code here just adding \setupoutput[pdftex]
The result seems ok. to me. See attachment.

Running:
TeXExec 5.2.3
pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2c 7.5.3)
ConTeXt  ver: 2005.01.13  fmt: 2005.1.18  int: english  mes: english

Willi

Steffen Wolfrum wrote:
> Hi,
> 
> there seems to be a fundamental problem with headings - or at least I have :(
> 
> Each kind of "emphasizing" - like \it \bf \cap \sc etc. - lets the respective phrase fall back to the documents bodyfont (see example below).
> 
> 
> How can I avoid this bug? Do I use wrong code?
> 
> 
> Thank you,
> 
> Steffen
> 
> 
> \starttext
> 
> \def\Textit{\groupedcommand\it\/}
> \definefont[SectionFont][Serif at 20pt]
> \def\SectionStyle{\SectionFont\setupinterlinespace[line=30pt]}
> \setuphead[section]
> [alternative=paragraph,style=\SectionStyle]
> 
> text
> 
> \section{heading \Textit{italic} heading}
> 
> text
> 
> \stoptext
> 
> 
> 
> 
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

[-- Attachment #2: sectionheader-Wolffrum.pdf --]
[-- Type: application/pdf, Size: 11920 bytes --]

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: fundamental problem with headings

[Willi Egger]

Hi Steffen

Hm, so I misinterpreted your first mail.
Indeed, the emphasized part is at bodyfontsize...

Sorry for the wrong answer


Willi

Taco Hoekwater wrote:
> Steffen Wolfrum wrote:
> 
>> Hi,
>>  
>> Each kind of "emphasizing" - like \it \bf \cap \sc etc. - 
> 
>  > lets the respective phrase fall back to the documents
>  > bodyfont (see example below).
> 
>>
>> How can I avoid this bug? 
> 
> 
> not a bug, this is the expected behaviour of \definefont.
> 
>> Do I use wrong code?
> 
> 
> Yes. \definefont defines a single font (hence it's name).
> 
> What you actually need is a full-blown bodyfont switch:
> 
>   \def\SectionStyle{%
>     \switchtobodyfont[rm,20pt]
>     \setupinterlinespace[line=30pt]
>   }
> 
> Greetings, Taco
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

Re: fundamental problem with headings

[Steffen Wolfrum]

Adam Lindsay <atl@comp.lancs.ac.uk> wrote:

>  Steffen Wolfrum said this at Fri, 11 Mar 2005 12:33:13 +0100:
>
>  >In fact, this is something I would like to have also for other
>  >purposes (for example to use a second set of oldstyle figures):
>  >defining my own *myserif* or *mysans* that could be used then in a
>  >typescriptfile the same way as sans, serif and mono are used there.
>  >
>  >But up to now I didn't manage it.
>  >
>  >Somebody did and would like to share his/her knowledge?
>
>  Okay, thanks for clarifying.
>
>  You might like to take a look at the typescripts in the OpenType.zip file
>  at <http://homepage.mac.com/atl/tex/>. I defined full myserif/mysans
>  families (I called them romancaps and capsans) to stand next to the serif
>  and sans families (same font, different features). There are also a
>  couple convenience macros in there to help switch between the two.
>
>  Is that the sort of thing you're looking for? There's nothing inherently
>  SmallCaps (or OpenType) about the fundamental typescripts--that's just
>  the first testing ground I found.


I had a look at your file but I think my point is different:

You still use only the predefined serif, sans etc.
\usetypescript[serif]...
\usetypescript[sans]...
\usetypescript[math]...

but I would like to use also
\usetypescript[myserif]...
and the corresponding \myrm (next to \tt and \ss).

I don't know Hans' texnical term for serif, sans, mono, math etc. is 
(as used above).

Steffen

Re: fundamental problem with headings

[Adam Lindsay]

Steffen Wolfrum said this at Fri, 11 Mar 2005 12:33:13 +0100:

>In fact, this is something I would like to have also for other 
>purposes (for example to use a second set of oldstyle figures): 
>defining my own *myserif* or *mysans* that could be used then in a 
>typescriptfile the same way as sans, serif and mono are used there.
>
>But up to now I didn't manage it.
>
>Somebody did and would like to share his/her knowledge?

Okay, thanks for clarifying.

You might like to take a look at the typescripts in the OpenType.zip file
at <http://homepage.mac.com/atl/tex/>. I defined full myserif/mysans
families (I called them romancaps and capsans) to stand next to the serif
and sans families (same font, different features). There are also a
couple convenience macros in there to help switch between the two.

Is that the sort of thing you're looking for? There's nothing inherently
SmallCaps (or OpenType) about the fundamental typescripts--that's just
the first testing ground I found.
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: fundamental problem with headings

[Steffen Wolfrum]

Adam Lindsay <atl@comp.lancs.ac.uk> wrote:

>  Steffen Wolfrum said this at Thu, 10 Mar 2005 23:11:41 +0100:
>
>  >But if the heading should be set in general in a bold face what do I
>  >use instead of \rm so that italic parts of he heading will be typeset
>  >in bold-italic (and \sc parts to bold-smallcaps)?
>  >I guess something (next to serif, sans, mono, ...) like serifbold
>  >(\brm?) should be defined in my typescript?
>
>  I'm a bit confused why you're not using \em in this situation, as it
>  adapts to both bold and roman contexts. If you dislike that it defaults
>  to slanted, then there's:
>
>  \setupbodyfontenvironment[default][em=italic]
>  {\bf Hello \em World} Hello \em World
>
>
>  But if you want to follow the path of defining your own, adaptive
>  switches, then you could look at these goodies already defined in font-ini:
>
>  %D \macros
>  %D   {emphbf,emphit,emphsl,emphtf}
>  %D
>  %D The next emphasis alternatives are for \THANH. They adapt
>  %D their style as good as possible.
>
>  \def\emphbf{\groupedcommand{\bf\def\emphit{\bi}\def\emphsl{\bs}}{}}
>  \def\emphit{\groupedcommand{\it\def\emphbf{\bi}\def\emphsl{\sl}}{}}
>  \def\emphsl{\groupedcommand{\sl\def\emphbf{\bs}\def\emphit{\it}}{}}
>  \def\emphtf{\groupedcommand{\tf\def\e
>  mphbf{\bf}\def\emphit{\it}\def\emphsl{\sl}}
>  {}}


Right. I can use \em.

But my workflow of using ConTeXt is typesetting already finished 
books (.doc-files). And so I would like to change the "text" as 
little as possible and instead use an suitable set of typescript and 
setup environment.

That's why I thought I'd need a mysans (or \myrm) defined in the 
typescript to be used in Taco's full-blown bodyfont switch as 
described above:

    \def\SectionStyle{%
      \switchtobodyfont[myrm,20pt]
      \setupinterlinespace[line=30pt]
    }



In fact, this is something I would like to have also for other 
purposes (for example to use a second set of oldstyle figures): 
defining my own *myserif* or *mysans* that could be used then in a 
typescriptfile the same way as sans, serif and mono are used there.

But up to now I didn't manage it.

Somebody did and would like to share his/her knowledge?


Thank you,

Steffen

Re: fundamental problem with headings

[Adam Lindsay]

Steffen Wolfrum said this at Thu, 10 Mar 2005 23:11:41 +0100:

>But if the heading should be set in general in a bold face what do I 
>use instead of \rm so that italic parts of he heading will be typeset 
>in bold-italic (and \sc parts to bold-smallcaps)?
>I guess something (next to serif, sans, mono, ...) like serifbold 
>(\brm?) should be defined in my typescript?

I'm a bit confused why you're not using \em in this situation, as it
adapts to both bold and roman contexts. If you dislike that it defaults
to slanted, then there's:

\setupbodyfontenvironment[default][em=italic]
{\bf Hello \em World} Hello \em World


But if you want to follow the path of defining your own, adaptive
switches, then you could look at these goodies already defined in font-ini:

%D \macros
%D   {emphbf,emphit,emphsl,emphtf}
%D
%D The next emphasis alternatives are for \THANH. They adapt
%D their style as good as possible.

\def\emphbf{\groupedcommand{\bf\def\emphit{\bi}\def\emphsl{\bs}}{}}
\def\emphit{\groupedcommand{\it\def\emphbf{\bi}\def\emphsl{\sl}}{}}
\def\emphsl{\groupedcommand{\sl\def\emphbf{\bs}\def\emphit{\it}}{}}
\def\emphtf{\groupedcommand{\tf\def\e
mphbf{\bf}\def\emphit{\it}\def\emphsl{\sl}}
{}}

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: fundamental problem with headings

[Steffen Wolfrum]

>  Steffen Wolfrum wrote:
>  > Hi,
>  >
>  > Each kind of "emphasizing" - like \it \bf \cap \sc etc. -
>   > lets the respective phrase fall back to the documents
>   > bodyfont (see example below).
>  >
>  > How can I avoid this bug?
>
>  not a bug, this is the expected behaviour of \definefont.
>
>  > Do I use wrong code?
>
>  Yes. \definefont defines a single font (hence it's name).
>
>  What you actually need is a full-blown bodyfont switch:
>
>     \def\SectionStyle{%
>       \switchtobodyfont[rm,20pt]
>       \setupinterlinespace[line=30pt]
>     }
>
>  Greetings, Taco


OK, so my example changes to
\starttext

\def\Textit{\groupedcommand\it\/}

% \definefont[SectionFont][SerifBold at 20pt]
% \def\SectionStyle{\SectionFont\setupinterlinespace[line=30pt]}

  \def\SectionStyle{%
    \switchtobodyfont[rm,20pt]
    \setupinterlinespace[line=30pt]
  }

\setuphead[section]
[alternative=paragraph,style=\SectionStyle]

text

\section{heading \Textit{italic} heading}

text

\stoptext




But if the heading should be set in general in a bold face what do I 
use instead of \rm so that italic parts of he heading will be typeset 
in bold-italic (and \sc parts to bold-smallcaps)?
I guess something (next to serif, sans, mono, ...) like serifbold 
(\brm?) should be defined in my typescript?

Thank you,


Steffen

Re: fundamental problem with headings

[Steffen Wolfrum]

"full-blown bodyfont switch" - that sounds good. 

thank you Taco!
st.


Taco Hoekwater <taco@elvenkind.com> wrote:

> Steffen Wolfrum wrote:
> > Hi,
> >  
> > Each kind of "emphasizing" - like \it \bf \cap \sc etc. - 
>  > lets the respective phrase fall back to the documents
>  > bodyfont (see example below).
> > 
> > How can I avoid this bug? 
> 
> not a bug, this is the expected behaviour of \definefont.
> 
> > Do I use wrong code?
> 
> Yes. \definefont defines a single font (hence it's name).
> 
> What you actually need is a full-blown bodyfont switch:
> 
>    \def\SectionStyle{%
>      \switchtobodyfont[rm,20pt]
>      \setupinterlinespace[line=30pt]
>    }
> 
> Greetings, Taco
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context