- ntg-context - NTG Mailing Lists

Re: [NTG-context] basic \cite[]
by Michael Saunders 18 Apr '10

18 Apr '10

Taco: > Try > > \setuppublications[alternative=num] Thank you, but using that I get the same result: \cite[myKey] prints out empty brackets "[]", not "[1]".

4 4

Re: [NTG-context] basic \cite[]
by Michael Saunders 18 Apr '10

18 Apr '10

Taco: > > \placepublications > > Please change the above line to > > \placepublications[criterium=all] Thanks, but that's what I was using already. To be clear, in Mk IV: \usemodule[bib] \setupbibtex[database=myProject] \setuppublications[alternative=num] ... \cite[myKey] ... \placepublications[criterium=all] The references in the back look okay, but at the point where \cite[myKey] occurs, I get empty brackets: "[]", not "[1]".

2 1

basic \cite[]
by Michael Saunders 18 Apr '10

18 Apr '10

I want to be able to write, in my text, \cite[myKey] (where myKey is the key of a record in my .bib file), and have this appear in print as: [<a number>] linked to the bibliograpy page where it (<a number>) occurs. I've been puzzling over bibmod-doc.pdf. I think the solution has to do with the commands \setuppublications and \setupcite, but since bibmod-doc never says what these commands do, it's very difficult. I'm guessing \setuppublications might be able to control what argument I should use in the \cite[] command. I'm guessing \setupcite might control how a citation will be printed in the text. (If this is true, the manual should say so so the reader doesn't have to guess.) One cryptic line tells me: "refcommand the default option for \cite" just like that. Based on this, I'm guessing refcommand=key will let me write things like \cite[myFirstKey]. The manual goes on to clear up the confusion by explaining: "The \cite command has a lot of alternatives, as could be seen above in the setting of ‘refcommand’." That's it---no mention of what \setupcite does. Based on this, I'm hoping that \setupcite[num] will cause the citation to be printed as [<some number>], e.g., [1]. So, I'm using: \usemodule[bib] \setupbibtex[database=myProject] \setuppublications[refcommand=key,alternative=apa,setupinteraction=start,numbering=yes] \setuppublicationlist[] \setupcite[num][] ... \placepublications[criterium=all] The bibliography prints out, but citations appear as empty brackets: "[]". I want them to be numbers linked to the appearance of the same number in the bibliography. There must be a way of doing this?

3 2

Re: [NTG-context] table: vertical distance
by Wolfgang Werners-Lucchini 17 Apr '10

17 Apr '10

> \define[1]\divisionrule > {\dontleavehmode\blap > {\vskip-\strutht > \blackrule[width=\the\dimexpr.5em*#1\relax,height=2\linewidth]}% > \vskip-\lineheight} Ahh! Yes, this helps a lot. Thank you very much! Wolfgang

1 0

table: vertical distance
by Wolfgang Werners-Lucchini 17 Apr '10

17 Apr '10

Hallo, I have to typeset a division and have two diverent solutions but they both have problems. %--------------------------------------------------------------------- \starttext {\setuptables[rulethickness=0.05em,distance=small] \starttable[s0|r|r|r|r|r|r|r|r|r|r|r|r|r|r|r|r|] \NC\NC 1\NC 1\NC 0\NC 0\NC 1\NC 1\NC :\NC 1\NC 1\NC = \NC 1\NC 0\NC 0 \NC 0 \NC 1\NC\AR \NC\NC 1\NC 1\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \DC \DL[2] \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DR \NC\NC \NC 0\NC 0\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \NC\NC \NC 0\NC 0\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \DC\DC \DL[2] \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DR \NC\NC \NC \NC 0\NC 0\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \NC\NC \NC \NC 0\NC 0\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \DC\DC\DC \DL[2] \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DR \NC\NC \NC \NC \NC 0\NC 1\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \NC\NC \NC \NC \NC 0\NC 0\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \DC\DC\DC\DC \DL[2] \DC \DC \DC \DC \DC \DC \DC \DC \DC \DC \DR \NC\NC \NC \NC \NC \NC 1\NC 1\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \NC\NC \NC \NC \NC \NC 1\NC 1\NC \NC \NC \NC \NC \NC \NC \NC \NC \NC\AR \DC\DC\DC\DC \DC \DL[2]\DC \DC \DC \DC \DC \DC \DC \DC \DC \DR \NC\NC\NC\NC\NC\NC\NC 0\NC\NC\NC\NC\NC\NC\NC\NC\NC\NC\AR \stoptable} \setuplines[style=type] \startlines 110011:11=10001 11 -- ~00 ~00 ~-- ~~00 ~~00 ~~-- ~~~01 ~~~00 ~~~-- ~~~~11 ~~~~11 ~~~~-- ~~~~~0 \stoplines \stoptext %--------------------------------------------------------------------- In both examples there is a far to big distance between the lines and the upper digits. But the interline distance as a whole could be smaller. The simulation of a line with '--' in the second example is unsatisfying. Are there some improvments? Or, is there an idea for a better approach? Wolfgang

2 3

code
by R. Bastian 17 Apr '10

17 Apr '10

Hello, how to translate in context the following plain tex: \font\fgras = cmbtt10 {\tt {\obeylines {\fgras def} ra(): \ \ \ \ a = 3 \ \ \ \ b = 4 } } -- René Bastian www.pythoneon.org www.musiques-rb.org http://www.soundsurvey.org.uk/

4 22

lua, footnotes, interaction
by Philipp Gesang 17 Apr '10

17 Apr '10

Good evening all, interaction remains a mystery to me. When tracking things I encountered the following deviation in footnotes: ---8<-------------------------------------------------------------------------- \startluacode track = {} track.preceding = "" function track.simple(arg) context("Last one:\\ {\\bf " .. track.preceding .. "}.\\ " .. "This one:\\ {\\bf " .. arg .. "}") if arg == track.preceding then context("\\ -- matching!") else context("\\ -- not matching!") track.preceding = arg end end \stopluacode \def\track#1{\ctxlua{track.simple("#1")}} \def\foottrack#1{\footnote{\ctxlua{track.simple("#1")}}} \starttext \section{Normal} \track{one}\par \track{two}\par \track{two}\par \track{one}\par \track{one}\par \track{two}\par \track{one}\par \section{In Footnotes} \foottrack{one} \foottrack{two} \foottrack{two} \foottrack{one} \foottrack{one} \foottrack{two} \foottrack{one} \setupinteraction[state=start] \section{In Footnotes, interaction enabled} \footnote{\hrule} \foottrack{one} \foottrack{two} \foottrack{two} \foottrack{one} \foottrack{one} \foottrack{two} \foottrack{one} \stoptext % vim:ft=context ---8<-------------------------------------------------------------------------- I'd naively expect \track#1 to behave identically regardless of interaction. How do I make it interaction-proof, and, if possible, how do I interaction-proof macros in general? Thanks for your efforts, Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

3 5

Treating orphans and widows
by Jan Pohanka 17 Apr '10

17 Apr '10

Hello, could anyone describe me, how to deal with orphans and widows in Context? Now I use \clubpenalty=8000 \widowpenalty=8000 is there any "context way" how to do that? greetings Jan -- Tato zpráva byla vytvořena převratným poštovním klientem Opery: http://www.opera.com/mail/

1 0

Re: [NTG-context] 3D annotations
by Michail Vidiassov 17 Apr '10

17 Apr '10

Dear Hans, I wrote to you > thank you for your latest effort to put u3d support in a working state, but more thanks for more effort, but > May be a more robust way is to read first 3 bytes of the model file, since > "U3D" or "PRC" signature is always there - that can be done instead of > relying on file name extension or only in case it it not "u3d" or "prc". you have implemented reading the file signature, but it is now almost useless, since if a file has extension other but U3D or PRC 3D annotation code will not be called by file inclusion mechanism and "io.readdata" routine is called local subtype, subdata = "U3D", io.readdata(foundname) or "" - what's that? One more point - preview bitmap images in 3D annotations are now disabled since necessary functionality of measuring XForms is missing - please, consider the following workaround. --- lpdf-u3d.lua.org 2010-03-26 18:24:44.000000000 +0300 +++ lpdf-u3d.lua 2010-04-14 14:24:28.000000000 +0400 @@ -17,6 +17,7 @@ local cos, sin, sqrt, pi, atan2, abs = math.cos, math.sin, math.sqrt, math.pi, math.atan2, math.abs local pdfconstant = lpdf.constant +local pdfnumber = lpdf.number local pdfboolean = lpdf.boolean local pdfunicode = lpdf.unicode local pdfdictionary = lpdf.dictionary @@ -62,8 +63,7 @@ local function make3dview(view) - local name = viewname - local name = pdfunicode((view.name ~= "" and name) or "unknown view") + local name = pdfunicode((view.name ~= "" and view.name) or "unknown view") local viewdict = pdfdictionary { Type = pdfconstant("3DView"), @@ -311,9 +311,6 @@ for i=1,#nodes do local node = checkedkey(nodes,i,"table") if node then - local position = checkedkey(node,"position","table") - position = position and #position == 12 and pdfarray(position) - if position then nodelist[#nodelist+1] = pdfdictionary { Type = pdfconstant("3DNode"), N = node.name or ("node_" .. i), -- pdfunicode ? @@ -325,13 +322,18 @@ }, M = position, } + local position = checkedkey(node,"position","table") + position = position and #position == 12 and pdfarray(position) + if position then + nodelist[#nodelist].M = position end end end - viewdict.NR = true viewdict.NA = nodelist end + viewdict.NR = true + return viewdict end @@ -349,19 +351,19 @@ local activationdict = pdfdictionary { TB = pdfboolean(param.toolbar,true), - NP = pdfboolean(param.tree,true), + NP = pdfboolean(param.tree,false), } local stream = streams[label] if not stream then - local subtype, subdata = "U3D", io.readdata(foundname) or "" + local subtype, subdata = "U3D", file.readdata(foundname) or "" if find(subdata,"^PRC") then - subtype == "PRC" + subtype = "PRC" elseif find(subdata,"^U3D") then - subtype == "U3D" + subtype = "U3D" elseif file.extname(foundname) == "prc" then - subtype == "PRC" + subtype = "PRC" end local attr = pdfdictionary { @@ -423,12 +425,35 @@ local ref = stored_pr[tag] if not ref then -- weird, has to be a /Form and not an /Image so we need a wrap = true key - -- local figure = img.immediatewrite { filename = preview, width = width, height = height } - local figure = img.immediatewrite { stream = ".5 .75 .75 rg 0 0 20 10 re f", bbox = {0,0,20,10 } } + local figure = img.immediatewrite { filename = preview, width = width, height = height } + -- local figure = img.immediatewrite { stream = ".5 .75 .75 rg 0 0 20 10 re f", bbox = {0,0,20,10 } } ref = figure.objnum stored_pr[tag] = ref end - annot.AP = ref and pdfdictionary { N = pdfreference(ref) } + if ref then + local pw = pdfdictionary { + Type = pdfconstant("XObject"), + Subtype = pdfconstant("Form"), + FormType = pdfnumber(1), + BBox = pdfarray { pdfnumber(0), pdfnumber(0), pdfnumber(factor*width), pdfnumber(factor*height) }, + Matrix = pdfarray { pdfnumber(1), pdfnumber(0), pdfnumber(0), pdfnumber(1), pdfnumber(0), pdfnumber(0) }, + Resources = pdfdictionary { + XObject = pdfdictionary { + IM = pdfreference(ref) + } + }, + ExtGState = pdfdictionary { + GS = pdfdictionary { + Type = pdfconstant("ExtGState"), + CA = pdfnumber(1), + ca = pdfnumber(1) + } + }, + ProcSet = pdfarray { pdfconstant("PDF"), pdfconstant("ImageC") }, + } + local pwd = pdf.immediateobj("stream",format("q /GS gs %s 0 0 %s 0 0 cm /IM Do Q",factor*width,factor*height),pw()) + annot.AP = pdfdictionary { N = pdfreference(pwd) } + end return annot, figure, ref else activationdict.A = pdfconstant("PV") Also I try to remind you AGAIN and AGAIN about pdfboolean problem in lpdf-ini.lua (old code is not OK if b is "false" and default is "true") local function pdfboolean(b,default) - if ((type(b) == "boolean") and b) or default then - return p_true + if type(b) ~= "boolean" then + if default then + return p_true + else + return p_false + end else - return p_false + if b then + return p_true + else + return p_false + end end end Sincerely, Michail PS. And a great palliative way to deal with 3D annotations is via attaching a 3D PDF file made with LaTeX (by Asymptote, for example). But while your method of answering my messages in lua works OK for new code (updating minimals and making a diff with old code is not harder than checking e-mail inbox - "Your morning patch, sir!" ;), I can not deduce from existing sea of ConTeXt code the status of file attachments support.

1 0

thinrules
by Hans van der Meer 16 Apr '10

16 Apr '10

\thinrules disappear when then are the lone item and I can make them appear only by typeing somthing behind/before. However, I would to force a thin rule anyway, even if there is no surrounding text. How? Hans van der Meer

2 1