ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Xan <dxpublica@telefonica.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \starttyping while processing XML causing error
Date: Thu, 27 Mar 2014 09:46:11 +0100	[thread overview]
Message-ID: <20140327094611.df1dcee8dc37c4f8c22f28cd@telefonica.net> (raw)

Hi,

I have this minimal example:

1) Tasques.context:

\environment ./entorn-xml

\starttext

A
\xmlprocessfile{demo}{./dades.xml}{}
B
\stoptext


2) entorn-xml.tex:

\startxmlsetups xml:demo:base
  \xmlsetsetup{demo}{*}{-}
  \xmlsetsetup{demo}{things|code|}{xml:demo:*}
\stopxmlsetups

\xmlregisterdocumentsetup{demo}{xml:demo:base}

\startxmlsetups xml:demo:things
  \xmlflush{#1}
\stopxmlsetups


%TODO: startcode: http://www.ntg.nl/pipermail/ntg-context/2012/064750.html
\startxmlsetups xml:demo:code
  \bigskip
  \startlines\xmlflush{#1}\stoplines
\stopxmlsetups


3) dades.xml:

<?xml version='1.0' standalone='yes' encoding="UTF-8"?>
<things>
  <code>
  [root@serviedre ~]# pacman -Syu
:: Synchronizing package databases...
 core                     193.0 KiB  50.0K/s 00:04 [######################] 100%
 extra                                            2037.1 KiB   166K/s 00:12 [##########################################] 100%
 community                                           2.2 MiB   374K/s 00:06 [##########################################] 100%
 alarm                                              55.6 KiB   242K/s 00:00 [##########################################] 100%
 aur                                                64.0 KiB   288K/s 00:00 [##########################################] 100%
:: Starting full system upgrade...
warning: linux-sun4i: ignoring package upgrade (3.4.79-1 => 3.4.79-2)
warning: linux-sun4i-headers: ignoring package upgrade (3.4.79-1 => 3.4.79-2)
 there is nothing to do
  </code>
</things>



When I compile tasques.context, all is ok, but when I substitute the \startlines \stoplines with \starttyping \stoptyping context never ends.

Is that a bug? 
I just found [this](http://www.ntg.nl/pipermail/ntg-context/2012/064750.html), but really no solution. Since 2012 I suppose many things are changed so I ask.

Why doesn't it work?

Thanks in advance,
Xan.

___________________________________________________________________________________
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:[~2014-03-27  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27  8:46 Xan [this message]
2014-03-27 21:49 ` Hans Hagen
2014-03-28  8:13 ` Xan
2014-03-28  8:56   ` Hans Hagen
2014-03-28 13:59     ` Xan
2014-03-28 14:04     ` Xan
2014-03-28 14:41     ` Xan

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=20140327094611.df1dcee8dc37c4f8c22f28cd@telefonica.net \
    --to=dxpublica@telefonica.net \
    --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).