- ntg-context - Mailing Lists

Re: [NTG-context] how to get thick and thin borders working in tables (ConTeXt)
by Lars Huttar 10 Dec '08

10 Dec '08

On 12/9/2008 12:04 PM, Wolfgang Schuster wrote: > > Am 09.12.2008 um 17:48 schrieb Lars Huttar: > >> Hello, >> >> We are using ConTeXt (with XeTeX engine) to typeset some tables that >> have borders (rules) between cells. >> >> In the previous edition of the book (which was not done in TeX), some of >> the lines between table cells were double, others single. This was done >> to show grouping of columns and rows. We have been told that in TeX, or >> at least in ConTeXt, you can't do double rules (we'd be happy to be >> corrected on that point), so we have been trying to use thick and thin >> lines to show grouping. >> >> Thick or thin lines work fine if applied to whole tables or whole cells, >> but when there are cells with thick rules on some sides and thin rules >> on other sides, it gets confused. >> >> For example, we tried >> (a) \setupTABLE[c][4][leftframe=on,rulethickness=0.5mm] >> to set the left border of the fourth column to be thick. This worked. >> But then if we use >> (b) \setupTABLE[c][4][rightframe=on,rulethickness=0.25mm] >> to set the right border of the same column to be thin, it overrides the >> thickness of both left and right borders, so setting (a) is lost. >> >> In other words, we can't seem to get a given cell to have a thick border >> on one side and a thin border on the other side. (Well, we could fake it >> in some cases by setting rulethickness for an adjacent cell, but that >> adjacent cell would then have to have thick borders on all sides.) >> >> Does anybody know if it's possible to do this in ConTeXt? or in TeX? >> >> Thanks for any ideas, >> Lars >> >> P.S. >> Incidentally, if you set the bottom border of row 1 and the top border >> of row 2 each to be thick, the result is additive: you get a >> doubly-thick border. > > I can provide a patch for ConTeXt to draw rules with different > thickness on each side but I can't assure it will work in the future. > > With metapost you can nearly all types of borders you want. > > \startuseMPgraphic{table:frame:double} > draw OverlayBox enlarged -\the\dimexpr\linewidth/2\relax ; % outer frame > draw OverlayBox enlarged -2pt ; % inner frame > setbounds currentpicture to OverlayBox ; > \stopuseMPgraphic > > \startuseMPgraphic{table:frame:all} > draw OverlayBox enlarged -\the\dimexpr\linewidth/2\relax ; > setbounds currentpicture to OverlayBox ; > \stopuseMPgraphic > > \startuseMPgraphic{table:frame:left} > linecap := squared ; > draw leftboundary OverlayBox withpen pencircle scaled 2 ; > setbounds currentpicture to OverlayBox ; > \stopuseMPgraphic > > \startuseMPgraphic{table:frame:right} > linecap := squared ; > draw rightboundary OverlayBox withpen pencircle scaled 2 ; > setbounds currentpicture to OverlayBox ; > \stopuseMPgraphic > > \startuseMPgraphic{table:frame:top} > linecap := squared ; > draw topboundary OverlayBox withpen pencircle scaled 2 ; > setbounds currentpicture to OverlayBox ; > \stopuseMPgraphic > > \startuseMPgraphic{table:frame:bottom} > linecap := squared ; > draw bottomboundary OverlayBox withpen pencircle scaled 2 ; > setbounds currentpicture to OverlayBox ; > \stopuseMPgraphic > > \defineoverlay[table:frame:double][\useMPgraphic{table:frame:double}] > > \defineoverlay[table:frame:all] [\useMPgraphic{table:frame:all}] > \defineoverlay[table:frame:left] [\useMPgraphic{table:frame:left}] > \defineoverlay[table:frame:right] [\useMPgraphic{table:frame:right}] > \defineoverlay[table:frame:top] [\useMPgraphic{table:frame:top}] > \defineoverlay[table:frame:bottom][\useMPgraphic{table:frame:bottom}] > > \starttext > > \startbuffer > \bTABLE[frame=off,offset=2ex] > \bTR > \bTD One \eTD > \bTD Two \eTD > \bTD Three \eTD > \eTR > \bTR > \bTD Four \eTD > \bTD Five \eTD > \bTD Six \eTD > \eTR > \bTR > \bTD Seven \eTD > \bTD Eight \eTD > \bTD Nine \eTD > \eTR > \eTABLE > \stopbuffer > > \start > \setupTABLE[background={table:frame:double}] > \getbuffer > \stop > \blank > > \start > \setupTABLE[background={table:frame:all}] > \setupTABLE[c][first][background={table:frame:all,table:frame:left}] > \setupTABLE[c][last][background={table:frame:all,table:frame:right}] > \setupTABLE[r][first][background={table:frame:all,table:frame:top}] > \setupTABLE[r][last][background={table:frame:all,table:frame:bottom}] > \setupTABLE[first][first][background={table:frame:all,table:frame:left,table:frame:top}] > > \setupTABLE[last][first][background={table:frame:all,table:frame:right,table:frame:top}] > > \setupTABLE[first][last][background={table:frame:all,table:frame:left,table:frame:bottom}] > > \setupTABLE[last][last][background={table:frame:all,table:frame:right,table:frame:bottom}] > > \getbuffer > \stop > > \stoptext > > Wolfgang > > > Thanks for the very detailed example! We should be able to apply this to our document. I'm copying it to the list because I think it would be valuable for posterity. Thanks to Aditya too for the reply. Regards, Lars -- Lars Huttar

1 1

backward-incompatible behavior of Palatino and modern
by Sanjoy Mahajan 09 Dec '08

09 Dec '08

I texexec'ed a one-page file that I hadn't compiled for almost a year (preparing for the next offering of the course). The font sizes increased, resulting in a two-page PDF file. The one-page result, which is what I expected, came from ConTeXt 2008.01.02 (MkII), for which I had selected font sizes to fit it onto one page. I couldn't find that release in the museum, so it was probably 2007.12.31 with my patches. I downloaded the cont-tmf for 2007.12.31, and it too produced the expected one-page PDF file. Whereas current versions produce a two-page file, either with 2008.10.31 from the Debian packages and with 2008.11.10 on live.contextgarden.net. I'm not sure which behavior (2007 or 2008) is correct. Below is a minimal example testfile.tex producing only a few lines instead of a whole page, but it illustrates the differences. With the 2007.12.31 version, the lines fits within the frame (from \showframe). With the new versions, the "Approximation" extends outside the frame, and the "The Art" gets split onto separate lines. Commenting out the "\setupbodyfont [palatino,11pt]" line makes the two versions identical. But the original example uses Palatino text, so I cannot do that for the long-term solution. I've attached 'good' and 'bad' PDF files. If the new version is correct, I'll retune the font sizes to make it fit, and it's no big deal. But I'm reporting the issue in case the example has exposed an unexpected change in ConTeXt over the last year. -Sanjoy ======= cut here: testfile.tex ==================== \setuppapersize[letter,landscape][letter,landscape] \setuplayout[height=fit,margin=0pt,width=fit, backspace=0.7in,cutspace=0.7in,topspace=0in,bottomspace=-0.2in] \setuppagenumbering[location=] \usetypescript [palatino][\defaultencoding] \setupbodyfont [palatino,11pt] \showframe \starttext \raggedleft \setupbodyfont[modern,54pt]\ss {\bfa 6.055J/2.038J\hfill The Art of}% \break \baselineskip=19pt% \setupbodyfont[modern,50.7pt]% \bfd Approximation \stoptext ======= cut here: testfile.tex ====================

2 2

how to get thick and thin borders working in tables (ConTeXt)
by Lars Huttar 09 Dec '08

09 Dec '08

Hello, We are using ConTeXt (with XeTeX engine) to typeset some tables that have borders (rules) between cells. In the previous edition of the book (which was not done in TeX), some of the lines between table cells were double, others single. This was done to show grouping of columns and rows. We have been told that in TeX, or at least in ConTeXt, you can't do double rules (we'd be happy to be corrected on that point), so we have been trying to use thick and thin lines to show grouping. Thick or thin lines work fine if applied to whole tables or whole cells, but when there are cells with thick rules on some sides and thin rules on other sides, it gets confused. For example, we tried (a) \setupTABLE[c][4][leftframe=on,rulethickness=0.5mm] to set the left border of the fourth column to be thick. This worked. But then if we use (b) \setupTABLE[c][4][rightframe=on,rulethickness=0.25mm] to set the right border of the same column to be thin, it overrides the thickness of both left and right borders, so setting (a) is lost. In other words, we can't seem to get a given cell to have a thick border on one side and a thin border on the other side. (Well, we could fake it in some cases by setting rulethickness for an adjacent cell, but that adjacent cell would then have to have thick borders on all sides.) Does anybody know if it's possible to do this in ConTeXt? or in TeX? Thanks for any ideas, Lars P.S. Incidentally, if you set the bottom border of row 1 and the top border of row 2 each to be thick, the result is additive: you get a doubly-thick border.

2 1

Building tables at runtime via --mode= option
by Bart C. Wise 09 Dec '08

09 Dec '08

I'm trying to build a table in a project that will be built based on a commandline parameter. Currently, I'd like to use the "--mode=<>" command. However, I've run into a number of snags that I have attempted to solve without any luck. I've included some sample code of what I would like to do. I can do all of what I need using \doifmodeelse, etc. However, I'm looking for a more elegeant solution. Any hints/solutions are welcomed! Problems: 1) \currentmode: I cannot use this variable in my file, but it works in the source code. Question: Is the mode option okay, or is there a better way? 2) CellWidth (below) needs to be a floating point dimension, based the size of the paper. So I need to divide the size of the paper (\textwidth) by a number and make sure it stays as a dimension. 3) I tried to use \getnumber[Rounds] to span a number of columns ( \bTD[nc=\getnumber[Rounds]]) but this would not compile. Here's the error: Runaway argument? Rounds=\plusone \ifnum \tblny =\plusone \ifnum \currentcol >\maximumcol \ETC. ! Paragraph ended before \getnumber was complete. Sample: \definenumber[Rounds] \setnumber[Rounds]{6} % desire: \setupnumber[Rounds]{\currentmode} % and verify that it's a number between a given range. % \currentmode comes back as undefined \definenumber[TotalCol] \setnumber[TotalCol]{\getnumber[Rounds] + 2} \def\CellWidth{0.625in} % desire: based on textwidth: \textwidth / \getnumber[TotalCol] % Needs to be floating point \starttext Rounds: \getnumber[Rounds]\crlf TotalCol: \getnumber[TotalCol]\crlf CellWidth: \CellWidth\crlf \bTABLE[align={middle,lohi},strut=no,width=\CellWidth] % Row 1 \bTR[frame=off] \bTD\eTD \bTD[nc=6] Title\eTD %desire: \bTD[nc=\getnumber[Rounds]] Title\eTD \eTR %Row 2 \bTR \bTD\eTD \dorecurse{\getnumber[Rounds]}{\expanded{\bTD\recurselevel\eTD}} \bTD\eTD \eTR %Row 3 \bTR \dorecurse{\getnumber[TotalCol]}{\expanded{\bTD\recurselevel\eTD}} \eTR \eTABLE \stoptext Thanks! Bart

1 0

Gentium package (was: minimals and greek font)
by Mojca Miklavec 09 Dec '08

09 Dec '08

On Wed, Oct 29, 2008 at 3:05 PM, Alan BRASLAU wrote: > Hello, > > What needs to be done to include greek fonts on top of the minimal > installation? Thank you. > > example: > \usemodule[greek] > \starttext > \greek{kalamos} > \stoptext Hello, Thomas has just prepared a new font package (before leaving for a few days) with support for Gentium: http://tug.ctan.org/tex-archive/fonts/gentium/ I'll add it to minimals, but you may play with it already. The contents of Greek module will be adapted once he comes back, but you can use it in standard ways. \usetypescriptfile[type-gentium] \usetypescript[gentium][agr] \setupbodyfont[gentium] \enableregime[...] \starttext ... greek text ... \stoptext Mojca

2 2

Problem with fonts
by Mohamed Bana 09 Dec '08

09 Dec '08

i just updated the minimals and I can no longer typeset, even though $ mtxrun --script fonts --list shows the font ! LuaTeX error ...mals/tex/texmf-context/tex/context/base/luat-log.lua:75: bad argument #2 to 'format' (string expected, got table) stack traceback: [C]: in function 'format' ...mals/tex/texmf-context/tex/context/base/luat-log.lua:75: in function 'report' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:1431: in function 'after' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:895: in function 'load' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:1845: in function 'otf_to_tfm' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:2066: in function 'read_from_open_type' ...mals/tex/texmf-context/tex/context/base/font-def.lua:333: in function <...mals/tex/texmf-context/tex/context/base/font-def.lua:315> (tail call): ? ...mals/tex/texmf-context/tex/context/base/font-def.lua:250: in function 'read' ...mals/tex/texmf-context/tex/context/base/font-def.lua:645: in function 'read' ...mals/tex/texmf-context/tex/context/base/font-def.lua:752: in function 'command_2' <main ctx instance>:1: in main chunk. \lowleveldefinefont ...s ", "\@@fontfallbacks " )} \edef \somefontspec {at \s... \xxdododefinefont ...efont {#4}\newfontidentifier \let \localrelativefontsiz... \fontstrategy ...me \fontclass #2#3#4#5\endcsname \tryingfontfalse \fi <inserted text> ...yle \fontalternative \fontsize \fi \iftryingfont \fontstr... \synchronizefont ...strategy \the \fontstrategies \relax \fi \iftryingfont \... <argument> \getvalue {\@style@ \fontstyle } \edef \fontstyle {\fontstyle }\if... ... l.148 \setupbodyfont[mainface,13pt] %should be 12pt, use 12.5pt for minion a... ? %%% test.tex %%% % engine=luatex \enableregime [utf-8] \def\sc{\setfontfeature{smallcaps}} \definefontfeature [default][default] [protrusion=quality,expansion=quality,mode=node,script=latn] \definefontfeature [oldstyle][default] [protrusion=quality,expansion=quality,mode=node,script=latn,onum=yes] \definefontfeature [smallcaps][default] [protrusion=quality,expansion=quality,mode=node,script=latn,smcp=yes] \usetypescript [serif] [hanging] [pure] \setupalign [hanging] \setfontfeature{oldstyle} \usetypescriptfile[type-folio] \definetypeface[mainface][rm][serif][warnockpro] [default] [features=default] \definetypeface[mainface][ss][sans][myriadpro] [default] [features=default] \definetypeface [mainface] [mm] [math] [palatino] [default] [encoding=texnansi] \setupbodyfont[mainface,13pt] \starttext {\tfa HELLO} {\tfb WORLD} \stoptext %%% type-folio.tex %%% \starttypescript [serif] [minionpro] \definefontsynonym [MinionPro-Regular] [name:minionproregular] \definefontsynonym [MinionPro-Bold] [name:minionprobold] \definefontsynonym [MinionPro-Italic] [name:minionproit] \definefontsynonym [MinionPro-BoldItalic] [name:minionproboldit] \stoptypescript \starttypescript [serif] [minionpro] \definefontsynonym [Serif] [MinionPro-Regular] [features=default] \definefontsynonym [SerifBold] [MinionPro-Bold] [features=default] \definefontsynonym [SerifItalic] [MinionPro-Italic] [features=default] \definefontsynonym [SerifBoldItalic] [MinionPro-BoldItalic] [features=default] % \definefontsynonym [SerifSlanted] [SerifItalic] [features=default] \definefontsynonym [SerifCaps] [Serif] [features=smallcaps] \stoptypescript \starttypescript [sans] [myriadpro] \setups[font:fallback:sans] % \definefontsynonym [MyriadPro-Regular] [name:MyriadPro-Regular] [features=default] % \definefontsynonym [MyriadPro-Bold] [name:MyriadPro-Bold] [features=default] % \definefontsynonym [MyriadPro-Italic] [name:MyriadPro-It] [features=default] % \definefontsynonym [MyriadPro-BoldItalic] [name:MyriadPro-BoldIt] [features=default] \definefontsynonym [MyriadPro-Regular] [name:myriadproregular] \definefontsynonym [MyriadPro-Bold] [name:myriadprobold] \definefontsynonym [MyriadPro-Italic] [name:myriadproit] \definefontsynonym [MyriadPro-BoldItalic] [name:myriadproboldit] \stoptypescript \starttypescript [sans] [myriadpro] \definefontsynonym [Sans] [MyriadPro-Regular] [features=historic] \definefontsynonym [SansBold] [MyriadPro-Bold] [features=historic] \definefontsynonym [SansItalic] [MyriadPro-Italic] [features=historic] \definefontsynonym [SansBoldItalic] [MyriadPro-BoldItalic] [features=historic] \definefontsynonym [SansCaps] [Sans] [features=latin-smallcaps] \stoptypescript \starttypescript [serif] [warnockpro] \setups[font:fallback:serif] \definefontsynonym [WarnockPro-Regular] [name:warnockproregular] \definefontsynonym [WarnockPro-Bold] [name:warnockprobold] \definefontsynonym [WarnockPro-Italic] [name:warnockproit] \definefontsynonym [WarnockPro-BoldItalic] [name:warnockproboldit] \stoptypescript \starttypescript [serif] [warnockpro] \definefontsynonym [Serif] [WarnockPro-Regular] [features=default] \definefontsynonym [SerifBold] [WarnockPro-Bold] [features=default] \definefontsynonym [SerifItalic] [WarnockPro-Italic] [features=default] \definefontsynonym [SerifBoldItalic] [WarnockPro-BoldItalic] [features=default] \definefontsynonym [SerifCaps] [Serif] [features=smallcaps] \stoptypescript Log; (report.tex ConTeXt ver: 2008.11.10 21:40 MKIV fmt: 2008.12.9 int: english/english system : cont-new loaded (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/cont-new.tex systems : beware: some patches loaded from cont-new.tex (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/cont-new.mkiv) (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/cont-mtx.tex)) system : cont-fil loaded (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/cont-fil.tex loading : Context File Synonyms ) system : cont-sys loaded (/home/mbana/context-minimals/tex/texmf-context/tex/context/user/cont-sys.tex (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/type-tmf.tex) (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/type-siz.tex) (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/type-otf.tex)) bodyfont : 12pt rm is loaded specials : pdftex loaded language : language en is active system : report.top loaded (report.top) color : mpcmyk color space is supported color : mpspot color space is supported color : system rgb is global activated interaction : active (report.tuo) (report.tuo) system : module bib loaded (/home/mbana/context-minimals/tex/texmf-local/tex/context/bib/t-bib.tex publications : loading formatting style from bibl-apa (/home/mbana/context-minimals/tex/texmf-local/tex/context/bib/bibl-apa.tex)) publications : wrote a new auxiliary file report.aux publications : loading formatting style from bibl-ssa (bibl-ssa.tex) (/home/mbana/context-minimals/tex/texmf-context/tex/context/base/page-run.tex loading : Context Page Macros / Runtime Macros ) check : missing or ungrouped '=' after 'frame' in line 115 (@@ef) check : missing or ungrouped '=' after 'frame' in line 115 (@@ex) (type-folio.tex) load otf | loading: /media/sdb1/Fonts/Minion Pro/MinionPro-Regular.otf load otf | warning: The following table(s) in the font have been ignored by FontForge load otf | warning: Ignoring 'DSIG' digital signature table load otf | warning: Warning: Mac and Windows entries in the 'name' table differ for the Fullname string in the language English (US) Mac String: Minion Pro Windows String: MinionPro-Regular load otf | warning: The glyph named mu is mapped to U+00B5. But its name indicates it should be mapped to U+03BC. load otf | warning: The glyph named Delta is mapped to U+2206. But its name indicates it should be mapped to U+0394. load otf | warning: The glyph named Omega is mapped to U+2126. But its name indicates it should be mapped to U+03A9. load otf | enhance: patch load otf | enhance: before load otf | enhance: enrich load otf | enhance: registering tlig feature load otf | enhance: registering trep feature load otf | enhance: flatten load otf | flattening 'specifications' tables load otf | flattening 'anchor' tables load otf | flattening 'gpos' tables load otf | flattening 'gsub' tables load otf | enhance: analyze load otf | enhance: after load otf | replacing 'kerns' tables by 'mykerns' tables ! LuaTeX error ...mals/tex/texmf-context/tex/context/base/luat-log.lua:75: bad argument #2 to 'format' (string expected, got table) stack traceback: [C]: in function 'format' ...mals/tex/texmf-context/tex/context/base/luat-log.lua:75: in function 'report' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:1431: in function 'after' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:895: in function 'load' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:1845: in function 'otf_to_tfm' ...mals/tex/texmf-context/tex/context/base/font-otf.lua:2066: in function 'read_from_open_type' ...mals/tex/texmf-context/tex/context/base/font-def.lua:333: in function <...mals/tex/texmf-context/tex/context/base/font-def.lua:315> (tail call): ? ...mals/tex/texmf-context/tex/context/base/font-def.lua:250: in function 'read' ...mals/tex/texmf-context/tex/context/base/font-def.lua:645: in function 'read' ...mals/tex

2 3

Luatex beta 0.31 update warning
by Taco Hoekwater 09 Dec '08

09 Dec '08

Hi all, Quick warning from me: if you update from the minimals this week, be prepared for some potential problems with opentype fonts in luatex. Because of the update of the embedded fontforge, there are some differences in the font table format that Hans and I have yet to sort out. While that will not take long, it will still mean the beginning of next week at the earliest (because Hans is teaching in Brno). Best wishes, Taco Taco Hoekwater wrote: > > Hi, > > I have just uploaded luatex 0.31.1, hopefully fixing a bunch > of compilation errors on various platforms, but with no other > visible changes.

4 4

texexec ignores file order
by Ben Barrowes 09 Dec '08

09 Dec '08

exexec --pdfarrange --result=yujo_insurance.pdf yujo_insurance1.pdf yujo_insurance2.pdf yujo_insurance3.pdf yujo_insurance4.pdf yujo_insurance5.pdf yujo_insurance6.pdf yujo_insurance7.pdf yujo_insurance8.pdf yujo_insurance9.pdf yujo_insurance10.pdf yujo_insurance11.pdf yujo_insurance12.pdf After upgrading recently, I found that texexec no longer preserves the order of files passed to it. When I concatenate files with texexec, I often have more than 10 files I want to pass to texexec names filename1.pdf, filename2.pdf, ... filename12.pdf, etc. In the past, the following has worked to concatenate these in the correct order: texexec --pdfarrange --result=filename.pdf `ls -a -v filename*.pdf` Now, even if I pass filename10.pdf after filename2.pdf on the command line, texexec ingores this and puts filename10.pdf before filename2.pdf in the resulting concatenated file. Is there a fix for this, or is there a better way to concatenate pdf files? bb

3 2

Re: [NTG-context] questions on ctxtools and line break.
by Dalyoung Jeong 09 Dec '08

09 Dec '08

Dear Mojca, Yue, and Hans, Thank you for the help. I updated ConTeXt and LuaTeX using rsync to the foler .../texlive/ 2008/../texmf-local. "texmfstart texexec --make (--xtx) --all" run smoothly, but luatools still has a cnf error. I'll do it again from the beginning when I have time. However, it works fine in ConTeXt-minimal. One day Mr. Wolfgang tried to do some work to set up standardization of CJK for MKIV. However, it is not easy because Korean use space between words. The rules of line break for Korean is simple in saying. We don't need any hyphenation inside word, so if it is longer than the \textwidth, just make a line break at that position. There may be a little adjustment to make it right flush. For the details of the line breaking system for Korean, I'll talked to the people in KTUG. Some experts in KTUG will answer how to do that. For ConTeXt, there is a font-kor.tex(by nomos) file which enable to use Korean in ConTeXt. So they know what and how to do. I hope that we find a good solution which is also good for the implementation in MKIV. Thank you again. Best regards, Dalyoung

3 2

modernized and augmented m-r.tex
by Johan Sandblom 08 Dec '08

08 Dec '08

The ConTeXt module for interaction with the statistical programming language R currently does not work with MKIV since buffers are not saved to file. The included file fixes this by calling \savebuffer on the buffer in case \ctxlua is defined (a trick gleaned from a discussion on the LilyPond module a while back). Also, all calls to R used to include a rather annoying proc.time() statement at the end, and a modified R call has fixed this. PATH must contain R or R.exe on Windoze. Should 'texmfstart' still be used for the R calls? A third modification involves being able to call \startRnoecho (which only echoes R output in the ConTeXt file) in addition to \startR (which echoes both input and output) and \startRhidden (which echoes nothing, useful for generating graphics) One further improvement would be to collect the R snippets and run them all at once. That would significantly reduce processing time since the R startup is on the order of a few seconds. However, that is beyond my knowledge of ConTeXt. Regards, Johan -- Johan Sandblom, MD PhD m +46735521477 Sweden "What is wanted is not the will to believe, but the will to find out, which is the exact opposite" - Bertrand Russell

2 2