July 2010 - ntg-context - NTG Mailing Lists

vim syntax highlighting in MKIV
by Martin 'golodhrim' Scholz 06 Sep '10

06 Sep '10

Hi Hans, Mojca, Aditya and List, just tried to use the vim Syntax Highlighting module in ConTeXt MKIV, but if running the documents complains it searches a file called filename-vimsyntax.tmp-vimsyntax.tmp sure that file not exists but there is a file called filename-vimsyntax.tmp is there a way to do a workaround so that the vim Syntaxhighlighting module would work in MKIV or does it need to be rewriten completedly? Greetings -- --- 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 Think sideways! -- Ed De Bono

6 12

Placing footnotes in right margin en bloc at bottom of page
by Elias Oltmanns 10 Aug '10

10 Aug '10

Hi there, not being a ConTeXt user myself, I have been advised on the tex-d-l list of the German TUG that a certain problem could possibly be solved more easily in ConTeXt than in LaTeX. So, here is what I'm trying to achieve: The numerous but short footnotes of a document shall be placed in the right margin rather than below the main text area. Additionally, though, the footnotes should not be placed near the call up (similar to what \marginpar does), but type set en bloc at the bottom of the page. In other words, the main text area should have fixed margins all round across all pages and the footnotes should be printed in a small rectangular block beside the main text area such that the height of this block varies according to the number of footnotes on the page, but the block is always flushed to the bottom of the page. You'll find an ascii art illustration below. Is such a layout feasible in ConTeXt without too much hassle at all? Regards, Elias ================================ = | = = | = = | = = M A I N | = = | = = T E X T | = = | = = A R E A | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = | = = |-----= = |foot-= = |notes= ================================

4 12

Re: [NTG-context] how to jump to figure and return to the original postion?
by dalyoung 09 Aug '10

09 Aug '10

Dear Hans, Thank you for a nice solution. It is really cool! I always wonder what is the limit of ConTeXt. But I think that I am using very small portion of it. Here I'd like to ask one more thing. I downloaded the example of "Euro symbol" animation. Both button "here" and "restart" worked fine. However, a new pdf file of Euro symbol animation which was madden by recompiling the source not properly working in my macbook. "here" button works fine while "restart" lost the position.(just blank window is appeared) I tried a similar step by step drawing and got the same situation. Is it a problem in my machine only? Mac OSX 10.6.4 ConTeXt ver: 2010.06.23 12:45 MKIV fmt: 2010.7.18 int: english/english - this is luatex, version beta-0.60.2-2010070117 Thank you for your help. Best regards, Dalyoung

2 1

\startcolumns ... \stopcolumns
by Horacio Suarez 06 Aug '10

06 Aug '10

Hello: After \startcolumns ... \stopcolumns there a big blank space. This sample shows it. %%%%%%%%% \starttext \startcolumns \input tufte \input tufte \input tufte \stopcolumns {\bf This should appear in the first page, below {\em tufte,} there is enough room.} \stoptext %%%%%%%%% why the last line jumps to a new page? Thankyou very much. -------------------- Horacio Suarez

2 2

Palatino Linotype under MKIV
by Paul Schalck 06 Aug '10

06 Aug '10

Hi, I'm trying to use the full glyph range of the Palatino Linotype font shipped with XP (version 1.40; significantly different from the Windows 7 one) under MKIV. Everything works fine (oldstyle figures, sups for instance), except that the small cap "i" character has a dot whereas it shouldn't. Here's a test file. The result, produced on WinXP / ConTeXt beta 2010-06-23, is attached. \definefontfeature[palatinolt-default][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality] \definefontfeature[palatinolt-smcp][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,smcp=yes,onum=yes] \definefontfeature[palatinolt-sups][mode=node,script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,sups=yes] \starttypescript[serif][palatinolt][name] \usetypescript[serif][fallback] \definefontsynonym[Serif][file:pala.ttf][features=palatinolt-default] \definefontsynonym[SerifBold][file:palab.ttf][features=palatinolt-default] \definefontsynonym[SerifItalic][file:palai.ttf][features=palatinolt-default] \definefontsynonym[SerifBoldItalic][file:palabi.ttf][features=palatinolt-default] \definefontsynonym[SerifCaps][file:pala.ttf][features=palatinolt-smcp] \stoptypescript \definetypeface[palatinolt][rm][serif][palatinolt][default] \setupbodyfont[palatinolt] \enableprotruding\setuppagenumbering[location=] \starttext {\sc \input knuth } \stoptext As far as I can see, it has to do with the messy name list of the glyphs. Both the normal small cap i and the small cap dotted i are named "i.sc", but the wrong one is picked when the smcp feature is activated. Moreover, the small cap glyphs have no unicode numbers in this font, so I cannot pick them manually with \char"XXXX or even with \charXXXXX. Any ideas how I can get the right dottless i?

5 10

4th ConTeXt Meeting, update
by Jano Kula 04 Aug '10

04 Aug '10

Hello to everybody! There are few weeks left till the 4th ConTeXt Meeting on September 13-18, 2010 in Brejlov, Czech Republic. We have collected interesting talks and tutorials (25+) on ConTeXt, LuaTeX, Lua, fonts, OpenType math, Metapost and more: http://meeting.contextgarden.net/2010/abstracts.shtml We are working on the preliminary programme and other things to make the meeting unforgettable. The highlights of the accompanying programme are delicious cuisine, excellent beer and lovely countryside. Many friends from the ConTeXt list are coming, so we are going to have wonderful time with many interesting talks -- formal and informal: great source of encouragement and inspiration. After the deadline, the registration for the meeting is still open until we reach the available capacity. We hope you are having a good time and we are looking forward to meeting you in Brejlov. Best regards, Jano Kula on behalf of the organizing committee http://meeting.contextgarden.net/2010/

9 20

no indent after blank
by Henning Hraban Ramm 03 Aug '10

03 Aug '10

(latest beta MkIV) With \setupindenting[yes, medium] there shouldn't be an indent after a \blank IMO. How can I suppress it? Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

4 10

MTXrun | error, no format found with name: cont-en, aborting
by Paul Dostert 03 Aug '10

03 Aug '10

I'm a moderate context user (finished a 100 page math text recently) and haven't had too many problems except for downloading an occasional beta which has an issue or two. My book compiles just fine on my office computer, but I installed context and get compilation errors on my home laptop (a windows 7 box). I've been able to work through all other problems with context up to this point, sometimes waiting a day or two until someone uploaded a fix in the new beta, but for some reason I've gotten stuck on this one. I installed context via: - Download of context-setup-mswin.zip - unzip to c:\context - run of first-setup.bat (with no args, and same happens with --context=current) - After running, I go to the tex/ directory and run the setuptex.bat - Go back to c:\context and run a test file with just \starttext TEST \stoptext using "context test.tex" - I get the error "MTXrun | error, no format found with name: cont-en, aborting" I also tried using TeXworks, using compilation using texmfstart.exe and texexec. That compiled the original test.tex, but refuses to compile any .tex code with metapost. What, in most cases, does the "MTXrun | error, no format found with name: cont-en, aborting" error indicate? I know that odds are I missed something stupid, but just can't figure it out this time. Thank you for your help and your time. Paul

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