From: Marius <mariausol@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: tooltips and glossary
Date: Tue, 4 May 2010 16:34:59 +0300 [thread overview]
Message-ID: <p2zc86049a21005040634wcf63427an6e73a53a36b4bac7@mail.gmail.com> (raw)
In-Reply-To: <j2t54d7f5601005040244hc5b50aaof743d2ebffedc094@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Tue, May 4, 2010 at 12:44 PM, Michael Saunders <odradek5@gmail.com> wrote:
> What I would really, really, like is to add short definitions to each
> glossary record that could pop up as tooltips when the reader hovers
> over an unfamiliar word. Since there is no mechanism for glossaries
> in Context, there is no mechanism to build this into, but I'm still
> interested in doing it. The idea is, I could write something like:
>
> \gloss{strange word}{short definition}
>
> The text would read "strange word". When you hover over it with the
> cursor, a tooltip would appear saying "short definition". It would be
> great if this were linked to a glossary mechanism so I wouldn't have
> to keep writing the short definition---I could say something like:
>
> \gloss{strange word}
>
> and its short definition would be looked up automatically for the
> tooltip. The automatic reference to the word might look like this, in
> the text:
>
> \gref{strange word}
>
> which would cause the page number at that point to be printed at the
> end of the glossary entry for "strange word".
I don't know how to make tooltips, but everything else is in the file attached.
[-- Attachment #2: test2.pdf --]
[-- Type: application/pdf, Size: 14169 bytes --]
[-- Attachment #3: test2.tex --]
[-- Type: application/x-tex, Size: 681 bytes --]
[-- Attachment #4: Type: text/plain, Size: 486 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-05-04 13:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2010-05-06 9:45 ` Hans Hagen
2010-05-06 10:00 ` 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-03 19:18 Michael Saunders
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
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=p2zc86049a21005040634wcf63427an6e73a53a36b4bac7@mail.gmail.com \
--to=mariausol@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).