From: MF <massifr@fastwebnet.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: CSS selector for elements strictly preceded by other elements
Date: Fri, 03 Aug 2018 16:31:27 +0200 [thread overview]
Message-ID: <ad2cce0795cf4172e94f99e7578754632e5bbda2.camel@fastwebnet.it> (raw)
In-Reply-To: <bcbfdc8d-2aa3-4af7-9bbf-863283a542dd@xs4all.nl>
> make a (real) minimal example and we'll see what can be done
>
Here it is:
\startbuffer[test]
<body>
<p>In this paragraph<footnote>first footnote</footnote><endnote>endnote strictly
following a footnote (no other XML nodes between them)</endnote>
a footnote marker and an endnote marker are at the same point in the text;
in the XML source, their elements are contiguous, with nothing in between.
The CSS selector <code>footnote + endnote</code> works right, and the setup
associated to that selector puts a comma between their markers to
separate them in the typesetting.</p>
<p>In this paragraph<footnote>second footnote</footnote> they don't occur at the
same point in the text<endnote>endnote comes after footnote: there's some
text between them, but no XML elements</endnote>;
for the CSS selector <code>footnote + endnote</code> it's the same case of the previous paragraph,
because there's no other XML element between the <code>footnote</code> and the
<code>endnote</code> elements: that's why you still see a comma before
the endnote's marker, but this time it's not what I want.</p>
<p>In this paragraph<footnote>third footnote</footnote> they don't occur at the
same point in the text, and the CSS selector <code>footnote + endnote</code>
does not match<endnote>endnote comes after footnote, but there are 3 nodes
between them: a text, a <code>code</code> element, another text</endnote>,
because there's a <code>code</code> element between <code>footnote</code>
and <code>endnote</code> elements.</p>
<p>CSS has no operator to discriminate between the first two cases.</p>
</body>
\stopbuffer
\setupnotation[footnote][numberconversion=a]
\setupwhitespace[line]
\startxmlsetups xml:notesetups
\xmlsetsetup{#1}{body|p|footnote|code}{xml:*}
\xmlsetsetup{#1}{{endnote}}{xml:endnote}
\xmlsetsetup{#1}{{footnote + endnote}}{xml:endnote-after-footnote}
\stopxmlsetups
\xmlregistersetup{xml:notesetups}
\startxmlsetups xml:body
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:p
\xmlflush{#1}\par
\stopxmlsetups
\startxmlsetups xml:footnote
\footnote{\xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:code
{\tt\xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:endnote
\endnote{\xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:endnote-after-footnote
\high{,}\endnote{\xmlflush{#1}}
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{test}{}
\page
\placenotes[endnote]
\stoptext
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-08-03 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 8:20 MF
2018-08-02 17:52 ` Hans Hagen
2018-08-03 14:31 ` MF [this message]
2018-08-04 10:10 ` 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=ad2cce0795cf4172e94f99e7578754632e5bbda2.camel@fastwebnet.it \
--to=massifr@fastwebnet.it \
--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).