From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: xml comments
Date: Mon, 26 Nov 2001 16:03:19 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20011126155901.03f58e28@server-1> (raw)
In-Reply-To: <200111261420.fAQEK8v07913@sol.cs.uni-dortmund.de>
At 03:20 PM 11/26/2001 +0100, Patrick Gundlach wrote:
>\starttext
>\startbuffer
><!-- ignored comment -->
><one>one</one>
><!--not ignored -->
><two>two</two>
>\stopbuffer
>\processXMLbuffer
>\stoptext
>
>this should (as far as I understand the spec right) only output
>one two and not the second comment (<!--not ignored -->)
what exactly do you mean with 'output'? Should I treat <!--crap as being
<!-- crap?
>it seems that the missing space between the -- and the n is
>causing this effect.
>
>Thats what the xml rec says:
>[15]
>Comment
> ::=
> '<!--' ((Char - '-') | ('-' (Char - '-')))* '-->'
ah, i instantly get an head ache when i see this line of spec
>I hope you don't understand me wrong: with all my bug reports
>I don't want to complain
>about context, which is in my eyes a great piece of software.
a bug reports <> comment -)
there should not be bugs; also i know rather well which pieces of context
are coded ok (apart from bugs) and which parts are crap (which i have to
work on), so keep on mailing
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-11-26 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 14:20 Patrick Gundlach
2001-11-26 15:03 ` Hans Hagen [this message]
2001-11-26 15:07 ` Hans Hagen
2001-11-27 8:37 ` Taco Hoekwater
2001-11-27 9:43 ` Hans Hagen
2001-11-27 13:21 ` Taco Hoekwater
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=5.1.0.14.1.20011126155901.03f58e28@server-1 \
--to=pragma@wxs.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).