From: Rik <rik@panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Custom tags, revisited
Date: Tue, 26 Jun 2018 14:26:34 -0400 [thread overview]
Message-ID: <db091a00-4d2f-ebbd-e142-b81fe1502cae@panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 952 bytes --]
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?
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 1374 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2018-06-26 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 18:26 Rik [this message]
2018-06-26 22:59 ` 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=db091a00-4d2f-ebbd-e142-b81fe1502cae@panix.com \
--to=rik@panix.com \
--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).