Re: [NTG-context] weird behavior of brackets in block quotations

Thanks, Wolfgang! That is very helpful. Alan On Mon, Mar 7, 2016 at 3:56 PM, Wolfgang Schuster < schuster.wolfg...@gmail.com> wrote: > Alan Bowen > 7. März 2016 um 21:52 > We use “[...]” in quotations to indicate departures from the written text. > > In the latest beta,

Re: [NTG-context] in next beta

Hans Hagen 4. März 2016 um 12:01 \starttext \setuplistalternative [c] [filler=symbol, symbol=\hbox to .25em{\periodcentered}, symcolor=darkred, symstyle=\bf] \startsubject[title=Contents]

Re: [NTG-context] weird behavior of brackets in block quotations

Alan Bowen 7. März 2016 um 21:52 We use “[...]” in quotations to indicate departures from the written text. In the latest beta, “[...]” is a problem in block quotations and [] does not appear in the output. \setupdelimitedtext [blockquote]

[NTG-context] weird behavior of brackets in block quotations

We use “[...]” in quotations to indicate departures from the written text. In the latest beta, “[...]” is a problem in block quotations and [] does not appear in the output. \setupdelimitedtext [blockquote] [before={\blank[small,fixed]}, after={\blank[small,fixed]}] \starttext

Re: [NTG-context] How to avoid overriding a control sequence?

On 2016-03-07 20:16:45 +, Hans Hagen said: On 3/7/2016 7:40 PM, Nicola wrote: How do I check in ConTeXt whether a control sequence is already defined (to avoid redefining it by accident)? Marginally related to the above, I have tried to use \show, only to discover, to my surprise, that it

Re: [NTG-context] Bug in startitemize

Thanks Wolfgang, Your patch does indeed solve the problem, after rebuilding with context --make —all Best regards: OK > On 07 Mar 2016, at 20:46, Wolfgang Schuster > wrote: > >> Otared Kavian 7. März 2016 um 20:28 >> Hi Hans, >> >> It seems that with

Re: [NTG-context] How to avoid overriding a control sequence?

On 3/7/2016 7:40 PM, Nicola wrote: How do I check in ConTeXt whether a control sequence is already defined (to avoid redefining it by accident)? Marginally related to the above, I have tried to use \show, only to discover, to my surprise, that it gives an error. For example: \show\NL \end

Re: [NTG-context] Bug in startitemize

Otared Kavian 7. März 2016 um 20:28 Hi Hans, It seems that with the new beta (ConTeXt ver: 2016.03.04 10:39 MKIV beta fmt: 2016.3.7), there is a bug with random itemization. I cannot tell exactly when this feature has been broken. The problem is that for instance in

[NTG-context] Bug in startitemize

Hi Hans, It seems that with the new beta (ConTeXt ver: 2016.03.04 10:39 MKIV beta fmt: 2016.3.7), there is a bug with random itemization. I cannot tell exactly when this feature has been broken. The problem is that for instance in the following example, sometimes the item C is repeated three

Re: [NTG-context] How to avoid overriding a control sequence?

On 2016-03-07 18:47:20 +, luigi scarso said: On Mon, Mar 7, 2016 at 7:40 PM, Nicola wrote: How do I check in ConTeXt whether a control sequence is already defined (to avoid redefining it by accident)? kind of  \ifdefined\writebanner \else

Re: [NTG-context] How to avoid overriding a control sequence?

On Mon, Mar 7, 2016 at 7:40 PM, Nicola wrote: > How do I check in ConTeXt whether a control sequence is already > defined (to avoid redefining it by accident)? > > kind of \ifdefined\writebanner \else \unexpanded\def\writebanner{\writestring} \fi ? -- luigi

[NTG-context] How to avoid overriding a control sequence?

How do I check in ConTeXt whether a control sequence is already defined (to avoid redefining it by accident)? Marginally related to the above, I have tried to use \show, only to discover, to my surprise, that it gives an error. For example: \show\NL \end Does ConTeXt override some of TeX

[NTG-context] non-splitting footnotes

Hi folks, http://context.fedarch.org/Context/trapChapter16_petra.pdf page 7-8 there's a very large space due to a footnote. I've tried to induce footnote splitting (I just updated to mtx-context | current version: 2016.03.04 10:39) but it doesn't seem to work. All the discussion on this list