From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: embeddedxtable
Date: Mon, 25 May 2015 08:35:17 +0000 [thread overview]
Message-ID: <43EA352E-AA79-454C-A7DE-3BF9D680EA35@uva.nl> (raw)
In-Reply-To: <6B34903A-A803-4592-91BC-23CD84E80CE7@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1244 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.
It is a pity if \xmlstrip does not work. It is of course fairly essential that the whitespace between the tags can be ignored. I sincerely hope this will be looked into. Or could this be a special effect related to either the use of a buffer as source or to the embeddedxtable structure?
However, it doesn't seem the whole story. I removed all whitespace between the tags and the \unskip's from the code. In the result below you can see that removing the whitespace between the tags removes most of the spurious spaces, but not all of them. Another picture has the = embedded before the \xmlflush in \startrow and shows that still spurious space is injected. To me it looks if every row gets an extra space: three of them before the table and the last one after the table (but here I am guessing).
Hans van der Meer
[cid:23AE90F4-C415-4635-B1CD-E8E10E65B791]
[cid:EBC94BBA-8505-47C8-B5D3-20329BC1E06E]
[-- Attachment #1.1.2: Type: text/html, Size: 2321 bytes --]
[-- Attachment #1.2: table-1.jpg --]
[-- Type: image/jpeg, Size: 20965 bytes --]
[-- Attachment #1.3: table-2.jpg --]
[-- Type: image/jpeg, Size: 14335 bytes --]
[-- Attachment #2: 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 8:35 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 ` Meer, H. van der [this message]
2015-05-25 9:26 ` embeddedxtable Meer, H. van der
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=43EA352E-AA79-454C-A7DE-3BF9D680EA35@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).