ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug with columnsets in projects
Date: Wed, 29 Sep 2010 09:35:06 +0200	[thread overview]
Message-ID: <E3762DD6-6ECB-47CC-BE3C-F955F4239948@st.estfiles.de> (raw)
In-Reply-To: <EA927643-5BAC-44DD-A0ED-4B5126CF1CF2@st.estfiles.de>


Am 29.09.2010 um 09:27 schrieb Steffen Wolfrum:

> 
> Am 28.09.2010 um 16:25 schrieb Steffen Wolfrum:
> 
>> Hi,
>> 
>> please see attached example:
>> 
>> If you run the file containing the columnset directly (chap_X) it runs fine.
>> 
>> But if you run MyProduct.tex there is an error:
>> 
>> 
>> 
>> ! Missing } inserted.
>> 
>> system          > error on line 21 in file MyProduct.tex: Missing  ...
>> 
>> 11     %\component TOCtocDatei
>> 12     \stopfrontmatter
>> 13     %
>> 14     \startbodymatter
>> 15     \component chap_X
>> 16     %\component teil_1
>> 17     %\component teil_2
>> 18     %\component teil_3
>> 19     %\component teil_4
>> 20     %\component teil_5
>> 21 >>  \stopbodymatter
>> 22     %
>> 23     \startbackmatter
>> 24     %\component register
>> 25     \stopbackmatter
>> 26     \stopproduct
>> 
>> <inserted text> 
>>               }
>> <to be read again> 
>>                  \endgroup 
>> l.21 \stopbodymatter
>> 
>> ? 
>> 
>> 
>> 
>> 
>> This is with MkIV.
> 
> 
> 
> If I would use columns instead of columnsets there is also an error, but different:
> 
> systems         : end file chap_X at line 15
> structure       : end of sectionblock bodypart
> backends        > using xmp file '/Users/steffen/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
> pages           > flushing realpage 1, userpage 1, subpage 1
> structure       : begin of sectionblock backpart
> structure       : end of sectionblock backpart
> )
> *


In this case (columns) it would help to include the file not as a \component but as a regular file via \input.
This runs without "*" error.

Yet, trying the same with the original case (columnsets) fails: this just does not get processed!
Again a "}" is supposed to be missing.


Can someone confirm this? Is there a workaround?

Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-09-29  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 14:25 Steffen Wolfrum
2010-09-29  7:27 ` Steffen Wolfrum
2010-09-29  7:35   ` Steffen Wolfrum [this message]
2010-09-29 18:05 ` Wolfgang Schuster
2010-09-29 18:51   ` Steffen Wolfrum
2010-09-29 19:08     ` Wolfgang Schuster

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=E3762DD6-6ECB-47CC-BE3C-F955F4239948@st.estfiles.de \
    --to=context@st.estfiles.de \
    --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).