From: Rik <rik@panix.com>
To: ntg-context@ntg.nl
Subject: Re: Overriding / redefining / disabling standard commands
Date: Mon, 25 Jun 2018 19:11:30 -0400 [thread overview]
Message-ID: <5a2d9820-7526-d2b7-ead2-cc11971ad46b@panix.com> (raw)
In-Reply-To: <5B31643B.5000601@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1007 bytes --]
On 6/25/2018 17:52, Wolfgang Schuster wrote:
> \startmode[ebook]
> \setupbackend[export=yes]
> \stopmode
>
> \starttext
>
> \index{Knuth}\input knuth
>
> \index{Ward}\input ward
>
> \index{Zapf}\input zapf
>
> \startnotmode[*export]
> \completeregister[index]
> \stopnotmode
>
> \stoptext
Unfortunately, this does not suppress generation of index references in
the exported output. Here is a snippet of the -div.html file generated
by the example you provided:
<div class="registerlocation index" href="#aut-1"
onclick="location.href='#aut-1'"><!--empty--></div>Thus, I
came to the conclusion that the designer of a new system must not
only be the implementer and first large--scale user; the designer
should also write the first user manual.
and a snip of the output with the default css:
Thus the request for a (simple) mechanism to redefine or disable
standard commands. There are commands other than \index that might also
benefit from similar treatment.
--
Rik
[-- Attachment #1.2.1: Type: text/html, Size: 1688 bytes --]
[-- Attachment #1.2.2: pninnflokfdmchpk.png --]
[-- Type: image/png, Size: 3996 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 prev parent reply other threads:[~2018-06-25 23:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 20:49 Rik Kabel
2018-06-25 21:52 ` Wolfgang Schuster
2018-06-25 23:11 ` Rik [this message]
2018-06-26 0:11 ` Alan Braslau
2018-06-26 0:50 ` Rik Kabel
2018-06-26 2:00 ` Alan Braslau
2018-06-26 2:44 ` Rik Kabel
2018-06-26 7:35 ` Hans Hagen
2018-06-26 12:56 ` Alan Braslau
2018-06-26 13:22 ` Hans Hagen
2018-06-26 6:34 ` Wolfgang Schuster
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=5a2d9820-7526-d2b7-ead2-cc11971ad46b@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).