ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>, ntg@scorecrow.com
Subject: Re: \definehead behaving differently when in an environment file versus \input'ed
Date: Sat, 2 May 2020 18:08:56 +0200	[thread overview]
Message-ID: <440d30f9-ea43-629c-9cba-396a19adcb4c@gmail.com> (raw)
In-Reply-To: <50AF511A-41B7-470A-A61C-29F63B1F083D@scorecrow.com>

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

ntg@scorecrow.com schrieb am 02.05.2020 um 17:14:
> I'm having trouble with \definehead behaving differently depending upon whether I process a file that includes it via a \input statement versus a project structure that calls it via an environment file referenced from a component file.
> 
> Overall aim:
> 
> I currently produce a small circulation journal in Word that I'm hoping to switch to ConTeXt. Each article is written by a different author and I currently provide a Word template so they can see how their article will eventually look and how long it is, etc. I want to do the same for the ConTeXt version so I have created a template tex file they can simply \input at the top of their article. Processing the single article gives the desired output. So far so good.
> 
> When I receive the articles, I want to use the project/product/component structure to allow me to produce an entire issue of the journal in one go. (I would simply comment out the \input line and add \startproject \startcomponent etc lines as necessary from each received article.)
> 
> Problem:
> 
> I've created a custom chapter heading, but the font size changes depending on whether I'm processing the \input version of the article or the \component version and I don't know why. Obviously, I would like the heading to be the same in each case so that authors see what I see and vice versa.

Your simple version sets the bodyfont before \starttext

%%%% begin example
\setupbodyfont[termes,14pt]

\starttext

{\bfc Cheesy double boxed title}

\stoptext
%%%% end example

while your complexer version loads the bodyfont after \starttext 
(\startcomponent acts here as \starttext)

%%%% begin example
\starttext

\setupbodyfont[termes,14pt]

{\bfc Cheesy double boxed title}

\stoptext
%%%% end example

When you use a non standard font size (e.g. 14pt) size switches are 
sometimes ignored even with ConTeXt's fallback mechanism.

To get the correct size for the header you can either use a standard 
font size (14.4pt) or you add the following line before you set the 
global font for your document (ConTeXt does this by itself in most cases 
but it can fail).

     \definebodyfontenvironment [14pt]

I attached a slightly modified version of your project structure to show 
a different way to organize documents. What I would change is to use a 
better section name for each article, e.g. \Article (or \startArticle) 
is better than \MyTitle as first level header in each article.

Wolfgang

[-- Attachment #2: journal.zip --]
[-- Type: application/x-zip-compressed, Size: 1601 bytes --]

[-- Attachment #3: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2020-05-02 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 15:14 ntg
2020-05-02 15:16 ` ntg
2020-05-02 16:08 ` Wolfgang Schuster [this message]
2020-05-02 21:34   ` ntg

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=440d30f9-ea43-629c-9cba-396a19adcb4c@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=ntg@scorecrow.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).