From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: force line spacing (was: uppercase section titles: no line breaking?)
Date: Sat, 11 Jan 2020 19:59:29 +0100 [thread overview]
Message-ID: <9878C5A4-8F15-405E-BA49-A9F6974EB9B5@fiee.net> (raw)
In-Reply-To: <ed0e43d2-e79d-2954-6f56-7d75b4f189e4@gmail.com>
Am 2020-01-11 um 19:51 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>
> Henning Hraban Ramm schrieb am 11.01.2020 um 19:38:
>> Thank you very much!
>> I tried a \framed to no avail.
>
> \framed needs a align setting to allow line breaks.
>
>> And I thought I needed my own command since I also set color and font, but
>> style={\MyDefinedFont\WORD}
>> actually works.
>
> Use \setcharactercasing with style keys when you need multiple settings, it's faster than \WORD because no group check is needed.
Ok.
>> My remaining problem in this case is irregular line spacing if there are umlauts, will open a new thread.
>
> Increase the value for the baseline distance, e.g.
>
> \defineinterlinespace[chapter][line=3.2ex]
>
> \setuphead[chapter][interlinespace=chapter]
>
> or
>
> \setuphead[chapter][style={\setupinterlinespace[line=3.2ex]}]
But I need to keep the line spacing, even if accents collide.
E.g.
\setupbodyfont[rm,20pt]
\setupinterlinespace[8mm]
\setuplayout[
width=10cm,
%grid=yes, % different, but bad either way
]
\showgrid
\definefont[TitleFont][SansBold at 24pt][8mm]
\def\Blindtext{Ein Anfänger der Gitarre habe Eifer. Mönsch ärgere düch nïcht! Über Állen Wípfeln ìst Ŕüh. O Tannenbaum, wie blau sind deine Nadeln.}
\starttext
\Blindtext
\WORD{\Blindtext}
{\TitleFont\Blindtext
\WORD{\Blindtext}}
\stoptext
In my actual use case, my usual line spacing is good for the body text, and the slightly bigger section titles should keep it; there would be no visual(!) collision of accents on uppercase characters with the previous line, but ConTeXt increases the line spacing nevertheless. If I activate the grid, I get double line height only in the section titles with umlauts – quite ugly.
Can’t I force the line height?
Best, Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-01-11 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 17:53 uppercase section titles: no line breaking? Henning Hraban Ramm
2020-01-11 18:21 ` Wolfgang Schuster
2020-01-11 18:38 ` Henning Hraban Ramm
2020-01-11 18:51 ` Wolfgang Schuster
2020-01-11 18:59 ` Henning Hraban Ramm [this message]
2020-01-11 19:05 ` force line spacing Wolfgang Schuster
2020-01-11 19:11 ` Henning Hraban Ramm
2020-01-11 19:43 ` Wolfgang Schuster
2020-01-11 19:49 ` Wolfgang Schuster
2020-01-11 20:07 ` Henning Hraban Ramm
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=9878C5A4-8F15-405E-BA49-A9F6974EB9B5@fiee.net \
--to=texml@fiee.net \
--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).