- ntg-context - NTG Mailing Lists

duplex printing
by Pablo Rodriguez 24 Dec '15

24 Dec '15

Dear list, for those interested, Hans has implemented in latest beta from 2015.12.22 10:50 values for duplex printing in the option key from \setupinteractionscreen. With this commit, it is possible to disable duplex printing in printers which have it set by default, or enable portrait or landscape duplex printing (no matter which the defaults are). More information at http://wiki.contextgarden.net/PDF_Print_Options. I must admit it is formatted like crap. But I had to write it in Markdown and convert it to mediawiki using pandoc. I hope you enjoy this feature, Pablo -- http://www.ousia.tk

1 0

strange output in math display mode
by Jeong Dal 23 Dec '15

23 Dec '15

Dear Hans, After updating the minimal, I got a strange output of math display mode. Would you please check it? Here is an example. Best regards, Thank you. Dalyoung %%%%%%%%%%%% \starttext Here is a strange output of math formula. It is displayed correctly in text line, but is displayed strangely in math display mode. \blank Here is a correct output in text line. $\int_0^t B(s)\ dB(s) = \frac{1}{2} B^2(t) - \frac{1}{2} t.$ \blank But in the output of display mode, the location of the sub- super-script of the integral sign is not normal and the output of \type{ \frac{1}{2} B^2(t)} is wrong. \startformula \int_0^t B(s)\ dB(s) = \frac{1}{2} B^2(t) - \frac{1}{2} t. \stopformula \stoptext %%%%%%%%%%%%%%

6 10

inter-word space in bibliographies
by Alan Bowen 23 Dec '15

23 Dec '15

The appended code is supposed to allow reduction of the inter-word spacing in my bibliographies but it does not. Adjusting the \spaceskip in the setups for [tightspace] does not seem to make any difference. Any suggestions will be most welcome. I am using the latest beta (ConTeXt ver: 2015.11.19 19:13 MKIV beta with LuaTeX 0.85) Alan \startsetups[tightspace] \spaceskip .7\interwordspace plus .5\interwordstretch minus \interwordshrink \stopsetups \def\dostartbibitem[#1]{\startBibItem[title={#1},reference={#1}]} \def\startbibitem{\dosingleempty\dostartbibitem} \def\stopbibitem{\stopBibItem} \definedescription[BibItem][ width=broad, margin=1.5pc, indenting={no}, indentnext=no, alternative=hanging, hang=1, headcommand=\gobbleoneargument, align=right, before={\directsetup{tightspace}\bgroup\language[packed]}, after={\egroup}, ] \starttext Martin, J. 1956. \emph{Histoire du texte des phénomènes d’Aratos}. Paris. \startbibitem[Martin 1956] Martin, J. 1956. \emph{Histoire du texte des phénomènes d’Aratos}. Paris. \stopbibitem \stoptext

2 2

behavior of \vfill has changed in latest beta
by Thomas A. Schmitz 21 Dec '15

21 Dec '15

Hi, the behavior of \vfill has changed in the latest beta. In some of my setups, I used code like this to produce vertically centered content: \starttext \null\vfill vertically centered? \vfill\null \stoptext This works with the beta of 2015.11.19 19:13, but no longer with 2015.12.21 12:16. Not sure if intended, side effect, or bug? Thomas

3 4

beta
by Hans Hagen 21 Dec '15

21 Dec '15

Hi, A few words on luatex 0.87 and the beta. As we're progressing to the first stable luatex release (stable in the sense that functionality will become stable, after 1.0 we will continue anyway) a couple of changes take place. And as context is the primary testbed it gets adapted too. (1) Luatex functionality gets finalized which means that some gets removed, some adapted and some extended. The last months not much changed in context in terms of functionality but adapting to luatex canhave temporary side effects as you might have noticed. (2) Luatex functionality that was already present but not yet used gets applied and again this should normally not have side effects. It might result in new (or extended) features. (3) Context code gets optimized but I must admit that there is not much room left for that. Some new luatex functionality makes it possible to code a bit less redundant (handy for tracing). That can result in left over bit and pieces, typos etc. Lucky us we have Wolfgang to check that. (4) Performance should be a little better but also depends on the source and quality of styles. If you encounter bottlenecks and can prove that it's due to poor context core performance I can have a look at it. (5) The new font loader is now used and still can have some issues but in general it behaves okay. (6) There are still some mechanisms that need to be mkiv'd. For instance I'm looking at columnsets. Some of the oldest code (early luatex) probably needs to be checked. 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 -----------------------------------------------------------------

1 0

Plot using pgfplots: order of appearance of two simple plots
by Procházka Lukáš Ing. - Pontex s. r. o. 21 Dec '15

21 Dec '15

Hello, I'm just starting with pgfplots library. I have two plots, one being filled: ---- \usemodule[pgfplots] \starttext \starttikzpicture \startaxis[legend entries={Sin,Cos}] \addplot+[mark=none] {sin(deg(x))}; \addplot+[mark=none,fill]{cos(deg(x))}; \stopaxis \stoptikzpicture \stoptext ---- The problem is that the latter plot hides the former as they appear in the order they are defined. A solution would be to change the order - to swap plot "Sin" and "Cos". But also I need to keep the order in which plots appear in the legend - it's important to keep "Sin" followed by "Cos"; I'm looking for a way to set the order of plots, something like \addplot+[mark=none,order=2] {sin(deg(x))}; \addplot+[mark=none,order=1] {sin(deg(x))}; or \addplot+[mark=none,z=2] {sin(deg(x))}; \addplot+[mark=none,z=1] {sin(deg(x))}; Although I'm having pgfplots.pdf ("Package PGFPLOTS manual", 20. 10. 2013) open, I cannot find a solution. Would anyone more experienced have an idea? Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

2 2

Bug in table ?
by Christian Prim 21 Dec '15

21 Dec '15

Dear list with the latest context I get wrong alignment in table. MWE: (not so minimal, it's a snippet of my document) \setuppapersize[A5][A5] \setuplayout[location=middle, marking=on, topspace=1.5cm, margin=1cm, headspace=0cm, header=0cm, headerdistance=0.0cm, footer=1cm, %bottomspace=1cm, width=fit, height=fit] \setupbodyfont[palatino,10pt] \definetabletemplate[fosa][s0|xp(3.5cm)|lw(0.7cm)m|xp(5cm)s2|lw(2.5cm)m|] \starttext \starttable[fosa] \NC Kräftegleichgewicht \NC\Use3[p(8cm)]{Ein Körper ist im Kräftegleichgewicht, wenn die resultierende Kraft $\vec{F}_{\rm res}$ Null ist.}\NC\AR \MR \NC Drehmoment \NC\Use2[lM]{M=Fr} \NC [M]=\unit{1 Newton meter}\NC\AR \NC \NC F \NC Kraft ($\perp$\ zur DA) \NC [F]=\unit{1 Newton}\NC\AR \NC \NC r \NC Kraftarm (Abstand DA – Wirkungslinie) \NC [r]=\unit{1 meter}\NC\AR \MR \NC Momenten-\crlf gleichgewicht \NC\Use3[lM]{\sum M_{\rm rechtsdrehend}=\sum M_{\rm linksdrehend}}\NC\AR \MR \NC Gleichgewichtsarten \NC\Use3[p(8cm)]{stabil, labil, indifferent}\NC\AR \MR \NC Hebelgesetz \NC\Use3[lM]{F_1 r_1 = F_2 r_2}\NC\AR \NC \NC r_i \NC Kraftarme \NC [r_i]=\unit{1 meter} \NC\AR \MR \stoptable \stoptext What I got before latest beta: old.pdf What I get with new beta (only snippet): new.pdf The misalignment is visible. I know table is deprecated. But I couldn't get xtable to baseline align two different cells with display math in the same row. MWE: \starttext \startxtable[frame=off] \startxrow \startxcell[width=5cm] \m{\displaystyle \gamma=\frac{1}{\sqrt{1-\left (\frac{v}{c}\right )^2}}}\stopxcell \startxcell[width=4cm] Reaktionsprinzip\stopxcell \stopxrow \stopxtable \stoptext \gamma isn't aligned with the text "Reaktionsprinzip". Please tell me what I have to change in table or what table-environment I have to use to get the desired output. Thanks Christian

2 2

[fontloader/old] mixed substitution / ligatures feature
by Philipp Gesang 20 Dec '15

20 Dec '15

Hi Hans, in the old loader, defining a feature containing mixed ligature / substitution causes a crash. Here’s an example: \enabletrackers [otf.loading] \startluacode fonts.handlers.otf.addfeature ("dunno", { { type = "substitution", data = { [0x0022] = 0x201D }, prepend = true, }, { type = "ligature", data = { [0x2013] = {0x002D, 0x002D} }, prepend = true, }, }) fonts.handlers.otf.features.register { name = "dunno", description = "bug demo", } \stopluacode \definefontfeature [myfeat] [default] [dunno=yes,liga=yes,mode=node] \definefont [somefont] [file:cmunrm.otf*myfeat] \starttext \somefont foo bar " baz \stoptext This crashes in font-otn on account of a number being indexed. This used to work -- anything that can be done about it? Best, Philipp

2 2

Re: [NTG-context] Synchronize ERROR: unknown node type 12
by Akira Kakuto 20 Dec '15

20 Dec '15

>>> I have updated >>> web2c/synctexdir/synctex-luatex.h >>> in the TeX Live SVN to support synctex in beta-0.87.0. > > The latest beta-0.87.0 binaries for win32 and win64 support > synctex. For the other platforms, it was too late for the > released beta-0.87.0 sources. SyncTeX will be supported in beta-0.87.1 or later ones. I will revert win32 and win64 binaries of beta-0.87.0 in which synctex is not supported for consistency with other platforms. Thanks, Akira

1 0

Re: [NTG-context] Synchronize ERROR: unknown node type 12
by Akira Kakuto 20 Dec '15

20 Dec '15

> Will this update also appear in the ConTeXt standalone version? > > Alan > > On Sun, Dec 20, 2015 at 10:30 AM, Akira Kakuto <kakuto at fuk.kindai.ac.jp> > wrote: > ... ... >> >> I have updated >> web2c/synctexdir/synctex-luatex.h >> in the TeX Live SVN to support synctex in beta-0.87.0. The latest beta-0.87.0 binaries for win32 and win64 support synctex. For the other platforms, it was too late for the released beta-0.87.0 sources. Thanks, Akira

1 0