From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: ConTeXt NTG <ntg-context@ntg.nl>
Subject: getting xml instead of context
Date: Tue, 20 Mar 2012 21:39:59 +0000 [thread overview]
Message-ID: <03A7829F-B1B2-4EA2-B227-7B1AD31A6B8C@uva.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]
In the processing of incoming xml-data this is typeset as is, not as processed text.
Thus for example: with \xmlflush{#1} the incoming data: "<text>its_content</text>" is not typeset as: "its_content", but as: <text>its_content</text>.
Substitution of \xmlcontext{#1}{.} for \xmlflush{#1} makes everything go away.
Allthough my program is a bit too long to present here, a minimal example is the application of \xmlstripped{#1}{.} instead of \xmlflush{#1}; it has the same result.
The output below shows how things looks and clarifies the issue; see the second answer of the multiple choice.
How to process these data to neatly typeset material?
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 2511 bytes --]
[-- Attachment #2: xm-test-exam.pdf --]
[-- Type: application/pdf, Size: 23118 bytes --]
[-- Attachment #3: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2012-03-20 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 21:39 Meer, H. van der [this message]
2012-03-24 15:06 ` Hans Hagen
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=03A7829F-B1B2-4EA2-B227-7B1AD31A6B8C@uva.nl \
--to=h.vandermeer@uva.nl \
--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).