ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: more xml in mkiv
Date: Mon, 14 Jul 2008 17:21:36 +0200	[thread overview]
Message-ID: <5BF92277-5B7F-4894-B46E-BB0A138D4C72@gmail.com> (raw)
In-Reply-To: <C082258B-7DD0-4C0C-8868-720F94F283EB@uni-bonn.de>


Am 14.07.2008 um 16:45 schrieb Thomas A. Schmitz:

> Hi all,
>
> I'm resurrecting an ooooold thread and top-posting... For details, see
> the post below. The problem was that the content of itemizations
> sometimes disappeared in xml processed by mkiv. I emphasize
> "sometimes": now you see it, now you don't... I can't really post a
> minimal example that will be certain to display the effect, but I
> have, since May, discovered one thing:
>
> this code:
>
> <item>
>   A
> </item>
>
> will sometimes make the A disappear. This code:
>
> <item>A</item>
>
> will always work correctly. So Hans, a shot in the dark: can it be
> that your lpeg xml parser can, under certain circumstances, have
> trouble with linebreaks within the xml-subtree it is trying to pick
> up? That would explain the mystery which had me baffled back in May.
>
> All best
>
> Thomas

Can you test the following definition for item a while:

\startxmlsetups xml:item
   \startitem
   \xmlflush{#1}
   \stopitem
\stopxmlsetups

Regards,
Wolfgang

> On Mar 25, 2008, at 4:29 PM, Wolfgang Schuster wrote:
>
>> On Mon, Mar 24, 2008 at 10:28 PM, Thomas A. Schmitz
>> <thomas.schmitz@uni-bonn.de> wrote:
>>> Hi all,
>>>
>>> I played some more with the new mkiv xml mechanism and am beginning
>>> to
>>> see the light: some things that turned out to be very difficult (at
>>> least for me) with the "old" mechanism are easy now. However, I  
>>> still
>>> have a couple of questions:
>>>
>>> 1. I have this minimal file test.xml:
>>>
>>> <document>
>>> <itemize>
>>>   <item>
>>>     one
>>>   </item>
>>>   <item>
>>>     two
>>>   </item>
>>>   <item>
>>>     three
>>>   </item>
>>> </itemize>
>>> </document>
>>>
>>> and this minimal environment test-style.tex:
>>> \startxmlsetups xml:mysetups
>>>      \xmlsetsetup{\xmldocument}{document|itemize|item}{xml:*}
>>> \stopxmlsetups
>>>
>>> \xmlregistersetup{xml:mysetups}
>>>
>>> \startxmlsetups xml:document
>>>      \xmlflush{#1}
>>> \stopxmlsetups
>>>
>>> \startxmlsetups xml:itemize
>>>      \startitemize
>>>      \xmlflush{#1}
>>>      \stopitemize
>>> \stopxmlsetups
>>>
>>> \startxmlsetups xml:item
>>>      \item \xmlflush{#1}
>>> \stopxmlsetups
>>>
>>> \starttext
>>> \xmlprocess{main}{\inputfilename}{}
>>> \stoptext
>>>
>>> When I run texexec --lua --env=test-style test.xml, I get output  
>>> only
>>> for item "three," not for one and two. What am I doing wrong?
>>>
>>> 2. In every run, I get this warning:
>>>
>>> TeXUtil | check loading of file 'test-style', begin/end problem
>>>
>>> I don't see anything wrong with my files, though. Is this harmless?
>>>
>>>
>>> 3. I have a structure like this to get numbered labels:
>>>
>>>   <lemmasection>
>>>     <label>1234</label>
>>>     <content>
>>>      blahblah
>>>     </content>
>>>   </lemmasection>
>>
>> you could try something like
>>
>> \startxmlsetups xml:lemma
>> \startlemma{\xmlfirst{#1}{label}}
>> \ignorespaces\xmlfirst{#1}{content}\removeunwatedspaces
>> \stoplemma
>> \stopxmlsetups
>>
>> 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  : https://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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-07-14 15:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 21:28 Thomas A. Schmitz
2008-03-24 22:34 ` Hans Hagen
2008-03-25 12:17   ` Thomas A. Schmitz
2008-03-25 12:42     ` Wolfgang Schuster
2008-03-25 13:39       ` Thomas A. Schmitz
2008-03-25 14:38         ` Peter Rolf
2008-03-25 15:14           ` Thomas A. Schmitz
2008-03-25 15:36             ` Peter Rolf
2008-03-25 17:08               ` Thomas A. Schmitz
2008-03-25 17:32                 ` Peter Rolf
2008-03-25 17:51             ` Hans Hagen
2008-03-25 15:29 ` Wolfgang Schuster
2008-07-14 14:45   ` Thomas A. Schmitz
2008-07-14 15:21     ` Wolfgang Schuster [this message]
2008-07-14 16:22       ` Thomas A. Schmitz

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=5BF92277-5B7F-4894-B46E-BB0A138D4C72@gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).