From: Willi Egger <w.egger@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: tooltips and glossary
Date: Tue, 4 May 2010 15:07:03 +0200 [thread overview]
Message-ID: <0889DD34-27D2-4BC5-A2C6-5E2BD2584F5B@boede.nl> (raw)
In-Reply-To: <j2t54d7f5601005040244hc5b50aaof743d2ebffedc094@mail.gmail.com>
Hi,
Why do you complain about other user's English? - Let us be happy, that people of another mother tong including my self do participate on the list and share their experience with others!
According to what I tested the basic functionality is already available in Context:
\definesynonyms[Gloss][Glosses][\infull][\inshort]
\Gloss{cooltip}{HEI! This is a longer text in a tooltip}
\def\Hint#1{\tooltip[middle]{#1}{\infull{#1}}}
\starttext
This is a text. This sentence contains a \tooltip[middle]{cooltip}{HEI! This is a longer text in a tooltip}
\blank
This is a text. This sentence contains a \inshort{cooltip}: say: \infull{cooltip}
\blank
This is a text. This sentence contains a \Hint{cooltip}.
\blank[2cm]
\placelistofGlosses
\stoptext
Willi
On 4 May 2010, at 11:44, Michael Saunders wrote:
> Marius:
>
>> Try this one: http://www.tex.ac.uk/tex-archive/info/context-top-ten/cmds.pdf
>> -> page 14
>
> Thanks, but that looks like it's just some extracts from cont-eni
> translated from Engijsh into Engrish along with a distracting
> background that makes it hard to read. The stuff about the not very
> useful abbreviation command is there again, but I'm drawn to the
> section about building a dictionary that says it's not about building
> a dictionary. It says:
>
> "All you have to do is inserting a \index at whatever the phrase you
> want to index is, and placeing a \placeindex where you want the
> glossary to be."
>
> and then goes on to describe and index, not a glossary, which seems to
> require commands that need a lot of redundant arguments. It also
> contains this gem:
>
> "Like many other ConTeXt command, users can define their own series of
> indexing, which pluses the default \index series are called register."
>
> That's the most remarkable thing I've read today. Maybe I need to be
> more clear. A glossary is like a little dictionary in the back of a
> book that defines the specialized words and phrases that the book uses
> that might not be known to the general reader. Here is a definition
> of "glossary":
>
> A collection of glosses; a list with explanations of abstruse,
> antiquated, dialectal, or technical terms; a partial dictionary.
>
> ("Glosses" were little explanatory notes written in the margins of
> medieval texts---the kind of thing I would do if Context's marginal
> notes weren't incompatible with its columns.)
>
> Ideally, I'd like a system where I could keep the entries in a bib
> database or in a special .tex file. The records would include the
> headword and the gloss, and maybe a cross reference to the point in
> the text that dealt with the headword definitively---the point where
> the term was explained. (A document that defines and explains the new
> words and phrases it coins---imagine such a thing!) It would be nice
> if there were a command that would automatically link this point in
> the text with the glossary entry. LaTeX has several packages
> (glosstex, gloss, glossary, glossaries) that do things like this.
>
> To do this in Context, I will probably have to do it all manually,
> defining a command to set an entry and then doing all the
> alphabetization and cross-referencing by hand.
>
> 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".
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:07 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 [this message]
2010-05-04 13:34 ` Marius
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=0889DD34-27D2-4BC5-A2C6-5E2BD2584F5B@boede.nl \
--to=w.egger@boede.nl \
--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).