From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Questions about \starttext
Date: Mon, 02 Apr 2018 20:39:32 +0200 [thread overview]
Message-ID: <5AC278E4.5090802@gmail.com> (raw)
In-Reply-To: <20180320113810.GA11776@akela.mendelu.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1972 bytes --]
> Tomas Hala <mailto:tomas.hala@mendelu.cz>
> 20. März 2018 um 12:43
> Hi all,
>
> doing some tests I discovered two interesting facts.
>
> The first is that commands \starttext and \stoptext do not behave as a
> group.
>
> Minimal example (tested on TL2015, TL2016, TL2017, current CTX from
> the Garden):
>
> \starttext
> text
> \starttext
> \bf text
> \stoptext
> text % this text is in bold, too.
> \stoptext
>
> Is this the expected behaviour, or not?
Opening a group with \starttext makes no sense because there is nothing
after \stoptext.
The possibility to nest \starttext is necessary when you \startproduct
etc. where components
can be be documents on its own and this means \startcomponent includes
\starttext in its
definition.
> The second interesting thing is that the unbalanced document is
> compiled without protests:
>
> Minimal example #1 (tested on TL2015, TL2016, TL2017, current CTX from
> the Garden):
>
> \starttext
> text % in this case, the "text" is shipped out
Take a look at the command line when you process a file and you should
see something like this:
mtx-context | run 1: luatex --fmt="[...]/cont-en" --jobname="test"
[...] --c:input="./test.tex" [...] "cont-yes.mkiv"
As you can see the luatex engine processes the file cont-yes.mkiv and
not your document
which put as argument to context. Your document is just read by
cont-yes.mkiv and at the
end of the document ConTeXt inserts an extra \stoptext which is ignored
when your document
is valid (equal number of \starttext and \stoptext).
> Minimal example #2 (tested on TL2015, TL2016, TL2017, current CTX from
> the Garden):
>
> text % in this case, the "text" is not shipped out
> \stoptext
The reason why no text appears is that ConTeXt doesn’t load the default
fonts
untill \starttext. The reason for this is to is a gain in speed and you
save resources.
You can test this by adding \setupbodyfont[modern] at the begin of your
example.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3641 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-04-02 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:43 Tomas Hala
2018-04-02 18:39 ` Wolfgang Schuster [this message]
2018-04-02 22:02 ` John Culleton
2018-04-03 7:12 ` Hans Hagen
2018-04-15 8:54 ` Tomas Hala
2018-04-02 22:03 ` John Culleton
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=5AC278E4.5090802@gmail.com \
--to=schuster.wolfgang@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).