From: drymartini@gmx.de (Robbie Pickering)
Subject: Re: Extraneous spaces in XML documents
Date: Mon, 10 Feb 2003 18:11:24 +0000 [thread overview]
Message-ID: <20030210181124.110B07E%05570575@gmx.de> (raw)
In-Reply-To: <5.1.0.14.1.20030210101155.027637a8@server-1>
Hans Hagen wrote:
>At 02:58 AM 2/10/2003 +0000, you wrote:
>
>
>>%this definition for the final version where the
>>% remaining comments are ignored
>>
>>\def\gobble#1{}
>>
>>\defineXMLargument [comment] \gobble
>
>you can use \gobbleoneargument here
Actually, \gobbleoneargument doesn't make any difference, but the
\XMLhideelement solution works perfectly. thanks
robbie
>
>the next solution may help:
>
>\defineXMLargument [comment] \XMLhideelement
>
>\long\def\XMLhideelement#1%
> {\futurelet\nexttoken\doXMLhideelement}
>
>\def\doXMLhideelement
> {\ifx\nexttoken\blankspace\removeunwantedspaces\fi}
>
next prev parent reply other threads:[~2003-02-10 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 2:58 Robbie Pickering
2003-02-10 9:26 ` Hans Hagen
2003-02-10 18:11 ` Robbie Pickering [this message]
2003-02-10 22:05 ` Simon Pepping
2003-02-11 13:30 ` Robbie Pickering
2003-02-11 20:18 ` Hans Hagen
2003-02-14 20:17 ` Simon Pepping
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=20030210181124.110B07E%05570575@gmx.de \
--to=drymartini@gmx.de \
--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).