From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: definedfont vs switchtobodyfont (was "shrink inter-line space")
Date: Mon, 20 Dec 2021 12:19:39 +0100 [thread overview]
Message-ID: <2e20cb6d-97e4-b476-a236-47d6356defb6@xs4all.nl> (raw)
In-Reply-To: <eac80faa-10a6-1cd2-602f-297078b52999@fastwebnet.it>
On 12/20/2021 12:06 PM, mf via ntg-context wrote:
> Il 18/12/21 13:00, Wolfgang Schuster ha scritto:
>> \definefontfeature [tightlines] [dimensions={*,0,0}]
>>
>> \starttext
>>
>> \samplefile{ward}\par
>>
>> \blank
>>
>> \start
>> \setupinterlinespace[line=5pt]
>> \definedfont[Normal*default,tightlines]
>> \samplefile{ward}\par
>> \stop
>>
>> \stoptext
>>
>
> Thanks Wolfgang.
>
> I tried this:
>
> \definefontfeature [tightlines] [dimensions={*,0,0}]
>
> \starttext
>
> \samplefile{ward}\par
>
> \blank
>
> \start
> \setupinterlinespace[line=5pt]
> \feature[+][tightlines]
> \samplefile{ward}\par
> \stop
>
> \stoptext
>
> but it doesn't add the feature to the current font.
> I understand I need a font switch.
> Usually I use \switchtobodyfont. How is \definedfont different?
it's a 'permanent' one ... so when the font is loaded the dimensions are
adapted so you need a new font definition
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-12-20 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:28 shrink inter-line space mf via ntg-context
2021-12-17 19:17 ` Wolfgang Schuster via ntg-context
2021-12-18 8:47 ` mf via ntg-context
2021-12-18 11:53 ` Hans Hagen via ntg-context
2021-12-18 12:00 ` Wolfgang Schuster via ntg-context
2021-12-20 11:06 ` definedfont vs switchtobodyfont (was "shrink inter-line space") mf via ntg-context
2021-12-20 11:19 ` Hans Hagen via ntg-context [this message]
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=2e20cb6d-97e4-b476-a236-47d6356defb6@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).