Re: [NTG-context] clutter with \start and \stop

2012-07-05 Thread Rogers, Michael K
On Jul 4, 2012, at 10:56 PM, luigi scarso wrote: On Thu, Jul 5, 2012 at 12:44 AM, Rogers, Michael K mrog...@emory.edumailto:mrog...@emory.edu wrote: XML seems a nice way for machines to deal with data. But it's not a very human way to speak. I mean, if I write \section{One}...\section{Two}

Re: [NTG-context] clutter with \start and \stop

2012-07-05 Thread luigi scarso
On Thu, Jul 5, 2012 at 12:44 AM, Rogers, Michael K mrog...@emory.eduwrote: On Jul 4, 2012, at 1:29 PM, Peter Münster wrote: On Wed, Jul 04 2012, Hans Hagen wrote: no, mixing this way is asking for troubles, if not now, than maybe in the future just use \section Yes, but isn't

Re: [NTG-context] clutter with \start and \stop

2012-07-05 Thread Rogers, Michael K
On Jul 5, 2012, at 1:23 AM, luigi scarso wrote: On Thu, Jul 5, 2012 at 12:44 AM, Rogers, Michael K mrog...@emory.edumailto:mrog...@emory.edu wrote: XML documents should form a tree, so a structure like \startA % A \startB % B \stopA % /A \stopB % /B won't translate to XML. Grouping in TeX

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread Hans Hagen
On 4-7-2012 00:51, Peter Münster wrote: Hi, Say I want Tufte in 2 columns and Knuth in 1 column: --8---cut here---start-8--- \starttext \startcolumns[n=2] \startsection[title=Tufte] \input tufte \stopsection \startsection[title=Tufte and Knuth]

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread Peter Münster
On Wed, Jul 04 2012, Hans Hagen wrote: no, mixing this way is asking for troubles, if not now, than maybe in the future just use \section Yes, but isn't \startsection the recommended method for the future and needed for XML output? -- Peter

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread Hans Hagen
On 4-7-2012 22:29, Peter Münster wrote: On Wed, Jul 04 2012, Hans Hagen wrote: no, mixing this way is asking for troubles, if not now, than maybe in the future just use \section Yes, but isn't \startsection the recommended method for the future and needed for XML output? Indeed, but there

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread Rogers, Michael K
On Jul 4, 2012, at 1:29 PM, Peter Münster wrote: On Wed, Jul 04 2012, Hans Hagen wrote: no, mixing this way is asking for troubles, if not now, than maybe in the future just use \section Yes, but isn't \startsection the recommended method for the future and needed for XML output? XML

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread Peter Münster
On Thu, Jul 05 2012, Rogers, Michael K wrote: Have you considered structuring your example like this?: The output is not the same... -- Peter ___ If your question is of interest to others as well,

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread Rogers, Michael K
On Jul 4, 2012, at 9:42 PM, Peter Münster wrote: On Thu, Jul 05 2012, Rogers, Michael K wrote: Have you considered structuring your example like this?: The output is not the same... Sorry, I misunderstood. This e-mail message (including any attachments)

Re: [NTG-context] clutter with \start and \stop

2012-07-04 Thread luigi scarso
On Thu, Jul 5, 2012 at 12:44 AM, Rogers, Michael K mrog...@emory.eduwrote: XML seems a nice way for machines to deal with data. But it's not a very human way to speak. I mean, if I write \section{One}...\section{Two} isn't it obvious that section One ends when section Two begins? Why

[NTG-context] clutter with \start and \stop

2012-07-03 Thread Peter Münster
Hi, Say I want Tufte in 2 columns and Knuth in 1 column: --8---cut here---start-8--- \starttext \startcolumns[n=2] \startsection[title=Tufte] \input tufte \stopsection \startsection[title=Tufte and Knuth] \input tufte \stopcolumns \input