May 2010 - ntg-context - NTG Mailing Lists

PPCHTEX with PSTricks option
by Helge Kruse 07 May '10

07 May '10

The minimal example shows diagonal lines. Since the line output of pictex is limited, I would choose PSTricks as output driver for better quality. When I enable the pstricks option, these diagonal lines collide with the radical atoms. You can easily reproduce this by removing the % comment symbol. How can we improve the postscript output. Any hints are appreciated. Best regards, Helge Kruse \documentclass{minimal} \usepackage%[pstricks] {m-ch-en} \begin{document} \setupchemical[scale=small,width=fit,frame=off] \setupchemical[top=1200,bottom=1200] \[ \startchemical[right=2500] \chemical[ONE,SB258,Z05][CH,CH_3] \chemical[PB:Z2,Z0,SB1,Z1,PE][ O,C_2H_5] \chemical[PB:Z8,Z0,SB1,Z1,PE][ O,C_2H_5] \stopchemical \] \end{document} PS: I wrote this to ntg-ppchtes(a)ntg.nl as sussgested at http://www.pragma-ade.com/link-1.htm, but that list appears as dead.

1 0

\installlanguage questions
by Tomáš Pustelník 06 May '10

06 May '10

Hello, I have few questions about command \installlanguage. First, in file lang-ini is command \setuplanguage for default language. It has parameters lefthyphen, righthyphen and hyphen. I would like to ask if these parameters can be used in command \installlanguage or not and what is their funcionality becouse I have tried use command: \setuplanguage[cz][lefthyphen=@,righthyphen=@,hyphen=€] and I didn't see any changes. I thought it's used to setup hyphen mark when the word is spilt at the end of line but I still get symbol - Also I would like to know whats the difference in \date and parameter date in \installlanguage? In parameter date in \installlanguage are curly backets, it's just some mask for command \date? Or those two are entirely different? Thank you answers. Tomas Pustelnik

3 2

Article titles not capitalized in bibliography
by Tom 06 May '10

06 May '10

Book titles retain proper capitalization from the .bib file but articles from periodicals do not. Only the first word of an article title is capitalized in the .bbl file. Even proper names in titles lose their capitalization. Is there an option that needs to be set to cause article titles to retain proper capitalization? MKII Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey

3 2

new issue with page break
by Peter Münster 06 May '10

06 May '10

Hello, IMHO there should never be a page break right *after* a section header, but here it is: \starttext \dorecurse{660}{text } \section{bla} % \par\page[no] % does not help \startTEX bla bla \stopTEX \stoptext My actual work-around: \page before \section{} Is there a better solution? TIA for any help! Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/

2 1

4th ConTeXt Meeting, registration & call for submissions
by Taco Hoekwater 06 May '10

06 May '10

Early-bird registration (till May 31, 2010) for the 4th ConTeXt Meeting is now open. The 4th ConTeXt Meeting will take place in Brejlov, Czech Republic on September 13-18, 2010. For more information visit: http://meeting.contextgarden.net/2010/ *Call for submissions* As in previous years, anything at all related to ConTeXt and LuaTeX that you would like to share is an acceptable subject for a presentation, tutorial, discussion, Q&A session, demonstration, workshop, recital, sketch, or sermon. The informal theme is: ConTeXt typesetting documentation, teach as we preach It follows that if you have something to say on educating users on how to best use ConTeXt or to developers on how to best document ConTeXt (and who doesn't have an opinion on those topics!) your submission will be all the more appreciated. The program committee is Hans Hagen and Taco Hoekwater, feel free to email them with hints and ideas. Because we want something interesting on the website, abstracts should be sent in before May 31, 2010. Hans, Jano, Pavel & Taco The organizing committee

1 0

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