Re: [NTG-context] Do environment files add implicit \starttext ... \stopttext
On 11/18/22 15:52, Wolfgang Schuster via ntg-context wrote: > Pablo Rodriguez via ntg-context schrieb am 15.11.2022 um 16:06: >> [...] >> It looks like when --environment is used, ConTeXt assumes that the main >> source only contains text. Which makes sense (at least, to me). > > The reason why this does work has nothing to do with the environment > file, the only thing which is responsible to get a PDF with output > is the \setupbodyfont line. Many thanks for your explanation, Wolfgang. Now it is perfectly clear to me why this worked. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Do environment files add implicit \starttext ... \stopttext
Pablo Rodriguez via ntg-context schrieb am 15.11.2022 um 16:06: On 11/15/22 13:22, Denis Maier via ntg-context wrote: Hi, if I process an XML buffer, I’ve noticed I need to wrap the \xmlprocessbuffer in a \starttext ... \stoptext pair. [] However, if I have the XML and the setups in dedicated files, there seems to be no need for \starttext ... \stoptext. [] Therefore my question: Does the use –environment automatically wrap the processed file in \starttext ... stoptext ? Hi Denis, try a source file with this contents: \ConTeXt\ is great. with the following environment: \setuppapersize[A6] \setupbodyfont[pagella] It looks like when --environment is used, ConTeXt assumes that the main source only contains text. Which makes sense (at least, to me). The reason why this does work has nothing to do with the environment file, the only thing which is responsible to get a PDF with output is the \setupbodyfont line. Better examples are begin example 1 \CONTEXT\ is great. end example 1 and begin example 2 \setupbodyfont[modern] \CONTEXT\ is great. begin example 2 where the output of the first example is broken. To ensure the document exists in a proper manner ConTeXt inserts \stoptext at the end of the document but there is never a \starttext inserted at any point when you process a regular tex file. You should also notice a message like system > invalid \starttext ... \stoptext structure on the terminal. Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Do environment files add implicit \starttext ... \stopttext
Denis Maier via ntg-context schrieb am 15.11.2022 um 13:22:
Hi,
if I process an XML buffer, I’ve noticed I need to wrap the
\xmlprocessbuffer in a \starttext ... \stoptext pair.
[...]
However, if I have the XML and the setups in dedicated files, there
seems to be no need for \starttext ... \stoptext.
[...]
Running
context text.xml –environment=setups.tex
gives me a proper PDF without errors.
Therefore my question:
Does the use –environment automatically wrap the processed file in
\starttext ... stoptext ?
If not, what’s the reason for this behaviour? Am I missing something?
ConTeXt uses the file extension to decide who it should handle document,
in your case the extension is xml and the file is processed as
\starttext
\xmlprocess{main}{...}{}
\stoptext
The same thing happens when you have CLD document and use cld as file
extension.
For more details you can look at the processjob function in cont-run.lmt.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Do environment files add implicit \starttext ... \stopttext
> -Ursprüngliche Nachricht- > Von: ntg-context Im Auftrag von Pablo > Rodriguez via ntg-context > Gesendet: Dienstag, 15. November 2022 16:07 > An: Denis Maier via ntg-context > Cc: Pablo Rodriguez > Betreff: Re: [NTG-context] Do environment files add implicit \starttext ... > \stopttext > > On 11/15/22 13:22, Denis Maier via ntg-context wrote: > > Hi, > > > > if I process an XML buffer, I’ve noticed I need to wrap the > > \xmlprocessbuffer in a \starttext ... \stoptext pair. > > [] > > However, if I have the XML and the setups in dedicated files, there > > seems to be no need for \starttext ... \stoptext. > > [] > > Therefore my question: > > > > Does the use –environment automatically wrap the processed file in > > \starttext ... stoptext ? > > Hi Denis, > > try a source file with this contents: > > \ConTeXt\ is great. > > with the following environment: > > \setuppapersize[A6] > \setupbodyfont[pagella] > > It looks like when --environment is used, ConTeXt assumes that the main > source only contains text. Which makes sense (at least, to me). > Thanks, Pablo. Yes, that makes sense. Denis ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Do environment files add implicit \starttext ... \stopttext
On 11/15/22 13:22, Denis Maier via ntg-context wrote: > Hi, > > if I process an XML buffer, I’ve noticed I need to wrap the > \xmlprocessbuffer in a \starttext ... \stoptext pair. > [] > However, if I have the XML and the setups in dedicated files, there > seems to be no need for \starttext ... \stoptext. > [] > Therefore my question: > > Does the use –environment automatically wrap the processed file in > \starttext ... stoptext ? Hi Denis, try a source file with this contents: \ConTeXt\ is great. with the following environment: \setuppapersize[A6] \setupbodyfont[pagella] It looks like when --environment is used, ConTeXt assumes that the main source only contains text. Which makes sense (at least, to me). Just in case it might help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Do environment files add implicit \starttext ... \stopttext
Hi,
if I process an XML buffer, I've noticed I need to wrap the \xmlprocessbuffer
in a \starttext ... \stoptext pair.
%%%
\startbuffer[test]
a paragraph of text
another paragraph of text
\stopbuffer
\startxmlsetups xml:demo
\xmlsetsetup{\xmldocument}{document|p}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:demo}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:p
\xmlflush{#1}\endgraf
\stopxmlsetups
\starttext
\xmlprocessbuffer{test}{test}{}
\stoptext
%%%
However, if I have the XML and the setups in dedicated files, there seems to be
no need for \starttext ... \stoptext.
%%% text.xml
a paragraph of text
another paragraph of text
%%%
%%% setups.tex
\startxmlsetups xml:demo
\xmlsetsetup{\xmldocument}{document|p}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:demo}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:p
\xmlflush{#1}\endgraf
\stopxmlsetups
%%%
Running
context text.xml -environment=setups.tex
gives me a proper PDF without errors.
Therefore my question:
Does the use -environment automatically wrap the processed file in \starttext
... stoptext ?
If not, what's the reason for this behaviour? Am I missing something?
Best,
Denis
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Questions about \starttext
Tue, Apr 03, 2018 ve 09:12:31AM +0200 Hans Hagen napsal(a): # On 4/3/2018 12:02 AM, John Culleton wrote: # >A reasonable approach to a Context file includes preliminary # >information before the first printed page. My basic master file # >looks like this : # > # > ... # # in the distribution there are a lot of manuals of which the setup # demonstrates ways to organize ... one probably not known to all is # # \startdocument[settings] ... \stopdocument ok, where can I find it? The thing I am a bit confused and which was the main reason of my question, is why the compiler does not report the unbalanced pair of start/stop in this case. Tomáš # 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 # ___ Tomáš Hála Mendelova univerzita, Provozně ekonomická fakulta, ústav informatiky Zemědělská 1, CZ-613 00 Brno, tel. +420 545 13 22 28 http://akela.mendelu.cz/~thala ___ 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 ___
Re: [NTG-context] Questions about \starttext
On 4/3/2018 12:02 AM, John Culleton wrote: A reasonable approach to a Context file includes preliminary information before the first printed page. My basic master file looks like this : > > ... in the distribution there are a lot of manuals of which the setup demonstrates ways to organize ... one probably not known to all is \startdocument[settings] ... \stopdocument 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 ___
Re: [NTG-context] Questions about \starttext
From: "Wolfgang Schuster" <schuster.wolfg...@gmail.com> Sent: Monday, April 2, 2018 2:41 PM To: "mailing list for ConTeXt users" <ntg-context@ntg.nl> Subject: Re: [NTG-context] Questions about \starttext Tomas Hala 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 ___ 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 ___
Re: [NTG-context] Questions about \starttext
A reasonable approach to a Context file includes preliminary information before the first printed page. My basic master file looks like this : \input variables.tex\relax \input layout.tex\relax \input macros.tex\relax \input fonts.tex\relax \starttext\relax %\showlayout \startfrontmatter \input half.tex\relax \startstandardmakeup \null \stopstandardmakeup \input title.tex\relax \input copy.tex\relax \input ded.tex\relax \input contents.tex\relax \input preface.tex\relax %\startstandardmakeup \relax %\null \relax %\stopstandardmakeup \relax \stopfrontmatter \startbodymatter \input body3.tex\relax \stopbodymatter\relax \startbackmatter\relax \input bib.tex\relax \input notes.tex \input index.tex \stopbackmatter \stoptext\relax By loading my usual macros in the macros file, standard items like author's name in a variables file and so on I save much time, typing and errors. From: "Wolfgang Schuster" <schuster.wolfg...@gmail.com> Sent: Monday, April 2, 2018 2:41 PM To: "mailing list for ConTeXt users" <ntg-context@ntg.nl> Subject: Re: [NTG-context] Questions about \starttext Tomas Hala 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 ___ 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 ___
Re: [NTG-context] Questions about \starttext
Tomas Hala <mailto:tomas.h...@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 ___ 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 ___
[NTG-context] Questions about \starttext
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? 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 Minimal example #2 (tested on TL2015, TL2016, TL2017, current CTX from the Garden): text% in this case, the "text" is not shipped out \stoptext If this is ok, it does not correspond to our garden wiki (http://wiki.contextgarden.net/Command/starttext): "The first command takes care of a number of initializations, and the last command tells TEX that processing can stop. When this command is left out TEX will display a * (a star) on the command line at the end of the job. TEX will expect a command, for example \end." Wishes, Tomáš Tomáš Hála Mendel's University of Agriculture and Forestry, Faculty of Business and Economics, Department of Informatics Mendelova zemědělská a lesnická univerzita, Provozně ekonomická fakulta, Ústav informatiky, Zemědělská 5, CZ-613 00 Brno, tel. +420 545 13 22 28 http://www.mendelu.cz/~thala ___ 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 ___
[NTG-context] tekst before \starttext?
I thought that typesetting should start after \startext and that anything before it should be ignored. That is indeed the case with the following input: ABC \starttext CONTENT \stoptext But add a \setupbodyfont and suddenly the ABC appears: \setupbodyfont[lmodern] ABC \starttext CONTENT \stoptext Is this correct behaviour? It is a nuisance because this phenomenon causes a spurious blank page appears in my book. It might be a recently introduced because I did not experience this in the past. ConTeXt ver: 2013.04.16 12:08 MKIV beta fmt: 2013.4.16 Hans van der Meer ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] tekst before \starttext?
Am 16.04.2013 um 19:56 schrieb Meer, H. van der h.vanderm...@uva.nl: I thought that typesetting should start after \startext and that anything before it should be ignored. That is indeed the case with the following input: ABC \starttext CONTENT \stoptext But add a \setupbodyfont and suddenly the ABC appears: \setupbodyfont[lmodern] ABC \starttext CONTENT \stoptext Is this correct behaviour? It is a nuisance because this phenomenon causes a spurious blank page appears in my book. It might be a recently introduced because I did not experience this in the past. There appears nothing in the first case because context delays font loading until \starttext but when you add \setupbodyfont a font is loaded and text is no visible. When you something in your document before \starttext which creates a blank page something is wrong with a macro and you put something there which shouldn’t be there. Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] \typesetbuffer adds \starttext ... \stoptext
Hello, It would be nice, if \typesetbuffer wouldn't add anything to the buffer. Here an example, where the outer \starttext ... \stoptext environment deranges: \starttext \startbuffer[pdf-pages] \setuppapersize[A7, landscape] \showframe \starttext page 1 \page page 2 \stoptext \stopbuffer \typesetbuffer[pdf-pages][page=2, frame=on, width=10cm] \stoptext -- Peter ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \typesetbuffer adds \starttext ... \stoptext
Am 30.01.2011 um 19:52 schrieb Peter Münster: Hello, It would be nice, if \typesetbuffer wouldn't add anything to the buffer. Here an example, where the outer \starttext ... \stoptext environment deranges: Why, context ignores the inner starttext/stoptext pair. Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \typesetbuffer adds \starttext ... \stoptext
Wolfgang Schuster schuster.wolfg...@googlemail.com writes: It would be nice, if \typesetbuffer wouldn't add anything to the buffer. Here an example, where the outer \starttext ... \stoptext environment deranges: Why, context ignores the inner starttext/stoptext pair. Wrong interpretation of the problem: it's the \setuppapersize[][samesized] that is broken... Nevertheless: are there situations, where the outer starttext/stoptext could cause some trouble? -- Peter ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \typesetbuffer adds \starttext ... \stoptext
On Sun, Jan 30, 2011 at 19:52, Peter Münster pmli...@free.fr wrote: Hello, It would be nice, if \typesetbuffer wouldn't add anything to the buffer. Yep, I agree that. Don't know why need add something to buffer ? ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \typesetbuffer adds \starttext ... \stoptext
Am 30.01.2011 um 20:23 schrieb Vnpenguin: On Sun, Jan 30, 2011 at 19:52, Peter Münster pmli...@free.fr wrote: Hello, It would be nice, if \typesetbuffer wouldn't add anything to the buffer. Yep, I agree that. Don't know why need add something to buffer ? \typesetbuffer add \starttext before and \stoptext after the buffer because it write the buffer content to a external file and process this file as a separate document which can be included as figure. This is a useful feature for documentation. Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \typesetbuffer adds \starttext ... \stoptext
Am 30.01.2011 um 20:20 schrieb Peter Münster: Nevertheless: are there situations, where the outer starttext/stoptext could cause some trouble? Don’t think so because when you use the project structure you have \startproduct \startcomponent … \stopcomponent \startcomponent … \stopcomponent \stopproduct where both \startproduct and \startcomponent act as \starttext and only the first is is used as real \starttext while the others are ignored. Wolfgang ___ 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
