- ntg-context - Mailing Lists

Re: [NTG-context] tooltips and glossary
by Michael Saunders 06 May '10

06 May '10

Philipp: Thank you---I appreciate your effort on glossarium.lua very much, but I don't want to be dependent on you every time I want to tweek my glossary. I find it difficult to change the appearance and behavior of anything in Context, but I think my chances are better with it than with trying to work in lua. So, I have pursued the problem via the \definesynonyms approach. What I have so far can do all the basic things I imagined, and only seems to need some cosmetic work now. This is what I have: In the preamble: \definesynonyms[gentry][gentries][\infull][\inshort] %to connect headwords to entries \definesynonyms[gloss][glosses][\tttext][\ttkey] %to make short glosses available for tooltips \def\gldef#1#2#3{\gloss{#1}{#2}\gentry{#1}{#3 {(p.\at[g:#1])}}} \def\hint#1{\tooltip[middle]{#1}{\tttext{#1}}} \def\glref#1{\reference[g:#1]{}} %to place at a substantive reference in the text %then you have a file of definitions like this one: \gldef{vibrato}{a periodic fluctuation in pitch}{A periodic fluctuation of pitch, typically in the range 6--12~Hz.} Then, in the text, when you use an unfamiliar word and the reader could benefit from a quick, pop-up gloss: \hint{vibrato} (I just need a more sophisticated version of this that can deal with variants of the word). And, when you are about to engage in a substantive discussion of a word or phrase that appears in the glossary (for a given headword, there might be zero, one, or several such points in the text): \glref{vibrato} (This causes a page reference after the glossary entry.) I have two questions remaining: 1. I was somehow able to guess that \definesynonyms[gentry][gentries] creates a new command called "\setupgentries[]", and I imagine this command must inherit its possible keys and values from another command, but I don't know what. Where can I look it up? 2. How can I modify the appearance/location/behavior of tooltips? I tried \setuptooltips, but apparently that's not it. I'll tinker with this and test it for a while. Eventually I hope to contribute a glossaries "my way" to the garden. Hans: No problem! I'm sure whatever I put in the Google translator was just as articulate as what came out of it. Really, I think the mistake is mine. All along I have been assuming that Context was like LaTeX: a system for end-users, a language where an author could easily manipulate the appearance of his document. Apparently, it's more like a supporting infrastructure for that. Maybe it needs a layer of macros sitting on top of it to make it accessible and friendly to users/writers. I'm hoping Idris's book will shed light on this. Thanks, everyone.

2 1

strange page break
by Peter Münster 06 May '10

06 May '10

Hello, Here is a strange page break (version 2010.04.29 22:30): \def\mySection{\section{bla}\dorecurse{30}{text }} \starttext \dorecurse8{ \mySection\par bla} \stoptext Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/

6 21

Re: [NTG-context] tooltips and glossary
by Michael Saunders 06 May '10

06 May '10

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.} %within the text, where you need a tooltip on a word, you can say: ... \hint{vibrato} ... %at then end of the text, something like: Glossary: \placelistofgentries I see three problems with this: 1. I don't know how to tell \hint to refer to the "vibrato" in glosses and not in gentries. 2. There is no mechanism to refer to the page with a substantive discussion of "vibrato". 3. There is no way to handle cases where the string in the text is some variation of "vibrato" (e.g., Vibrato, vibrati, vibrato's) II. Marius's modified index solution is the only one to successfully link the entry back to a point in the text, but the resulting "glossary" really just looks like an index. III. Philipp Gesang's lua-based solution connects headwords to entries just as \definesynonyms[gentry][gentries][\infull][\inshort] does, and it produces something that looks like a glossary, but the entries have no link back to the text. Also, I don't see the point of the \usegloss{word} command unless it references the substantive discussion(s) of the word. I think that is what his "\usegloss[exp]{word}" is for, but then there should be a reference to it in the entry. Something like: {\bd headword}---entry text, p.\at[g:headword] There probably is some advantage in using the lua script for this, but I don't know what it is. About tooltips: \tooltip surprised me, and I was impressed that it appears to typeset the tooltip text with Context, but there are some problems with it: 1. It's stretched horizontally. 2. The active area begins at the baseline and stretches about 1 ex _under_ the word. 3. It appears without a border and under the cursor. I have seen tooltips in pdf files before, and they looked better than this. I suspect the reason is that, as you say, \tooltip uses Javascript, and the ones I saw use a different mechanism. I dug around and found this reference which describes how it's done with form fields and invisible buttons: http://gilbertconsulting.com/pdf/Build_tool_tips_in_InDesign.pdf (Notice how tidy the tooltips in it look.) That document describes setting them up manually in a point-and-click interface, but surely Context could automate this by putting an invisible frame around the word and creating a form field/button over it? And, correct me if I'm wrong, but that mechanism is not Javascript-based at all, is it? (by the way: I've not broken the thread again, have I?)

4 4

TeX comments in Lua strings - message: Undefined control sequence
by Jaroslav Hajtmar 06 May '10

06 May '10

Hello, Is there any possibility use TeX comments (text behind character %) in Lua strings? When I use comment char % inside luastring, then rest of string (i.e. next TeX definitions) are for TeX invisible. For example: When I make string : TeXDefsByLua=[[ \def\printline{ \directlua{printline()} \par\hrule\par } \def\printall{ \directlua{printall()} \par\hrule\par } ]] tex.sprint(TeXDefsByLua) then is all right, BUT when I make string : TeXDefsByLua=[[ \def\printline{ % my comment inside string \directlua{printline()} \par\hrule\par } \def\printall{ \directlua{printall()} \par\hrule\par } ]] tex.sprint(TeXDefsByLua) then I get message: "Undefined control sequence" Is there possibility use TeX comments inside Lua strings? Thanx Jaroslav

1 0

Re: [NTG-context] tooltips and glossary
by Michael Saunders 06 May '10

06 May '10

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".

6 5

Re: [NTG-context] Captials in section head
by richard.stephens＠converteam.com 06 May '10

06 May '10

> Am 04.06.2009 um 14:56 schrieb richard.stephens(a)converteam.com: > > > > > I need all section heads to be in full-size capitals, so I tried: > > > > \setuphead[section][textcommand=\uppercase] > > > > \starttext > > \section{New section} > > \input knuth > > \stoptext > > > > But I still get lowercase. > > Using 'textcommand=\cap' gives me small capitals, but I want full-size > > capitals. > > Is there a way to get what I want? > > In MkIV you can say \setuphead[section][style=WORD] or > \setuphead[section][style=\WORD] > > Wolfgang That's fantastic, thanks Wolfgang. Richard Converteam UK Ltd. Registration Number: 5571739 and Converteam Ltd. Registration Number: 2416188 Registered in England and Wales. Registered office: Boughton Road, Rugby, Warwickshire, CV21 1BU. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium. Please consider the environment before printing this e-mail

4 3

Columnset with defined height
by Honza Pohanka 05 May '10

05 May '10

Hello, is it possible to somehow define certain height of a columnset? I have tried to put it into the frame, but it does not work. I'm trying to create a conference poster and I think it could be useful for it. greetings Jan -- Tato zpráva byla vytvořena převratným poštovním klientem Opery: http://www.opera.com/mail/

1 0

existence of file
by Hans van der Meer 05 May '10

05 May '10

Is there a ConTeXt macro that can tell me if a certain file exists? If not, may I ask what Lua-call could be made in mkiv? I looked into the wiki but was not able to find the answer, allthough it probably is buried somewhere in it. Thanks beforhand. Hans van der Meer

2 1

Re: [NTG-context] tooltips and glossary
by Michael Saunders 05 May '10

05 May '10

>> 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)?

4 4

Re: [NTG-context] tooltips and glossary
by Michael Saunders 04 May '10

04 May '10

> (Preliminary remark to M.S.: please, please, configure your MUA to > correctly reply to the current thread!) (What's wrong with my subject line? I'm merely hitting "reply" in gmail.) > No, it's plain English. Unfamiliar phrases are just one consequence of a > language becoming the world standard. Do you want to flame Italians or > French for not adhering to the norms of classical Latin? You don't. > There's no point at all in even mentioning somebody's stylistic > idiosyncrasies on the internets. Just face it: the world won't adopt > English as a global means of communication without interfering with its > norms. If you don't understand something why don't you contact the > author, his email adress is right there on the first page. I don't mind non-native speakers using bad grammar, strange usages, or odd constructions at all. Things like that are usually no problem for native speakers to understand, although the two sentences I quoted were not "plain English" at all---one was completely indecipherable. The biggest problem with the docs is far more basic---it's the most basic mistake a beginning writer can make. I'm sure documents like the ones I was shown on this thread make perfect sense to their authors---who already know what they mean---but they fail to communicate their message to anyone who doesn't already know it. The reader isn't being given enough information to decode the message and what he is given is in no particular order: it's whatever bits and pieces of the story the author thinks of in the order he happens to think of them. You can't tell the author this. It makes sense to him and he can't understand the criticism. He has to put himself in the place of the reader who doesn't already know the message. If he can't do that, he can't communicate. I'm sure that these documents would be just as bad in the native languages of the authors as they are in English. The fault is far deeper than bad translation. Increasingly, I'm wondering whether the problem with Context is just bad docs or bad language design (it's hard to control, it looks bad most of the time). I still don't know. I'm hoping that Idris's book will shed light on this. > I append a snippet that should allow basic glossaries. It doesn't > provide much functionality (capitalization might have to be implemented > …) but you may fit it to your needs. ... > > (As for the code, it's certainly not context style, I'm aware of that > but don't have the time to care.) > > Awaiting your feedback, Thank you. I'm not quite sure what to do with these files (the .lua file in particular). Unfortunately, I won't be able to get to them until tomorrow. > As for the tooltips, unfortunately > I don't know how to create them. The functionality would be nice, > though, as long as no javascript is involved. It's not done with javascript. As I understand it, the usual way is to place an invisible pdf "forms"-style button over the word you want to gloss and then set its "short description" feature. I think context knows how to make such buttons and to set bounding boxes around words, so I think it should be possible, no?

3 2