ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: issue with css selector in lpath
Date: Thu, 14 Dec 2017 20:46:08 +0100	[thread overview]
Message-ID: <9f2773df-1ce1-b2ef-7023-65f0876db61e@gmx.es> (raw)
In-Reply-To: <1513156943.2387.10.camel@fastwebnet.it>

On 12/13/2017 10:22 AM, MF wrote:
> Il giorno mar, 12/12/2017 alle 22.36 +0100, Pablo Rodriguez ha scritto:
>> [...]
>> 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?

Here you have it:

    \startbuffer[demo]
    <doc>
        <header>
            <p>Document Title</p>
            <p>Text from paragraph.</p>
        </header>
        <div id="header">
            <p>Document Title</p>
            <p>Text from paragraph.</p>
        </div>
        <div class="header">
            <p>Document Title</p>
            <p>Text from paragraph.</p>
        </div>
    </doc>
    \stopbuffer

    \startxmlsetups xml:initialize
         \xmlsetsetup{#1}{doc|p}{xml:*}
         \xmlsetsetup{#1}{{header}}{xml:header}
         \xmlsetsetup{#1}{{.header}}{xml:header:class}
         %~ \xmlsetsetup{#1}{{#header}}{xml:header:id}
         \xmlsetsetup{#1}{{id="header"}}{xml:header:id}
    \stopxmlsetups

    \xmlregistersetup{xml:initialize}

    \startxmlsetups xml:doc
       \xmlflush{#1}
    \stopxmlsetups

    \startxmlsetups xml:header
       \startalign[left]\xmlflush{#1}\stopalign
    \stopxmlsetups

    \startxmlsetups xml:header:class
       \start\em\xmlflush{#1}\stop
    \stopxmlsetups

    \startxmlsetups xml:header:id
       \startalign[right]\xmlflush{#1}\stopalign
    \stopxmlsetups

    \startxmlsetups xml:p
       \xmlflush{#1}
    \stopxmlsetups

    \starttext
        \xmlprocessbuffer{main}{demo}{}
    \stoptext

.header works fine, it is only #header that breaks compiliation.

I hope Hans can fix it (or explain what I’m doing wrong).

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2017-12-14 19:46 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
2017-12-14 19:46       ` Pablo Rodriguez [this message]
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=9f2773df-1ce1-b2ef-7023-65f0876db61e@gmx.es \
    --to=oinos@gmx.es \
    --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).