[NTG-context] register confusion
Finding simple \at[] statements inadequate for glossaries (where there might be zero, one, or several page references per entry), I'm experimenting with registers, but I'm not getting the expected results: \defineregister[glind][glinds] \setupregister[glind][style=\it] \setupinteraction[state=start] \starttext double\glind[double]{} \page single\glind[single]{} \page double\glind[double]{} \page single should read, '2': (p.\placeglind[single]) double should read, '1, 3': (pp.\placeglind[double]) zero should be blank: (\placeglind[zero]) \stoptext Note the problems: 1. \placeglind[label] doesn't point to the label, it points to any label. 2. Context forces a linebreak before and after the numbers. 3. The numbers aren't italic. Also, it would be nice to set 'p.', 'pp.', or nothing automatically, depending on whether there was one, several or zero instances of the label in the text. Is register not the mechanism to do this? If not, I don't know what is. ___ 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 ___
Re: [NTG-context] simple bibliography and dots after section numbering
I think what are you looking for is possible with bib module. Look at the 3.1 section "Default and explicit citations" http://dl.contextgarden.net/modules/bibmod-doc-2009.11.04.zip http://wiki.contextgarden.net/Bibliography On Fri, May 7, 2010 at 1:52 AM, wrote: > rogu...@googlemail.com (2010-05-05 05:12): >> 2. I would like to use something like this for bibliography: >> http://wiki.contextgarden.net/Simple_Bibliography#Another_Approach >> but adapting it seems too hard for me. Perhaps someone could help? A >> very crude example: >> >> --- >> People are writing about this \cite[ref1], (\cite[ref2] - page 25). >> >> \startbibliography >> \bibitem[ref1] This is the first reference. >> \bibitem[Daniel, 2004][ref2] This is the second reference. >> \stopbibliography >> --- >> >> should be rendered as: >> >> --- >> People are writing about this [1], (Daniel, 2004 - page 25) >> >> 1. This is the first reference. >> 2. This is the second reference. >> --- >> >> That is, I want an environment and 2 commands: >> \startbibliography >> \cite [key] >> \bibitem [label_replacing_\cite[key]_but_not_the_item_number] [key] > > A bump to my initial question to add that I am using MKIV and a question: > would this be hard to implement for a total ConTeXt newcommer? What > should he use? TeX / Lua? Would ConTeXt commands be enough? > > -- > -- Rogutės Sparnuotos > ___ > 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 ___
[NTG-context] PPCHTEX with PSTricks option
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-ppch...@ntg.nl as sussgested at http://www.pragma-ade.com/link-1.htm, but that list appears as dead. ___ 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 ___
Re: [NTG-context] simple bibliography and dots after section numbering
rogu...@googlemail.com (2010-05-05 05:12): > 2. I would like to use something like this for bibliography: >http://wiki.contextgarden.net/Simple_Bibliography#Another_Approach >but adapting it seems too hard for me. Perhaps someone could help? A >very crude example: > >--- >People are writing about this \cite[ref1], (\cite[ref2] - page 25). > >\startbibliography > \bibitem[ref1] This is the first reference. > \bibitem[Daniel, 2004][ref2] This is the second reference. >\stopbibliography >--- > >should be rendered as: > >--- >People are writing about this [1], (Daniel, 2004 - page 25) > >1. This is the first reference. >2. This is the second reference. >--- > >That is, I want an environment and 2 commands: > \startbibliography > \cite [key] > \bibitem [label_replacing_\cite[key]_but_not_the_item_number] [key] A bump to my initial question to add that I am using MKIV and a question: would this be hard to implement for a total ConTeXt newcommer? What should he use? TeX / Lua? Would ConTeXt commands be enough? -- -- Rogutės Sparnuotos ___ 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 ___
Re: [NTG-context] simple bibliography and dots after section numbering
Otared Kavian gmail.com> writes: > On 5 mai 2010, at 09:25, Marius wrote: > > On Wed, May 5, 2010 at 5:12 AM, googlemail.com> wrote: > >> > >> 1. How does one add a dot after the numerals in headings, so that > >> "\section{First}" > >> becomes > >> "1. First" > >> instead of > >> "1 First" > >> ? > > > > \setupheads[sectionstopper=.] > > Actually this works only in mkiv, and implies also a dot after the > chapter numbers and so on. > If you want only a dot after the section number you may say > \setuphead[section][sectionstopper={.}] > > The same thing is possible in mkii, but I don't remember how to do it > right now… Thank you both very much. I have a humble question now: how did you find out about this setting? I thought about adding sectionstopper to the Reference in the wiki (sectionstarter should go with it, no?), but was not sure how to go about a MKIV-only parameter. Moreover, I was not successful in finding any documentation about it. There's no more to the new manual than the chapters on typography, fonts, is there? ___ 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 ___
Re: [NTG-context] [NTG Context] Storm (Lido) font support seems to be broken in newer versions of MKII
On 3-5-2010 10:09, Honza Pohanka wrote: Hello, the Storm font support by Vit Zyka is broken in actual version of MKII. I spoke with him, but unfortunately he uses old version and does not have the time for updates. I discovered that renaming the enco-*.tex files to enco-*.mkii solves a part of the problem, but there still remains an issue with math typesetting. Context does not know many characters (\times, \neq, ...), boldmath etc. Typescripts looks OK and I don't know enough to look deeper. Could anyone help? aren't there open type storm fonts? Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] \installlanguage questions
On 5-5-2010 3:48, Tomáš Pustelník wrote: 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 - lefthyphen and righthyphen are supported now - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] mistake in lang-cjk.mkiv
On 3-5-2010 8:43, Tomáš Pustelník wrote: Hi, I have found a glitch in lang-cjk.mkiv in definition of Japanese language name of days are shifted. It begins at line 136, sunday is actualy monday etc. In source code it looks like that: \setuplabeltext [\s!ja][\v!sunday=月曜日] \setuplabeltext [\s!ja][\v!monday=火曜日] \setuplabeltext [\s!ja][\v!tuesday=水曜日] \setuplabeltext [\s!ja][\v!wednesday=木曜日] \setuplabeltext [\s!ja][\v!thursday=金曜日] \setuplabeltext [\s!ja][\v!friday=土曜日] \setuplabeltext [\s!ja][\v!saturday=日曜日] but it should be: \setuplabeltext [\s!ja][\v!monday=月曜日] \setuplabeltext [\s!ja][\v!tuesday=火曜日] \setuplabeltext [\s!ja][\v!wednesday=水曜日] \setuplabeltext [\s!ja][\v!thursday=木曜日] \setuplabeltext [\s!ja][\v!friday=金曜日] \setuplabeltext [\s!ja][\v!saturday=土曜日] \setuplabeltext [\s!ja][\v!sunday=日曜日] patched Also I would like to ask if file lang-spe.mkii have some equivalent in MkIV and where the language specifics are defined (in which file)? Or is it treated in enco files? in mkiv we don't have (want) language specifics ... why do yoi need them? Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] problem with package.path
On 4-5-2010 10:28, Peter Münster wrote: Hello, I need to include lua-modules from different directories, but package.path does not seem to work: \startbuffer[test] bla = nil \stopbuffer \savebuffer[test][../mytest.lua] \starttext \startluacode package.path = "../?.lua;;" require("mytest") \stopluacode \stoptext dofile "../mytest.lua" - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] Article titles not capitalized in bibliography
On Thu, 6 May 2010, Taco Hoekwater wrote: You will have to do that in a local copy, as I am a hesitant to change this in the distribution (it would introduce compatibility problems in already existing documents). Moreover, certain styles demand that only the first word of the title be capitalized and proper nouns be capitalized. I usually add {...} in my bib file around words whose capitalization should not be changed. Aditya ___ 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 ___
Re: [NTG-context] new issue with page break
On 6-5-2010 2:39, Peter Münster wrote: 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? function buffers.verbatimbreak(n,m) if flags.optimize_verbatim then if n == 2 or n == m then texsprint(no_break_command) elseif n > 1 then texsprint(do_break_command) end end end in buff-ini.lua or otherwise \optimizeverbatimfalse - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
[NTG-context] new issue with page break
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/ ___ 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 ___
[NTG-context] 4th ConTeXt Meeting, registration & call for submissions
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 ___ 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 ___
Re: [NTG-context] tooltips and glossary
> 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. It's the opposite, but I think we all understand the difficulties that a Latex user has in changing his point of view (for me it's the same when I jump in LaTeX) We cannot do anything more than write same examples that encourage you in find your solution (that perhaps you want to share with us or in the wiki then). The hard part is to find a "context-way" (I personally tend to write more TeX-plain than context), so looking into the source is always the best choice. Anyway I want to say that most of us are sometimes in someway annoyed by your strong sentences and this doesn't help so much in finding a solution. -- 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 ___
Re: [NTG-context] strange page break
On 6-5-2010 1:17, Peter Münster wrote: On Thu, May 06 2010, Hans Hagen wrote: When you take my example from this morning, then you'll see, that \allowbreak really helps, whereas \testpage[5] only helps in some cases. yes but allowbreak introduces a penalty node that can interfere with spacing Anyway, I don't consider \allowbreak a solution, rather a work-around. Should I put this issue on the tracker? as long term issue ok, as it has to wait till we've opened up the par builder in luatex Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] tooltips and glossary
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. ___ 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 ___
Re: [NTG-context] strange page break
On Thu, May 06 2010, Hans Hagen wrote: >> When you take my example from this morning, then you'll see, that >> \allowbreak really helps, whereas \testpage[5] only helps in some cases. > > yes but allowbreak introduces a penalty node that can interfere with > spacing Anyway, I don't consider \allowbreak a solution, rather a work-around. Should I put this issue on the tracker? Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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 ___
Re: [NTG-context] strange page break
On 6-5-2010 12:09, Peter Münster wrote: On Thu, May 06 2010, Hans Hagen wrote: \setuphead[section][before={\allowbreak\blank[2*big]}] {\testpage[5]\blank[2*big]} Hello Hans, When you take my example from this morning, then you'll see, that \allowbreak really helps, whereas \testpage[5] only helps in some cases. yes but allowbreak introduces a penalty node that can interfere with spacing (as taco explained, it's all related to tex not being that clever in breaking pages and there is no 100% robust way to predict and calculate such situations) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] tooltips and glossary
On Wed, May 5, 2010 at 6:36 AM, Michael Saunders 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 ___
Re: [NTG-context] strange page break
Am 06.05.10 12:09, schrieb Peter Münster: On Thu, May 06 2010, Hans Hagen wrote: \setuphead[section][before={\allowbreak\blank[2*big]}] {\testpage[5]\blank[2*big]} Hello Hans, When you take my example from this morning, then you'll see, that \allowbreak really helps, whereas \testpage[5] only helps in some cases. MkIV has a 'preference' option for \blank but it does not work for me. \setuphead[section][before={\blank[preference,2*big]}] Wolfgang ___ 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 ___
Re: [NTG-context] strange page break
On Thu, May 06 2010, Hans Hagen wrote: >>> \setuphead[section][before={\allowbreak\blank[2*big]}] > > {\testpage[5]\blank[2*big]} Hello Hans, When you take my example from this morning, then you'll see, that \allowbreak really helps, whereas \testpage[5] only helps in some cases. Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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 ___
[NTG-context] TeX comments in Lua strings - message: Undefined control sequence
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 ___ 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 ___
Re: [NTG-context] tooltips and glossary
Just being helpful here: Hans Hagen wrote: Aangezien een antwoord in het engels voor jou meer vragen oproept dan antwoorden, reageer ik maar even in het Nederlands. Wellicht dat de google translator je een perfecte vertaling oplevert. Since an answer in English you calls more questions than answers, I react but just as in Dutch. Possibly that the google translator you produce a perfect translation. Omdat iedere gebruiker wel wat anders wil, is het onmogelijk om alles in te bouwen zonder dat het ontaard in een veelheid aan commandos. Het is dan ook vaak beter bestaande mechanismes te combineren. Veel mechanismes hebben een 'command hook' en het is niet zo lastig om bijvoorbeeld het synoniem mechanisme op die manier uit te breiden met een tooltip. Because every user, however, what differently wants, it is impossible everything build in without it degenerated in a multiplicity to commandos. It is thus frequently better existing combine mechanisms. Many mechanisms have ' command hook' and it is not this way cumbersome for example the synonymous extend mechanism this way with a tool tip. Er zijn inmiddels verschillende suggesties gedaan en ik ga daar niets aan toevoegen. Het is niet mijn probleem als een gebruiker gebrek heeft aan fantasie danwel suggesties niet gebruikt cq. zijn mails zodanig formuleert dat er niemand zin heeft om te reageren. Het verbaast me zowieso dat er gereageerd wordt, zeker als de toonzetting ronduit beledigend is, maar dat kan aan mijn gebrekkige engels liggen. Several suggestions have been meanwhile done and I will add to that nothing. It is not my problem if a user to fantasia or suggestions have not used lack cq. to be mails as such formulate that there nobody has to react sense. It astonishes me zowieso that there is reacted, the more so if the toonzetting is simply offending, but that can lie to my poor English. Overigens, in een perl of lua handleiding zie je ook geen kant en klare antwoorden. Men mag er zelf wel wat voor doen. Moreover, in perl or lua guide to see you side also no and klare answering. One can do there himself, however, what kind of. Lijkt me logisch, waarom zou ik een glossary beschrijven als het over een index gaat. Je bent de eerste die hier deze twee door elkaar haalt. Me seems logical, for which I would describe glossary if it concerns an index. You are the first which obtains here these two by each other. Overigens, in mkiv kun je user data laten meereizen en gebruiken maar dat leg ik nog wel eens uit (of misschien ook nooit, want ik waag me niet meer aan Engels). Moreover, in mkiv can to user let travel with you to data and use but that explanation I still once (or perhaps also never, because I venture myself no longer to English). Ach ja, gsub(manual,"index","glossary") zal je niet geven wat je zoekt vrees ik. Overigens, we hebben dat soort 'begrippenlijsten in vrijwel elk van onze projekten dus het kan echt wel. At last, gsub (manual, " index" , " glossary") you will not give what zoekt you apprehension I. Moreover, we have that type ' term lists in nearly each of our projects therefore are possible it really, however. Etc etc. Etc etc. Overigens, als ik zoveel commentaar had op een programma en de manuals, dan was ik al lang afgehaakt dus een doorzetter ben je wel. Moreover, if I had so much comment on a programme and the manuals, then I had been for a long time pulled out therefore a doorzetter am you, however. ___ 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 ___
Re: [NTG-context] strange page break
On 6-5-2010 11:33, Otared Kavian wrote: On 6 mai 2010, at 11:13, Wolfgang Schuster wrote: Am 06.05.10 10:46, schrieb Otared Kavian: Hi Peter, I had noticed such strange page breaks before and since it was always in small documents (maths problem sheets), I used an elementary workaround which consists in adding a \medskip or \smallskip before every \section. Actually analogous bad page breaks happen in Plain TeX with \beginsection. Regarding the minimal example you sent, adding \setuphead[section][before=\smallskip] to the top of your document, solves the problem appearing in the first section. I don't know whether this solves all other strange page breaks or not. You should at least keep the original space before the \section. \setuphead[section][before={\allowbreak\blank[2*big]}] {\testpage[5]\blank[2*big]} this will make sure that at least there are 5 line equivalents of text. (I want to integrate that in the spacing code.) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] \installlanguage questions
Tomáš Pustelník wrote: 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 think this is a case of NYI (not yet implemented). Luatex has support for these parameters, but it looks like mkiv only has the \setuplanguage keys at the moment, not an actual implementation. I thought it's used to setup hyphen mark when the word is spilt at the end of line Yes, that is wat it is supposed to do. Also I would like to know whats the difference in \date and parameter date in \installlanguage? In parameter date in \installlanguage are curly backets, That is just a syntax trick to solve a problem with embedded commas. In context, "key=value" and "key={value}" are equivalent, except that the second form allows embedded commas. it's just some mask for command \date? Or those two are entirely different? The \setuplanguage parameter provides a formatting template for \date. Best wishes, Taco ___ 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 ___
Re: [NTG-context] tooltips and glossary
On 4-5-2010 11:44, Michael Saunders wrote: 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: Aangezien een antwoord in het engels voor jou meer vragen oproept dan antwoorden, reageer ik maar even in het Nederlands. Wellicht dat de google translator je een perfecte vertaling oplevert. Omdat iedere gebruiker wel wat anders wil, is het onmogelijk om alles in te bouwen zonder dat het ontaard in een veelheid aan commandos. Het is dan ook vaak beter bestaande mechanismes te combineren. Veel mechanismes hebben een 'command hook' en het is niet zo lastig om bijvoorbeeld het synoniem mechanisme op die manier uit te breiden met een tooltip. Er zijn inmiddels verschillende suggesties gedaan en ik ga daar niets aan toevoegen. Het is niet mijn probleem als een gebruiker gebrek heeft aan fantasie danwel suggesties niet gebruikt cq. zijn mails zodanig formuleert dat er niemand zin heeft om te reageren. Het verbaast me zowieso dat er gereageerd wordt, zeker als de toonzetting ronduit beledigend is, maar dat kan aan mijn gebrekkige engels liggen. Overigens, in een perl of lua handleiding zie je ook geen kant en klare antwoorden. Men mag er zelf wel wat voor doen. "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: Lijkt me logisch, waarom zou ik een glossary beschrijven als het over een index gaat. Je bent de eerste die hier deze twee door elkaar haalt. Overigens, in mkiv kun je user data laten meereizen en gebruiken maar dat leg ik nog wel eens uit (of misschien ook nooit, want ik waag me niet meer aan Engels). "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": Ach ja, gsub(manual,"index","glossary") zal je niet geven wat je zoekt vrees ik. Overigens, we hebben dat soort 'begrippenlijsten in vrijwel elk van onze projekten dus het kan echt wel. Etc etc. Overigens, als ik zoveel commentaar had op een programma en de manuals, dan was ik al lang afgehaakt dus een doorzetter ben je wel. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] strange page break
On Thu, May 06 2010, Wolfgang Schuster wrote: > \setuphead[section][before={\allowbreak\blank[2*big]}] Thanks for this workaround! > The problem is indeed that ConTeXt tries to keep the header and the material > before the header together And does this make sense? Keeping header and the material after the header together *does* make sense, but not the material *before*. Thanks for your investigations! Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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 ___
Re: [NTG-context] strange page break
On 6 mai 2010, at 11:13, Wolfgang Schuster wrote: > Am 06.05.10 10:46, schrieb Otared Kavian: >> Hi Peter, >> >> I had noticed such strange page breaks before and since it was always in >> small documents (maths problem sheets), I used an elementary workaround >> which consists in adding a \medskip or \smallskip before every \section. >> Actually analogous bad page breaks happen in Plain TeX with \beginsection. >> Regarding the minimal example you sent, adding >> \setuphead[section][before=\smallskip] >> to the top of your document, solves the problem appearing in the first >> section. I don't know whether this solves all other strange page breaks or >> not. > > You should at least keep the original space before the \section. > > \setuphead[section][before={\allowbreak\blank[2*big]}] Hi Wolfgang, Yes, indeed you are right: my point was that adding something before the section solves, sometimes such problems (I can't say why), but as you say one must, or it is wiser to, keep the original space around the \section. > The problem is indeed that ConTeXt tries to keep the header and the material > before the header together and there is no real key to control this. What you > can find in the core is this > > % \chardef\somestructureheadbreakmethod\plusone % 0=nothing, 1=weighted, > 2=strict, 3=vspacing > \chardef\somestructureheadbreakmethod\plusthree > > but that's not what i consider to be available for the user. … well, at least not available for users such as me… But it is available for you :-) Best regards: OK ___ 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 ___
Re: [NTG-context] Article titles not capitalized in bibliography
Tom wrote: 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 This is controlled by the bst files and cannot be corrected elsewhere. In each of the four bst files in bibtex/bst/context, there are two calls to the do.t.out function: FUNCTION {format.t.title} { "" "\title" title do.t.out "" "\isbn" isbn do.out } FUNCTION {format.arttitle} { "" "\arttitle" title do.t.out } These calls have to be replaced by do.out: FUNCTION {format.t.title} { "" "\title" title do.out "" "\isbn" isbn do.out } FUNCTION {format.arttitle} { "" "\arttitle" title do.out } You will have to do that in a local copy, as I am a hesitant to change this in the distribution (it would introduce compatibility problems in already existing documents). Best wishes, Taco Best wishes, Taco ___ 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 ___
Re: [NTG-context] strange page break
Am 06.05.10 10:46, schrieb Otared Kavian: Hi Peter, I had noticed such strange page breaks before and since it was always in small documents (maths problem sheets), I used an elementary workaround which consists in adding a \medskip or \smallskip before every \section. Actually analogous bad page breaks happen in Plain TeX with \beginsection. Regarding the minimal example you sent, adding \setuphead[section][before=\smallskip] to the top of your document, solves the problem appearing in the first section. I don't know whether this solves all other strange page breaks or not. You should at least keep the original space before the \section. \setuphead[section][before={\allowbreak\blank[2*big]}] The problem is indeed that ConTeXt tries to keep the header and the material before the header together and there is no real key to control this. What you can find in the core is this % \chardef\somestructureheadbreakmethod\plusone % 0=nothing, 1=weighted, 2=strict, 3=vspacing \chardef\somestructureheadbreakmethod\plusthree but that's not what i consider to be available for the user. Wolfgang ___ 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 ___
Re: [NTG-context] strange page break
Hi Peter, I had noticed such strange page breaks before and since it was always in small documents (maths problem sheets), I used an elementary workaround which consists in adding a \medskip or \smallskip before every \section. Actually analogous bad page breaks happen in Plain TeX with \beginsection. Regarding the minimal example you sent, adding \setuphead[section][before=\smallskip] to the top of your document, solves the problem appearing in the first section. I don't know whether this solves all other strange page breaks or not. Best regards: OK On 6 mai 2010, at 10:13, Peter Münster wrote: > On Wed, May 05 2010, Wolfgang Schuster wrote: > >> The *strict prevents widows and orphans (comment \setuplayout in this >> example) >> but the important setting here is \setupalign[line]. > > Hello Wolfgang, > > I know that \setupalign[line] means: last line should touch the bottom. > It can be useful, but it's not always what I want. > > Here an example from real life (not the content... ;). I hope you agree, > that there should be done something in the default setup of ConTeXT: > > %\setuplayout[setups=*strict] % this helps only in some cases... > %\setupalign[line] % this means "flushbottom" and I don't always want that > \def\Lines#1{\dorecurse{#1}{\dorecurse{17}{text }}\par} > \def\Table#1{\starttable[|l|]\dorecurse{#1}{\NC bla \NC\AR}\stoptable} > \showframe > \starttext > \completecontent > \section{bla} > \Lines{10} > \Lines3 > \section{bla} > \Table9 > \section{bla} > \subsection{bla} > \Lines2 > \placetable[force][bla1]{bla}{\Table7} > \Lines2 > \subsection{bla} > \Lines7 > \placetable[force][bla2]{bla}{\Table{22}} > \subsection{bla} > \Lines2 > \placefigure[force][bla3]{}{\framed[height=2cm]{bla}} > \subsubsection{bla} > \Lines8 > \subsubsection{bla} > \Lines2 > \subsubsection{bla} > \Lines4 > \subsubsection{bla} > \Lines2 > \section{bla} > \Lines{15} > \Lines2 > \section{bla} > \Lines2 > \Table9 > \Lines2 > \stoptext > > Cheers, Peter %% Otared Kavian Département de Mathématiques Université de Versailles Saint-Quentin Bâtiment Fermat 45 aveue des Etats Unis 78035 Versailles cedex Téléphone: +33 1 39 25 46 42 Secrétariat: +33 1 39 25 46 44 Secrétariat: +33 1 39 25 46 46 e-mail: otared.kav...@math.uvsq.fr ___ 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 ___
Re: [NTG-context] strange page break
On Wed, May 05 2010, Wolfgang Schuster wrote: > The *strict prevents widows and orphans (comment \setuplayout in this > example) > but the important setting here is \setupalign[line]. Hello Wolfgang, I know that \setupalign[line] means: last line should touch the bottom. It can be useful, but it's not always what I want. Here an example from real life (not the content... ;). I hope you agree, that there should be done something in the default setup of ConTeXT: %\setuplayout[setups=*strict] % this helps only in some cases... %\setupalign[line] % this means "flushbottom" and I don't always want that \def\Lines#1{\dorecurse{#1}{\dorecurse{17}{text }}\par} \def\Table#1{\starttable[|l|]\dorecurse{#1}{\NC bla \NC\AR}\stoptable} \showframe \starttext \completecontent \section{bla} \Lines{10} \Lines3 \section{bla} \Table9 \section{bla} \subsection{bla} \Lines2 \placetable[force][bla1]{bla}{\Table7} \Lines2 \subsection{bla} \Lines7 \placetable[force][bla2]{bla}{\Table{22}} \subsection{bla} \Lines2 \placefigure[force][bla3]{}{\framed[height=2cm]{bla}} \subsubsection{bla} \Lines8 \subsubsection{bla} \Lines2 \subsubsection{bla} \Lines4 \subsubsection{bla} \Lines2 \section{bla} \Lines{15} \Lines2 \section{bla} \Lines2 \Table9 \Lines2 \stoptext Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ ___ 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 ___
Re: [NTG-context] Captials in section head
Am 05.05.10 15:22, schrieb Carsten Fechtmann: Is there also a way how to achieve this in MkII ? (other than by hand) \setuphead[...][deeptextcommand=\WORD] Wolfgang ___ 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 ___
Re: [NTG-context] Captials in section head
Try \uppercased instead of \uppercase (Just guess, untested) On Wed, May 5, 2010 at 4:22 PM, Carsten Fechtmann wrote: > > Is there also a way how to achieve this in MkII ? (other than by hand) > > Cheers > Carsten > > Am 04.06.2009 um 16:34 schrieb richard.steph...@converteam.com: > >> >>> Am 04.06.2009 um 14:56 schrieb richard.steph...@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 >> ___ >> 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 : https://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 > ___ > ___ 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 ___