From: Hans Hagen <pragma@wxs.nl>
Subject: Fwd: BOUNCE ntg-context@let.uu.nl: Non-member submission from [robbieinsel@freeuk.com (Robbie Pickering )]
Date: Fri, 30 Aug 2002 00:32:55 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020830003239.03c4e490@server-1> (raw)
>Simon Pepping wrote:
>
> >> \defineXMLenvironment [DEFN] {}{.}
> >> to add a full stop after the definition. It would be nice, though, to be
> >> able to automatically add a colon instead in those cases where the DEFN
> >> environment is immediately followed by a EGPH.
> >
> >This is very difficult, because your tagging has no moment at which
> >this can be concluded: </DEFN> is too early to know, but when there is
> >no following EGPH, there is nothing that can trigger the period or
> >colon.
>
>I see your point, but couldn't the trigger be "anything which is not
><EGPH>" ?
>
>
>It would be easier if the whole definition would be in a
> >container: <definition><DNUM/><DEFN/><EGPH/></definition>. Then you
> >can save EGPH, and </definition> could typeset it with preceding
> >colon, or it could typeset a period.
>
>this is a good idea, I don't want to modify the XML by adding
>punctuation marks, but extra tagging might be possible.
>
>it occurs to me that if we could determine whether EGPH actually
>contains anything this would be simple, no?
>
>================================================================
>Deze e-mail is door E-mail VirusScanner van Planet Internet gecontroleerd
>op virussen.
>Op http://www.planet.nl/evs staat een verwijzing naar de actuele lijst
>waar op wordt gecontroleerd.
-------------------------------------------------------------------------
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
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next reply other threads:[~2002-08-29 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 22:32 Hans Hagen [this message]
2002-08-29 22:33 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=5.1.0.14.1.20020830003239.03c4e490@server-1 \
--to=pragma@wxs.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).