ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: tooltips and glossary
Date: Mon, 3 May 2010 14:18:26 -0500	[thread overview]
Message-ID: <y2y54d7f5601005031218q8182bef1ob797edaf453ed4ed@mail.gmail.com> (raw)

>> Also, is there no Context method to produce a glossary?  It might be
>> enough to produce a secondary .bib file with special entries and to
>> print this out as a secondary "References" section, but I don't know
>> how to do this or how to control the appearance of the printed
>> "references".

Wolfgang Schuster:

> http://wiki.contextgarden.net/Reference/en/definesynonyms

If you read that page, you'll notice it doesn't say what the second
and third arguments of \definesynonyms do, what the command
\definesynonyms itself does, nor does it hint at what \infull is
doing.  There is certainly nothing there about using an external
database.  I don't see any way to use \definesynonyms for a glossary
or any practical purpose for \definesynonyms at all, and the
abbreviations example is obviously more trouble than it's worth.

More to the point, there is nothing about tooltips.  Is there a way
for Context to produce tooltips in text (with invisible buttons,
perhaps)?
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2010-05-03 19:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 19:18 Michael Saunders [this message]
2010-05-03 19:21 ` Wolfgang Schuster
2010-05-04  1:40 ` Michael Saunders
2010-05-04  8:18   ` Marius
2010-05-05  6:28   ` Taco Hoekwater
  -- strict thread matches above, loose matches on Subject: below --
2010-05-06 11:20 Michael Saunders
2010-05-06 11:49 ` luigi scarso
2010-05-05  4:36 Michael Saunders
2010-05-05  7:02 ` Philipp Gesang
2010-05-05  7:04   ` Philipp Gesang
2010-05-05  7:04 ` Marius
2010-05-06 10:31 ` luigi scarso
2010-05-04  9:44 Michael Saunders
2010-05-04 12:28 ` Philipp Gesang
     [not found]   ` <o2i54d7f5601005040628p90c28ea6s47eab9d212acce20@mail.gmail.com>
2010-05-04 13:32     ` Michael Saunders
2010-05-04 19:04       ` Philipp Gesang
2010-05-04 19:42       ` Corsair
2010-05-04 13:07 ` Willi Egger
2010-05-04 13:34 ` Marius
2010-05-06  9:45 ` Hans Hagen
2010-05-06 10:00   ` Taco Hoekwater
2010-05-02 22:51 Michael Saunders
2010-05-03 12:26 ` Wolfgang Schuster
2010-05-03 19:09 ` 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=y2y54d7f5601005031218q8182bef1ob797edaf453ed4ed@mail.gmail.com \
    --to=odradek5@gmail.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).