From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: embeddedxtable
Date: Mon, 25 May 2015 09:26:08 +0000 [thread overview]
Message-ID: <E4253A3C-9530-4AA8-ABB0-3BFFD714CFAB@uva.nl> (raw)
In-Reply-To: <43EA352E-AA79-454C-A7DE-3BF9D680EA35@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1338 bytes --]
On 24 May 2015, at 22:53, Wolfgang Schuster <schuster.wolfgang@gmail.com<mailto:schuster.wolfgang@gmail.com>> wrote:
The spaces in the output are produced by the spaces between the tags (\xmlstrip doesn’t seem to work)
and you have to use a combination of \removeunwantedspaces and \ignorespaces to remove them.
There is something I do not understand and I hope you can explain this. The table is typeset by the \xmlflush{#1} in the table macro:
\startxmlsetups xmlcommon:table
Z\bgroup
\setupxtable[% Setup defaults
leftmargindistance=0pt,rightmargindistance=0pt,
offset=2pt,height=fit,width=fit,
align={center,lohi},columndistance=0pt]
\setupxtableparameters{#1}
\startlocationbox{#1}
\removeunwantedspaces
\startembeddedxtable X\xmlflush{#1}Y\stopembeddedxtable
\ignorespaces
\stoplocationbox
\egroup
\stopxmlsetups
The "X" and "Y" have been placed around the \xmlflush to see what happens. Why do I see them 3 times? It looks as if the embeddedxtable-line is called 3 times (or maybe 4 times once for each row with the last call vanishing). However, the table macro itself is called only once, the "Z" at the beginning proves that. I cannot explain this.
Another observation: inserting a newline after the <?xml>-tag also does insert a space just before the "Z".
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 3868 bytes --]
[-- Attachment #2: xtablespace.pdf --]
[-- Type: application/pdf, Size: 17236 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 prev parent reply other threads:[~2015-05-25 9:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 10:18 embeddedxtable Meer, H. van der
2015-05-24 10:36 ` embeddedxtable Meer, H. van der
2015-05-24 11:49 ` embeddedxtable Meer, H. van der
2015-05-24 13:06 ` embeddedxtable Meer, H. van der
2015-05-24 13:32 ` embeddedxtable Meer, H. van der
2015-05-24 15:31 ` embeddedxtable Wolfgang Schuster
2015-05-24 16:01 ` embeddedxtable Meer, H. van der
2015-05-24 18:16 ` embeddedxtable Wolfgang Schuster
2015-05-24 19:33 ` embeddedxtable Meer, H. van der
2015-05-24 20:53 ` embeddedxtable Wolfgang Schuster
2015-05-25 8:35 ` embeddedxtable Meer, H. van der
2015-05-25 9:26 ` Meer, H. van der [this message]
2015-05-25 10:59 ` embeddedxtable Wolfgang Schuster
2015-05-25 10:55 ` embeddedxtable Wolfgang Schuster
2015-05-25 9:06 ` embeddedxtable Meer, H. van der
2015-05-25 10:08 ` embeddedxtable Meer, H. van der
2015-05-25 11:05 ` embeddedxtable Wolfgang Schuster
2015-05-25 13:50 ` embeddedxtable Meer, H. van der
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=E4253A3C-9530-4AA8-ABB0-3BFFD714CFAB@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).