ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: \startXML vs \startPARSEDXML
Date: Wed, 11 May 2022 18:19:15 +0200	[thread overview]
Message-ID: <4b421232-1245-83ec-abf4-b875befa45b0@gmx.es> (raw)
In-Reply-To: <a3d855d99fe041a4bf46ef463d8c41e2@unibe.ch>

On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> Hi everyone,
>
> the wikipage on \starttyping
> (https://wiki.contextgarden.net/Command/_starttyping
> <https://wiki.contextgarden.net/Command/_starttyping>) says there are
> some dedicated commands, e.g. \startXML and \startPARSEDXML. How do they
> differ?

Hi Denis,

yesterday I had to start using xml instead of parsed-xml.

See the difference:

  \setuppapersize[A4, landscape]
  \setupbodyfont[dejavu]
  \starttext
  \startxtable[option=stretch]
  \startxrow[offset=1ex]
  \startxcell
  \startXML
  <?xml version="1.0" encoding="UTF-8"?>
  <xml>
   <documento xml:lang="es">
    <sección id="sect">
     <título>Anuncio</título>
     <p xml:lang="grc">&#954;&#945;&#955;&#940;</p>
     <p class="traducción">Belleza</p>
    </sección>
   </documento>
  </xml>
  \stopXML
  \stopxcell
  \startxcell
  \startPARSEDXML
  <?xml version="1.0" encoding="UTF-8"?>
  <xml>
   <documento xml:lang="es">
    <sección id="sect">
     <título>Anuncio</título>
     <p xml:lang="grc">&#954;&#945;&#955;&#940;</p>
     <p class="traducción">Belleza</p>
    </sección>
   </documento>
  </xml>
  \stopPARSEDXML
  \stopxcell
  \stopxrow
  \stopxtable
  \stoptext

I wonder why attribute values are parsed so. I don’t know whether this
might be a bug (but this is why I replaced "parsed-xml" with "xml" in my
code).

If I could ask you a favor, would you be so kind to confirm whether
\xmlpos and \xmldepth are misbehaving or not (as already reported in
https://mailman.ntg.nl/pipermail/ntg-context/2022/105495.html and
https://mailman.ntg.nl/pipermail/ntg-context/2022/105604.html)?

Many thanks for your help,

Pablo
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-05-11 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  9:47 Denis Maier via ntg-context
2022-05-11 16:19 ` Pablo Rodriguez via ntg-context [this message]
2022-05-12  7:49   ` Denis Maier via ntg-context

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=4b421232-1245-83ec-abf4-b875befa45b0@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).