ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: XML expression to read HTML classes
Date: Thu, 27 Aug 2015 22:57:04 +0200	[thread overview]
Message-ID: <55DF79A0.1040607@wxs.nl> (raw)
In-Reply-To: <2314073.gCWnhbtjGW@max>

On 8/25/2015 5:05 PM, massifr@fastwebnet.it wrote:
> Hello list,
> I'm working on HTML typesetting with ConTeXt.
> I wrote a custom expression to test whether an element has a class:
>
> function xml.functions.classes(classAttr)
>    local classes = {}
>    if classAttr then
>      for c in string.gmatch(classAttr, "%S+") do
>        if (string.len(c) > 0) then classes[c] = true end
>      end
>    end
>    return classes
> end
>
> function xml.expressions.hasClass(classAttr, className)
>    if classAttr and className then
>      return xml.functions.classes(classAttr)[className] ~= nil
>    end
>    return false
> end
>
> This way I can write this in my xmlsetup:
> \xmlsetsetup{#1}{p[hasClass(@class,'myclass1')]}{html:p:myclass1}
>
> That is better than
> - p[@class='myclass1']   (it fails when you have more classes)
> - p[contains(@class, 'myclass1')]    (it gives you false positives when you have class="myclass12")
>
> That works, but I would like to write:
> \xmlsetsetup{#1}{p[hasClass('myclass1')]}{html:p:myclass1}
>
> omitting the @class argument, because it's obvious.
> To omit it I need to access the current collected element.
>
> At page 25 of "Dealing with XML in ConTeXt MkIV" it is said
> that the predefined variables "list","l","ll" (I think I need that one)
> and "order" are available, but I did not manage to access them.
>
> How can I get the current element in Lua to write
> local classAttr = xml.attribute(currentElement, "", "class")   ?

function xml.functions.classes(e)
     local class = e.at.class
     if class then
         local classes = { }
         for c in string.gmatch(class,"%S+") do
             classes[c] = true
         end
         return classes
     else
         return { }
     end
end



-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2015-08-27 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 15:05 massifr
2015-08-26 13:16 ` massifr
2015-08-27 20:57 ` Hans Hagen [this message]
2015-08-27 21:16   ` 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=55DF79A0.1040607@wxs.nl \
    --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).