- ntg-context - Mailing Lists

Re: [NTG-context] Making a template, defining a macro
by Demián Gutierrez 31 Jul '08

31 Jul '08

Thanks a million! Works perfect :-) Wolfgang Schuster wrote: > On Thu, Jul 31, 2008 at 1:18 AM, Demián Gutierrez > <dmi(a)minotauro.com.ve> wrote: >> Hi, >> >> I have to prepare a template to typeset a document that will have a >> lot of tables of similar kinds repeated across the document. I want to >> put that tables in some kind of templates, so I can use those >> templates over and over. So the idea is to hide to the authors all the >> format details behind the template allowing them to focus on the data >> that has to be filled in those tables (which is the important thing). >> >> So, I would like to define some macros, that allows me to do something like: >> >> \starttableX >> \startSomeField >> Some Field Value... >> \stopSomeField >> >> \startOtherField >> Other Field Value... >> \stopOtherField >> \stoptableX >> >> And the result, should be a table like this: >> >> | Some Field Label: | Some Field Value... | >> | Other Field Label: | Other Field Value... | >> >> That way I define a template for each table type I'll have in the document. >> >> I'm not having trouble with the tables, but with the macro definition, >> this is my approximation of what I want (which does not work): >> >> \startsetups crudmain >> \long\def\startguiname #1 >> \stopguiname{\setvariables[crudmain][guiname=#1]} >> \long\def\startclassname #1 >> \stopclassname{\setvariables[crudmain][classname=#1]} >> >> GUI Name: \getvariable{crudmain}{guiname} >> Class Name: \getvariable{crudmain}{classname} >> \stopsetups >> >> \definestartstop[crudmain][commands=\setups{crudmain}] >> >> \startcrudmain >> \startguiname >> Some name here... >> \stopguiname >> \startclassname >> Other name here... >> \stopclassname >> \stopcrudmain >> >> At this point I'm getting this error: >> >> ! Use of \startguiname doesn't match its definition. >> >> I want the \long\def\startguiname inside the \startsetups / >> \stopsetups to be sure that it will only be called inside the >> \startcrudmain / \stopcrudmain (Cause other tables of different types >> may have fields with the same name). But even considering the previous >> point, if I move the \long\def\startguiname outside the \startsetups / >> \stopsetups definition it does not works, because the >> \getvariable{crudmain}{guiname} just returns blank. >> >> So is it possible to do what I want or something similar? What would >> be a good way to do it? Any advice on the code I've already written? >> This is really getting me crazy, cause context is not like any other >> programming language I'm used to use ;-) > > \def\startcrudmain > {\bgroup > \def\startguiname##1\stopguiname > {\setvalue{crudmain:guiname}{##1}}% > \def\startclassname##1\stopclassname > {\setvalue{crudmain:classname}{##1}}} > > \def\stopcrudmain > {\bTABLE[frame=off]% > \bTR > \bTD GUI Name: \eTD > \bTD \getvalue{crudmain:guiname} \eTD > \eTR > \bTR > \bTD Class Name: \eTD > \bTD \getvalue{crudmain:classname} \eTD > \eTR > \eTABLE > \egroup} > > \starttext > > \startcrudmain > \startguiname > Some name here... > \stopguiname > \startclassname > Other name here... > \stopclassname > \stopcrudmain > > \stoptext > > Wolfgang > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an > entry to the Wiki! > > maillist : ntg-context(a)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 > ___________________________________________________________________________________ > >

1 0

problem with \appendtoks \to\everypar
by Steffen Wolfrum 31 Jul '08

31 Jul '08

Hi, There is no hangover for italics. Please have a look: \starttext \def\hangover{\hangafter=1\hangindent=1em} \definestartstop[hangingarea] [before={\bgroup\appendtoks\hangover\to\everypar}, after=\egroup] \starthangingarea \input tufte {\it italic} text roman test text roman test text roman test text roman test text roman test text roman test text roman test text roman test text roman test text \stophangingarea \stoptext Thanks, Steffen

3 2

Re: [NTG-context] mkii and xetex with tl2008: invalid fontname errors
by Mojca Miklavec 31 Jul '08

31 Jul '08

Taco: > ... does it actually work, and can you explain why? I don't get the "error" any more with that fix (and it's not an error anyway). The problem is that if there is no "file:" prefix in font synonyms, then ConTeXt asks for \font\whatever="texgyre-whatever:options" and XeTeX first asks fontconfig, font not there, and then asks kpathsea and kpathsea complains about "font not present". With minimals I don't get that complaint printed out. It used to complain in some other way some time ago, but let's forget that for a moment. Then, since ConTeXt figures out that font doesn't exist, it asks for \font\whatever="[texgyge-whatever]:options" and then XeTeX finds the font and ConTeXt uses it. There's a third iteration asking for a font without quotes, but I should check the exact order of those three attempts, and maybe attempt without quotes is not needed any more since Jonathan fixed the behaviour of quoted filenames to also look for kpathsea fonts, not only system fonts if I recall correctly. If there is "file:" prefix, the first iteration is skipped, so it's more efficient to load fonts. We have fixed that (added "file:" in front of names) in number of font definitions some time ago (most important being LM since it's really used each time when one compiles a XeTeX document), but those "palatino"/"times" synonyms were not fixed at the time of major changes for some reason (overseen, me being lazy, it worked anyway?, ... I don't quite remember). However, there is still "problem" with "+trep" (a missing/unneeded mapping, depends on how you treat it) in this font call: texgyrepagella-italic:+liga;+kern;mapping=tlig;+trep; trep and tlig both happened to map to tex-text some time ago. Then I asked Hans to optimize the behaviour a bit since some mappings of " and ` were really cruel and lead to inability to use grave accents at all. He removed some mappings, but left both tlig and trep there. In luatex, tlig does a mapping of -- and --- and trep does a mapping of apostrophe. In XeTeX +tlig option in "features=default" gets replaced by "mapping=tlig" which has all the three replacements (--, --- and ') font-ini.tex: \remapfontfeature tlig yes mapping=tlig while +trep is passed unmodified to xetex. So the behaviour is inconsistent in LuaTeX and XeTeX (no reason why it should be), but it just happens that nobody cares/complains. The second option would be useful if one really wanted to recall all the other TeX ligatures and replacements back (`, ``, ", >>, <<, `<, `> or whatever else is there), else I think that having two options is really not needed. tlig and trep used to have all the other old TeX replacements & ligatures there, but I asked Hans to remove most of them exactly for the reason mentioned above (grave accents were gone). XeTeX just happens not to complain about "+trep", but that "+trep" should be removed one day. Maybe just font-ini.tex: \remapfontfeature trep yes [empty] Mojca

1 0

Error when calling \placecontent from product
by Elliot Clifton 31 Jul '08

31 Jul '08

Hi, I'd appreciated some help with the following problem. How can I stop the following code generating an error on calling \placecontent from a product? In the test case I have files: env-test, prd-test, cmp-test. \startenvironment [env-test] \def\dostartArticle[#1]% generate article header with {\getgparameters[my][#1] \chapter{\mytitle} } \def\dostopArticle{% \page} \def\startArticle{\dosingleempty\dostartArticle} \def\stopArticle{\dosingleempty\dostopArticle} \stopenvironment \startproduct prd-test \environment ../env-test \placecontent %fails with Undefined control sequence \mytitle \component cmp-test \stopproduct \startcomponent[cmp-test] \product prd-test \environment env-test %\placecontent %works here \startArticle[title={Into the unknown}, author={A. U. Thor}] %author parameter unused in test, just example of what I expect \startArticle to look like \input knuth \stopArticle \stopcomponent Any ideas how to make this work? TIA, Elliot

2 1

OpenType beginners question
by Ulrich Dirr 31 Jul '08

31 Jul '08

Hi, I've adapted the complete luatex/markiv typescript example at http://wiki.contextgarden.net/Mark_IV#Opentype_features for FF Kievit Pro I. It works quiet nice out of the box (aaah, nomore fiddling with font installation!). \starttypescript [sans] [kievit] \definefontsynonym [KievitProRegular] [name:KievitPro-Regular] [features=default] \definefontsynonym [KievitProMedium] [name:KievitPro-Medium] [features=default] \definefontsynonym [KievitProExtraBold] [name:KievitPro-ExtraBold] [features=default] \definefontsynonym [KievitProItalic] [name:KievitPro-Italic] [features=default] \definefontsynonym [KievitProMediumItalic] [name:KievitPro-MediumItalic] [features=default] \definefontsynonym [KievitProExtraBoldItalic] [name:KievitPro-ExtraBoldItalic] [features=default] \stoptypescript \starttypescript [sans] [kievit] \definefontsynonym [Sans] [KievitProRegular] [features=default] \definefontsynonym [SansItalic] [KievitProItalic] [features=default] \definefontsynonym [SansBold] [KievitProMedium] [features=default] \definefontsynonym [SansSlanted] [SansItalic] [features=default] \definefontsynonym [SansBoldSlanted] [SansBoldItalic] [features=default] \definefontsynonym [SansCaps] [Sans] [features=smallcaps] \stoptypescript \definetypeface[kievit][rm][sans][kievit][default] \definetypeface[kievit][ss][sans][kievit][default] \definetypeface[kievit][tt][mono][modern] [default][rscale=1.12] \definetypeface[kievit][mm][math][iwona] [default][rscale=1.02] \setupbodyfont[kievit,ss,10pt] Now \bf \it works perfectly well but \sc doesn't. Do I need some extra definition? Best regards, Ulrich

9 11

Making a template, defining a macro
by Demián Gutierrez 31 Jul '08

31 Jul '08

Hi, I have to prepare a template to typeset a document that will have a lot of tables of similar kinds repeated across the document. I want to put that tables in some kind of templates, so I can use those templates over and over. So the idea is to hide to the authors all the format details behind the template allowing them to focus on the data that has to be filled in those tables (which is the important thing). So, I would like to define some macros, that allows me to do something like: \starttableX \startSomeField Some Field Value... \stopSomeField \startOtherField Other Field Value... \stopOtherField \stoptableX And the result, should be a table like this: | Some Field Label: | Some Field Value... | | Other Field Label: | Other Field Value... | That way I define a template for each table type I'll have in the document. I'm not having trouble with the tables, but with the macro definition, this is my approximation of what I want (which does not work): \startsetups crudmain \long\def\startguiname #1 \stopguiname{\setvariables[crudmain][guiname=#1]} \long\def\startclassname #1 \stopclassname{\setvariables[crudmain][classname=#1]} GUI Name: \getvariable{crudmain}{guiname} Class Name: \getvariable{crudmain}{classname} \stopsetups \definestartstop[crudmain][commands=\setups{crudmain}] \startcrudmain \startguiname Some name here... \stopguiname \startclassname Other name here... \stopclassname \stopcrudmain At this point I'm getting this error: ! Use of \startguiname doesn't match its definition. I want the \long\def\startguiname inside the \startsetups / \stopsetups to be sure that it will only be called inside the \startcrudmain / \stopcrudmain (Cause other tables of different types may have fields with the same name). But even considering the previous point, if I move the \long\def\startguiname outside the \startsetups / \stopsetups definition it does not works, because the \getvariable{crudmain}{guiname} just returns blank. So is it possible to do what I want or something similar? What would be a good way to do it? Any advice on the code I've already written? This is really getting me crazy, cause context is not like any other programming language I'm used to use ;-) Thanks in Advance Demián

2 1

Figure Captions and Equation Numbers
by Ernesto Schirmacher 31 Jul '08

31 Jul '08

Wolfgang, Thank you very much for both solutions. They work like a charm! Best regards, Ernesto

1 0

Sample code: a textbook
by Jörg Hagmann 30 Jul '08

30 Jul '08

Some time ago, I showed a few sample pages of a biochemistry textbook I wrote in ConTeXt. I now uploaded the setup file with comments in ContextGarden (http://wiki.contextgarden.net/Biochemistry_textbook) I hope that it will be useful for beginners---I found examples helpful myself. A comment regarding the ongoing documentation discussion: The "Excursion" is basically excellent, I also love its Wordsworthian title; keep it! All that's needed is a few corrections and additions. Just an example: Based on "Excursion", you wouldn't be able to indent paragraphs. You'll find the answer in the FAQs, where a beginner probably wouldn't look for it (he/she would probably just give up). Cheers, Jörg -- Prof. Jörg Hagmann-Zanolari MD University of Basel Department of Biomedicine Institute of Biochemistry and Genetics Mattenstrasse 28 CH-4058 Basel Switzerland Phone +41 (0)61 267 3565

4 4

\*interaction* commands
by Alan Stone 30 Jul '08

30 Jul '08

HI, Where can I find a *comprehensive* explanation of all \*interaction* commands and their options ? Thanks, Alan

3 9

Avoiding hyphenation
by Maurício 30 Jul '08

30 Jul '08

Hi, How can avoid a word to be hyphenated? I know that it is a basic question, but all I was able to find was a tip about using \hbox{}, which didn't work. Thanks, Maurício

3 2