From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>, Rik <rik@panix.com>
Subject: Re: Custom tags, revisited
Date: Wed, 27 Jun 2018 00:59:44 +0200 [thread overview]
Message-ID: <5c6b7897-52c1-5a51-94d5-1da4fa44f431@xs4all.nl> (raw)
In-Reply-To: <db091a00-4d2f-ebbd-e142-b81fe1502cae@panix.com>
On 6/26/2018 8:26 PM, Rik wrote:
> In September 2015 thread "Custom XML Export," Hans instructed us on how
> to create custom tags. The example he presented is:
>
> \setupbackend[export=yes]
>
> \definehighlight[this]
>
> \starttext
> \startelement[what]
> \this{that} \input ward
> \stopelement
> \stoptext
>
> When that example is run with the current (2018-06-25) beta or TL18,
> there is no html body:
>
> </head>
> <body>
> <div class="document" xmlns="http://www.pragma-ade.com/context/export">
>
> <div class="warning">Rendering can be suboptimal because there is no default/fallback css loaded.</div>
>
> <div>
> <div class="metadata">
> </div>
> </div>
>
> </div>
> </body>
> </html>
>
> Further experimentation suggests that \startelement is gobbling the
> output. (Adding \setupstructure does not change the result.)
>
> What is the proper way to add custom tags?
\setelementbackendtag[what]
\setelementnature[what][inline]
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2018-06-26 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 18:26 Rik
2018-06-26 22:59 ` Hans Hagen [this message]
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=5c6b7897-52c1-5a51-94d5-1da4fa44f431@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=rik@panix.com \
/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).