ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Adjusted Chapter Headings
Date: Tue, 19 Mar 2024 15:45:18 +0100	[thread overview]
Message-ID: <8acc5515-b309-43f8-bc99-8c24d2f758b8@fiee.net> (raw)
In-Reply-To: <CAPtmdbMJcPpY3sPYkRDeTYnFqPEVa=9TBgsKXNj+7g0=uwHeRw@mail.gmail.com>


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

Hi Jeroen,

it might make sense to use

\setuphead[chapter][
   conversion=R,
]
\setuplabeltext[nl][chapter={Boek }]

instead of ownnumber.

I would use one command for number and title and put both in the same 
kind of frame. Probably you should use a \strut in the text or 
\inframed[strut=yes] to assure the same text height.

HTH, Hraban

Am 19.03.24 um 12:59 schrieb Jeroen:
> I have some style adjustments for the chapters. The chapter "numbers" 
> need to be Boek I, Boek II, etc. A vertical separator was introduced 
> with an inframe. The chapter title at the right side does not 
> vertically align properly with the chapter number in the frame (inside 
> the frame is vertically centered, the title not). Is there a way to 
> align the chapter title with the chapter number?
>
>
>
> \starttexdefinition MyNumberChapterCommand #1
>     \inframed[frame=off,rightframe=on,framecolor=black,
>      rulethickness=1px,height=30pt]{#1\enspace}
> \stoptexdefinition
>
> \setuphead[chapter][style={\bfc},numbercommand=\MyNumberChapterCommand,
>     page=no]
>
> \starttext
>
> \startchapter
>   [title={Algemene Beginselen},
>    ownnumber={Boek I}]
>
> \samplefile{tufte}
>
> \stopchapter
>
> \startchapter
>   [title={Organisatorische Structuren},
>    ownnumber={Boek II}]
>
> \samplefile{tufte}
>
> \stopchapter
>
> \stoptext
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist :ntg-context@ntg.nl  /https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  :https://www.pragma-ade.nl  /https://context.aanhet.net  (mirror)
> archive  :https://github.com/contextgarden/context
> wiki     :https://wiki.contextgarden.net
> ___________________________________________________________________________________

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

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

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

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-03-19 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 11:59 [NTG-context] " Jeroen
2024-03-19 14:45 ` Hraban Ramm [this message]
2024-03-19 18:51   ` [NTG-context] " Jeroen
2024-03-19 19:09 ` Wolfgang Schuster

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=8acc5515-b309-43f8-bc99-8c24d2f758b8@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).