ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: question about linespace adjustment
Date: Wed, 25 Sep 2013 23:00:16 +0200	[thread overview]
Message-ID: <CAG5iGsDBzgRpuD+0UY6V5tV=m7cH6+Cjg0YFPFFBj8MPq4Vdjg@mail.gmail.com> (raw)
In-Reply-To: <52433F76.30905@sil.org>


[-- Attachment #1.1: Type: text/plain, Size: 2249 bytes --]

On Wed, Sep 25, 2013 at 9:54 PM, Lars Huttar <lars_huttar@sil.org> wrote:

> And is the answer that the bodyfont is a conglomerate
> of more properties than just the font, including interlinespace?
>


You can read  font-ini.mkvi :

%D \macros
%D   {setupbodyfont,switchtobodyfont}
%D
%D The next two macros are user ones. With \type{\setupbodyfont}
%D one can set the document bodyfont size, font family, style
%D and/or options defined in files, for example:
%D
%D \starttyping
%D \setupbodyfont[modern,12pt,roman]
%D \stoptyping
%D
%D This command affects the document as a whole: text, headers
%D and footers. The second macro however affects only the text:
%D
%D \starttyping
%D \switchtobodyfont[10pt]
%D \stoptyping
%D
%D So we've got:
%D
%D \showsetup{setupbodyfont}
%D \showsetup{switchtobodyfont}
%D
%D Both macros look alike. The second one also has to take
%D all kind of keywords into account.
If you follow switchtobodyfont you can see

unexpanded\def\font_basics_switchtobodyfont#specification%
  {\edef\m_font_step{\bodyfontvariable{#specification}}%
   \ifx\m_font_step\empty
     \font_helpers_set_font\zerocount{#specification}%
   \else
     \font_helpers_switch_bodyfont_step % so we have a fast [small] switch
   \fi
   \the\everybodyfont
   \the\everyswitchtobodyfont}

\unexpanded\def\switchtobodyfont[#specification]% could become an ifx

{\doifsomething{#specification}{\font_basics_switchtobodyfont{#specification}}}


The token register \everybodyfont  and
 \everyswitchtobodyfont take care for spaces:

(still in font-ini.mkvi)

%D   {everybodyfont,Everybodyfont,everyglobalbodyfont}
%D
%D Every change in bodyfont size has conseqences for the baseline
%D distance and skips between paragraphs. These are initialized
%D in other modules. Here we only provide the hooks that
%D garantees their handling.

%D At the system level one can initialize thing like:
%D
%D \starttyping
%D \appendtoks \setupspacing \to \everybodyfont
%D \stoptyping

In core-def.mkiv

\appendtoks
    \synchronizelocallinespecs
\to \everyswitchtobodyfont

while  spac-ver.mkiv

\unexpanded\def\synchronizelocallinespecs
  {\bodyfontlineheight \normallineheight
   \bodyfontstrutheight\strutheight
   \bodyfontstrutdepth \strutdepth}



-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 3235 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2013-09-25 21:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 14:36 Lars Huttar
2013-09-24 14:51 ` Aditya Mahajan
2013-09-24 16:01 ` Lars Huttar
2013-09-24 17:45   ` Lars Huttar
2013-09-24 18:18     ` luigi scarso
2013-09-24 21:07       ` Lars Huttar
2013-09-24 21:25         ` Aditya Mahajan
2013-09-25 19:54           ` Lars Huttar
2013-09-25 21:00             ` luigi scarso [this message]
2013-09-25 21:02             ` Wolfgang Schuster
2013-09-25 21:45               ` Lars Huttar
2013-09-26 19:47                 ` Wolfgang Schuster
2013-09-27 15:57                   ` Lars Huttar
2013-09-30 20:22                   ` Lars Huttar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG5iGsDBzgRpuD+0UY6V5tV=m7cH6+Cjg0YFPFFBj8MPq4Vdjg@mail.gmail.com' \
    --to=luigi.scarso@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).