- ntg-context - Mailing Lists

Errors with MacTeX/TeXLive installation
by Grant W. Petty 02 Aug '10

02 Aug '10

I am trying out ConTeXt for the very first time, hoping to assess whether it's worth re-tooling from LaTeX for authoring scientific textbooks. I am using a fresh installation of TeX Live 2009 (installed via MacTex on a MacBook running Mac OS X 10.6), and I'm trying to process a sample file I downloaded from one of the ConTeXt web pages. Unfortunately, the process generates a couple of cryptic warnings ("Lua binary way out of date") and a fatal error ("can't find ...dcc/formats/cont-en.luc"). I wonder if someone can examine the input file and the log file (both attached) to help me understand what I have to do to clean things up and, if possible, why the TeX Live ConTeXt configuration doesn't work correctly "right out of the box" to begin with. Thanks, Grant

3 4

new current
by Hans Hagen 02 Aug '10

02 Aug '10

Hi, I uploaded a current release that matches luatex 0.61 beta (released a few days ago). The release notes will follow. Apart from a couple of fixes in mkiv the main additions are tagged pdf and the possibility to include pages from pdf documents with hyperlinks which is controlled by the 'interaction' key (given that interaction is enabled). \externalfigure[file.pdf][page=1,scale=700,frame=on,interaction=yes] This is experimental code and it will be extended in the future. Also more control will provided. Future releases will also deal with layers in embedded images (all within reasonable bounds). The current code still supports older mplib although so this current might work with alpha 0.61 versions. We expect a next beta if luatex in a couple of weeks so there will for sure be beta releases of context in the meantime. 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 -----------------------------------------------------------------

8 19

CSV parser do not processed macro.
by Jaroslav Hajtmar 01 Aug '10

01 Aug '10

Hello all, to solve my problem I need to find why my function ParseCSVdata incorrectly parses strings stored in a macro. It's including possibly the reason why do not work properly Mojca database module as I wrote in a recent mail. It seems to enter a string function, which is not my function to find a separator. Thanx Jaroslav Here is my minimal example: \startluacode function ParseCSVdata(string2parse, separator, leftdelimiter, rightdelimiter) -- Funkce pro "rozparsování" jednotlivých záznamů (řádků) CSV tabulky -- Vstupní textový řetězec (načtený řádek) je v místech výskytu separátoru "rozsekán" na jednotlivá pole -- Jediný povinný vstupní parametr je 'string2parse'. Při nenastavení zbývajících tří parametrů se jako separátor a oddělovače použijí buď globální proměnné Sep, Ld a Rd nebo se použijí defaultní hodnoty -- Výstupem je pole oddělených řetězců -- Když nejsou globální proměnné Sep, Ld a Rd nastaveny uživatelem, nastaví se na defaultní hodnoty. Uživatel si může defaultní hodnoty libovolně změnit podle toho, jaké hodnoty používá ve svých aplikacích nejčastěji Sep = (Sep == nil) and UserCSVSeparator or Sep -- Pokud není glob. neznámá Sep nastavena, použije se defaultní hodnota ';' (středník). Ld = (Ld == nil) and UserCSVLeftDelimiter or Ld -- Pokud není glob. neznámá Ld (left delimiter) nastavena, použije se defaultní hodnota '' (prázdný řetězec) Rd = (Rd == nil) and UserCSVRightDelimiter or Rd -- Pokud není glob. neznámá Rd (right delimiter) nastavena, použije se defaultní hodnota '' (prázdný řetězec) -- Nastavení hodnot parametrů, které nejsou při volání funkce nastaveny tj. při volání funkce ParseCSVdata(string2parse) s pouze jedním parametrem local separator = (separator == nil) and Sep or separator -- při nenastavení separátoru se použije local leftdelimiter = (leftdelimiter == nil) and Ld or leftdelimiter local rightdelimiter = (rightdelimiter == nil) and Rd or rightdelimiter -- A jdeme na vlastní zpracování řetězce ... local result={} if leftdelimiter ~= '' and rightdelimiter ~= '' then -- Když jsou položky v řádku vymezeny levým i pravým delimiterem (tj. jakousi závorkou) např. "pole1";"pole2" nebo {pole1};{pole2} .. atd. string.gsub(string2parse, leftdelimiter.."(.-)"..rightdelimiter, function(a) table.insert(result,a) end ) -- Je vidět, že v tomto případě ani nezáleží na separátoru, jednotlivé uzávorkované řetězce se od sebe oddělí else -- Když je pouze separátor polí bez vymezujících znaků - delimiterů (tento případ bohužel neumožňuje použití separátoru jako samostatného znaku v nějakém poli ) result=string.split(string2parse,separator) -- pak stačí vstupní řetezec jen "vysplitovat" tj. rozsekat na samostatné části end return result -- Funkce vrátí pole result obsahující oddělená jednotlivá pole řádkového CSV záznamu end function pars(inppar) tex.sprint("input parametr (string): "..inppar.."\\par") CSVLine=ParseCSVdata(inppar,',','','') tex.print(table.maxn(CSVLine).." item(s) \\par") for i = 1, table.maxn(CSVLine) do tex.sprint(i..". "..CSVLine[i].."\\par") end tex.sprint("\\blank[big]") end \stopluacode \def\printaction{x,y,z,u,v} \starttext \startluacode pars("a,b,c,d") pars("\\printaction") \stopluacode \stoptext

2 1

Expansion of TeX macros inside the Lua function
by Jaroslav Hajtmar 01 Aug '10

01 Aug '10

I came across an interesting issue (for me), which is probably the beginner, but accompanied me for a long time. The problem is probably that I do not understand very well the principles of operation LuaTeX and while I want to do more complex things. I think many beginners will love it when someone indicate solutions. My problem is that I need in my complex application, evaluate parameters of Lua functions, which are a TeX macros (respectively their expanded contents). I did not discover the possibility of expansion of TeX macros, which is a parameter Lua function. Here are three examples in which I demonstrate the problem. 1. In first example is function parameter a text string. \ctxlua{pars('a,b,c,d,e')} Everything works as expected - evaluation of parameter was carried out OK - comma separator was found and replaced. 2. In second example is a function parameter a TeX macro \printaction. Macro expanded before entering the function. Everything works as expected too - comma separator is found and replaced: \ctxlua{pars('\printaction')} 3. The third example of my most interesting. Function parameter in example is a TeX macro \printaction which not expanded, respectively expanded only when I printing it to TeX. Parameter of function is string "\printaction" in which it is futile to look for a comma separator. Comma not be found, although the content of macro face that is so. \ctxlua{pars('\\printaction')} Is there a possibility for this case, as in some way to save to Lua variable content of macro (of course expanded)? I note that this example is important for me and I would like there to be a Lua function (eg "expandtostring"), which expanded a TeX macro into variable until inside function Lua. I hope the my example (with comments) will be comprehensible and I apologize if the solution is too trivial. I searched dozens of examples, but I come across something similar. Thanx very much - Jaroslav Here is example: \startluacode function pars(inppar) strpar=tostring(inppar) -- here I need a function "expandtostring(inppar)" gsubstr=string.gsub(strpar, ',', ';') tex.print("Input parametr (string or macro): ") tex.write(inppar) tex.print("\\par") tex.print("Content of string (macro): "..strpar) -- There will always be expansion tex.print("\\par") tex.print("Length string (macro): "..string.len(inppar).."\\par") tex.print("Length of content : "..string.len(strpar).."\\par") tex.print("Occurrence of the commma separator: "..gsubstr.."\\par") end \stopluacode \def\printaction{x,y,z} \starttext Example 1) Function parameter in first example is a text string. Everything works as expected - comma separator is found and replaced: \ctxlua{pars('a,b,c,d,e')} \blank[big] Example 2) Function parameter in second example is a TeX macro \backslash printaction which expanded before entering the function. Everything works as expected too - comma separator is found and replaced: \ctxlua{pars('\printaction')} \blank[big] Example 3) The third example of my most interesting. Function parameter in example is a TeX macro \backslash printaction which not expanded, respectively expanded only when I printing it to TeX. Parameter of function is still string "\backslash printaction" in which it is futile to look for a comma separator. Comma not be found, although the content of macro face that is so. Is there a possibility for this case, as in some way to save to Lua variable content of macro (of course expanded)? \ctxlua{pars('\\printaction')} \stoptext

2 2

part problems
by Henning Hraban Ramm 01 Aug '10

01 Aug '10

(MkIV, latest beta) I'm trying to get a title page for book parts: \def\FPart#1#2{#2} \setupheads [align=right, tolerance=verytolerant, before=\nohyphen\startlinecorrection, after=\stoplinecorrection, number=no] \setuphead[part][command=\FPart, page=right, style={\bfc}] \part{My First Part} But the page is empty, also without "command", also with a suitable "textcommand", also without "style". Next problem: In my ToC I get "Part My First Part". (Or "Part 1 My First Part", if I enable the number.) How can I suppress that piece of text ("Part")? Generally, what's the best approach to get a fixed font size for some titles, e.g. the part title should have 64 pt. Should I use \setuphead[part][before={\switchtobodyfont[64pt]}] ? Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

5 9

tex in context
by R. Bastian 01 Aug '10

01 Aug '10

Hello, is there a way to insert plain tex code in context source ? example: \startTEX \font\ttbold=cmbtt10 at 12pt .... {\ttbold texte monospace en gras} ... \stopTEX -- René Bastian www.pythoneon.org

2 2

CLD Documents
by Martin 'golodhrim' Scholz 01 Aug '10

01 Aug '10

Hi Hans, I like the way how one can write ConTeXt-Lua-Documents, works really good, but I tried to load a module but there seems to be no solution for this included. Is there a way to include this in a CLD-Document? Thanks -- --- Martin 'golodhrim' Scholz Auf dem Sattler 4 34516 Ederbringhausen Phone: +49 6454 799623 mobile: +49 176 63301749 Fax: +49 6454 e-Mail: scholz.m82(a)googlemail.com BOFH Excuse #260: We're upgrading /dev/null

2 1

Passing info from MetaPost to TeX
by Oliver Buerschaper 01 Aug '10

01 Aug '10

Dear all, is it possible to pass data from MetaPost back to TeX? This would be similar in spirit to, say, the MetaPost variable BodyFontSize that contains data from the TeX surrounding. Just the other way round. Best, Oliver Buerschaper

3 7

Re: [NTG-context] Setting up protrusion, side-effects
by Martin Althoff 31 Jul '10

31 Jul '10

I hate to pick up on this again, but... The basic Palatino, together with protrusion and small caps is causing issues. Essentially horizontal placing of the characters fails (see previous PDF). In the example below, I can reliably cause the effect by commenting out (or not) the line with the \sc. This effect shows up the my "real" files. While trying to find the trigger by culling down the files, for a moment I could reliably (!) turn the effect on and off with the line %\setupfootertexts[chapter][pagenumber] and not changing the \sc lines. Weird side effect? Sorry, I can't reproduce that one anymore. One way to reduce, but not prevent the effect, is if more plain text is output before using \sc. eg by adding an \input tufte beforehand. But once the text after the \sc is a bit longer ie. 10x tufte the effect will show again. Gut feeling: successive and cumulative rounding errors. Question: Am I tripping over "side effects"? Is using SmallCaps a bad idea when using protrusion? It just feels odd that something like this would be so uncontrollable. Particularly since the palatino font is from the TexGyre set (so close to home) Thanks for thoughts! Martin \definefontfeature [default][default][protrusion=quality,expansion=quality] \setupalign[hz,hanging] %\setupfooter[text][before=\hairline,leftwidth=.85\textwidth,style=\tfx] %\setupfootertexts[chapter][pagenumber] %\usetypescript[palatino] \setupbodyfont[palatino,12pt] \starttext %\input tufte {\sc Erster Teil} \input tufte \stoptext > Fonts are sometimes special and when ypu load a font it's > setting (e.g. ligatures, protrusion etc.) are frozen. To change the > settings you need \definefontfeature before \setupbodyfont, > Wolfgang

2 4

footnote missing
by Peter Münster 31 Jul '10

31 Jul '10

Hello, Example: \starttext \startlocalfootnotes AAA\footnote{aaa} \placelocalfootnotes \stoplocalfootnotes BBB\footnote{bbb} \startlocalfootnotes CCC\footnote{ccc} % footnote missing \placelocalfootnotes \stoplocalfootnotes \stoptext Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/

1 1