From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: tooltips and glossary
Date: Thu, 6 May 2010 12:31:26 +0200 [thread overview]
Message-ID: <j2lfe8d59da1005060331pe80c4bc3k2e33686858be751f@mail.gmail.com> (raw)
In-Reply-To: <k2x54d7f5601005042136lcc7dc74duaed717af54a51ca3@mail.gmail.com>
On Wed, May 5, 2010 at 6:36 AM, Michael Saunders <odradek5@gmail.com> wrote:
> About glossaries:
>
> Thank you, everyone. I'm not much of a TeXpert and certainly not a
> lua expert, but I'm trying to understand your different solutions and
> integrate them into a working system. There seem to be three
> approaches:
>
> I. Willi Egger---synonym-based
> II. Marius---modified index
> III. Philipp Gesang---lua-based
>
> I. So far, Willi's synonym-based solution looks simple and promising.
> I imagine something like this:
>
> \definesynonyms[gloss][glosses][\infull][\inshort]%to make short
> glosses available for tooltips
> \definesynonyms[gentry][gentries][\infull][\inshort]%to connect
> headwords to entries
> \def\gdef#1#2#3{\gloss{#1}{#2}\gentry{#1}{#3}}
> \def\hint#1{\tooltip[middle]{#1}{\infull{#1}}}
>
>
> %then you have a file of definitions like this one:
>
> \gdef{vibrato}{a periodic fluctuation in pitch}{A periodic fluctuation
> of pitch, typically in the range 6--12~Hz.}
Synonyms are defined in
strc-syn.mkii (or strc-syn.mkiv, if you are using mkiv) ;
maybe it can help you in defining your own macros (just to avoid to
reinvent the wheel, possibly)
--
luigi
___________________________________________________________________________________
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-06 10:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- 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-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-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=j2lfe8d59da1005060331pe80c4bc3k2e33686858be751f@mail.gmail.com \
--to=luigi.scarso@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).