From: MF <massifr@fastwebnet.it>
To: ntg-context@ntg.nl
Subject: Re: issue with css selector in lpath
Date: Wed, 13 Dec 2017 10:22:23 +0100 [thread overview]
Message-ID: <1513156943.2387.10.camel@fastwebnet.it> (raw)
In-Reply-To: <03e83523-0a5f-9b37-68b1-aa2fc8fc7310@gmx.es>
Il giorno mar, 12/12/2017 alle 22.36 +0100, Pablo Rodriguez ha scritto:
> On 12/11/2017 11:51 PM, mf wrote:
> > I think it's the "#header" without the name of an element before.
> > Try specifying an element you find in your document (i.e.
> > "{{header,
> > tag#header}}"), just to see if it compiles.
> >
> > If it compiles, it's likely you found a bug.
>
> No, it doesn’t compile.
>
> But {header, #header} shouldn’t be a problem, accorrding to
> http://pragma-ade.com/general/manuals/xml-mkiv.pdf#page=34.
>
> If this isn’t a bug, I wonder what I’m doing wrong.
>
Could you send a minimal (not) working example?
> > > I have the following code:
> > >
> > > \xmlsetsetup{\xmldocument}
> > > {{header, #header}}
> > > {xml:titlepage}
> > >
> > >
The error you get says that #header is read as a macro parameter, but
the "#" is not followed by a number, so the error.
Why "#header" is interpreted as a parameter? It smells like the "#" is
being parsed in a context with the wrong catcodes.
I would investigate the first (\xmldocument) and the third argument
(your xml:titlepage setup).
For the first one, I've always used the form:
\xmlsetsetup{#1}{{header, #header}}{xml:titlepage}
I'm reading from xml-mkiv.pdf, at page 19, that "The macro \xmldocument
expands to the current document id. There is also \xmlself which
expands to the current node number (#1 in setups)."
Could you modify your setup to use that form ("#1" i mean) and see if
it works?
Best wishes,
Massi
___________________________________________________________________________________
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:[~2017-12-13 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 20:51 Pablo Rodriguez
2017-12-11 22:51 ` mf
2017-12-12 21:36 ` Pablo Rodriguez
2017-12-13 9:22 ` MF [this message]
2017-12-14 19:46 ` Pablo Rodriguez
2017-12-14 20:39 ` Hans Hagen
2017-12-14 21:18 ` Pablo Rodriguez
2017-12-15 6:55 ` Hans Hagen
2017-12-18 22:33 ` Pablo Rodriguez
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=1513156943.2387.10.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).