ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Achim Jander <achim@jander.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Fwd: Re: xml-processing: missing or ungrouped '='
Date: Sat, 08 Jan 2011 15:23:19 +0100	[thread overview]
Message-ID: <4D287357.3000906@jander.de> (raw)
In-Reply-To: <3DB8F220-B0CC-403D-A13C-E5B59C6DEA39@uni-bonn.de>

Hi Thomas,
yes, of course you are right, but thats not making the problems. Its 
switched in while making a "minimal" example.
My problem or maxbe misunderstanding ist what I try to achieve with

\xmldoifelse{#1}{/num}{ownnumber=\xmlcommand{#1}{/num}{xml:ueberForceFlush}}{number=no} 


or in a more complex way:

\startxmlsetups xml:title
\startchapter[

%start here
number=\xmldoifelse{#1}{/num}{yes}{no}, %works
ownnumber=\xmldoifelse{#1}{/num}{\xmlcommand{#1}{/num}{xml:ueberForceFlush}}{},%works 

%stop here

title={\xmlflush{#1}},%works
]
\stopchapter
\stopxmlsetups

what I want to do is to process the part between %start here and %stop 
here in another template
which I can reuse in different hierarchies. But I cant find no way to do so.

Greetings,
Achim


Am 08.01.2011 14:07, schrieb Thomas A. Schmitz:
> On Jan 8, 2011, at 1:39 PM, Achim Jander wrote:
>
>> Hi Hans,
>> sorry, i'll try to make it more clear:
> Excuse me, your example makes my head spin. Just from looking at it, there appears to be a fundamental error: you flush the content of<title>  into a context \startchapter \stopchapter environment, AFAICS. But that's not right: the title is not the content of the chapter, but just its, errm, title. Can this be the reason why your code doesn't work?
>
> Thomas
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>

___________________________________________________________________________________
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:[~2011-01-08 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 10:20 Achim Jander
2011-01-08 11:15 ` Hans Hagen
2011-01-08 12:39   ` Achim Jander
2011-01-08 13:07     ` Thomas A. Schmitz
2011-01-08 14:23       ` Achim Jander [this message]
2011-01-08 17:00         ` Thomas A. Schmitz
2011-01-09 11:05           ` Achim Jander

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=4D287357.3000906@jander.de \
    --to=achim@jander.de \
    --cc=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).