- ntg-context - NTG Mailing Lists

\date in LMTX
by Aditya Mahajan 18 Aug '19

18 Aug '19

Hi, There is a bug with \date in LMTX. \starttext \date[d=10] \stoptext does not change the date. Works okay in MKIV. Thanks, Aditya

3 2

Re: [NTG-context] \setupcolumnsetlines does not work
by Sytse Knypstra 17 Aug '19

17 Aug '19

Wolfgang wrote: > The settings for the second columnset work when the first columnset goes over of two or more pages. Thank you, now I understand the mechanism: only if the first columnset extends to more than one page, the next \setupcolumnsetlines will work properly. Is this a bug or a feature? If it is a feature, what is the idea behind it? Sytse

1 0

Re: [NTG-context] \setupcolumnsetlines does not work
by Sytse Knypstra 17 Aug '19

17 Aug '19

Thank you, Denis and Wolfgang. Wolfgang, your sentence > No, you set relative numbers (I checked it) but the first columnset > environment ends on the third page because you leave just enough > space on the second page to fit the text which produces an empty > third page. is not clear to me. If \setupcolumnsetlines has to be specified before \starttext and if the second parameter denotes the absolute page number of the column to be limited, then the following example still does not work correctly for the second page (ouput consists of two pages). \definecolumnset[Two][n=2]  \setupcolumnsetlines[Two][1][1][9]  \setupcolumnsetlines[Two][2][1][9]  \starttext   \startcolumnset[Two]  \input knuth   \stopcolumnset   \startcolumnset[Two]   \input knuth   \stopcolumnset  \stoptext Sytse > Op 17 augustus 2019 om 15:14 schreef Denis Maier <maier.de(a)gmail.com>: > > > Ok, have tried it now. No change ... > > Am Sa., 17. Aug. 2019 um 13:33 Uhr schrieb Denis Maier <maier.de(a)gmail.com>: > > > Also, what about \setupcolumnsetlines[Two][2][1][9]? > > > > Denis Maier <maier.de(a)gmail.com> schrieb am Sa., 17. Aug. 2019, 13:32: > > > >> If I am remembering correctly, the documentation has \setupcolumnsetlines > >> before \starttext. > >> > >> Sytse Knypstra <sytse.knypstra(a)home.nl> schrieb am Sa., 17. Aug. 2019, > >> 12:59: > >> > >>> In an effort to balance columns in a columnset layout, I found that in > >>> the following minimal example this effect is not obtained. > >>> After commenting out the first three lines after \starttext the result > >>> is ok. > >>> I am wondering what I overlooked this time. > >>> > >>> \definecolumnset[Two][n=2] > >>> \starttext > >>> \startcolumnset[Two] > >>> \input knuth > >>> \stopcolumnset > >>> \page > >>> \setupcolumnsetlines[Two][1][1][9] > >>> \startcolumnset[Two] > >>> \input knuth > >>> \stopcolumnset > >>> \stoptext > >>> > >>> Thank you for your suggestions, > >>> > >>> Sytse Knypstra > >>> > >>> ___________________________________________________________________________________ > >>> If your question is of interest to others as well, please add an entry > >>> to the Wiki! > >>> > >>> maillist : ntg-context(a)ntg.nl / > >>> http://www.ntg.nl/mailman/listinfo/ntg-context > >>> webpage : http://www.pragma-ade.nl / http://context.aanhet.net > >>> archive : https://bitbucket.org/phg/context-mirror/commits/ > >>> wiki : http://contextgarden.net > >>> > >>> ___________________________________________________________________________________ > >>> > >> > Op 17 augustus 2019 om 15:50 schreef Denis Maier <maier.de(a)gmail.com>: > > > This here works for the first columnset, but not for the second one: > > ================================= > \usemodule[newcolumnsets] > > \definecolumnset[One][n=2] > > \setupcolumnsetlines[One][1][1][9] > \setupcolumnsetlines[One][1][2][9] > \setupcolumnsetlines[One][2][1][9] > \setupcolumnsetlines[One][2][2][9] > > \definecolumnset[Two][n=2] > \setupcolumnsetlines[Two][1][1][9] > \setupcolumnsetlines[Two][1][2][9] > \setupcolumnsetlines[Two][2][1][9] > \setupcolumnsetlines[Two][2][2][9] > > \starttext > \startcolumnset[One] > \input knuth > > \input knuth > \stopcolumnset > > \startcolumnset[Two] > \input knuth > > \input knuth > \stopcolumnset > \stoptext > =================================== > > Am Sa., 17. Aug. 2019 um 15:14 Uhr schrieb Denis Maier <maier.de(a)gmail.com>: > > > Ok, have tried it now. No change ... > > > > Am Sa., 17. Aug. 2019 um 13:33 Uhr schrieb Denis Maier <maier.de(a)gmail.com > > >: > > > >> Also, what about \setupcolumnsetlines[Two][2][1][9]? > >> > >> Denis Maier <maier.de(a)gmail.com> schrieb am Sa., 17. Aug. 2019, 13:32: > >> > >>> If I am remembering correctly, the documentation has > >>> \setupcolumnsetlines before \starttext. > >>> > >>> Sytse Knypstra <sytse.knypstra(a)home.nl> schrieb am Sa., 17. Aug. 2019, > >>> 12:59: > >>> > >>>> In an effort to balance columns in a columnset layout, I found that in > >>>> the following minimal example this effect is not obtained. > >>>> After commenting out the first three lines after \starttext the result > >>>> is ok. > >>>> I am wondering what I overlooked this time. > >>>> > >>>> \definecolumnset[Two][n=2] > >>>> \starttext > >>>> \startcolumnset[Two] > >>>> \input knuth > >>>> \stopcolumnset > >>>> \page > >>>> \setupcolumnsetlines[Two][1][1][9] > >>>> \startcolumnset[Two] > >>>> \input knuth > >>>> \stopcolumnset > >>>> \stoptext > >>>> > >>>> Thank you for your suggestions, > >>>> > >>>> Sytse Knypstra > >>>> > >>>> ___________________________________________________________________________________ > >>>> If your question is of interest to others as well, please add an entry > >>>> to the Wiki! > >>>> > >>>> maillist : ntg-context(a)ntg.nl / > >>>> http://www.ntg.nl/mailman/listinfo/ntg-context > >>>> webpage : http://www.pragma-ade.nl / http://context.aanhet.net > >>>> archive : https://bitbucket.org/phg/context-mirror/commits/ > >>>> wiki : http://contextgarden.net > >>>> > >>>> ___________________________________________________________________________________ > >>>> > >>> > Op 17 augustus 2019 om 16:24 schreef Wolfgang Schuster <wolfgang.schuster.lists(a)gmail.com>: > > > Denis Maier schrieb am 17.08.2019 um 15:50: > > This here works for the first columnset, but not for the second one: > > > > ================================= > > \usemodule[newcolumnsets] > The new code base is used by default and you don't have to load the module. > > \definecolumnset[One][n=2] > > > > \setupcolumnsetlines[One][1][1][9] > > \setupcolumnsetlines[One][1][2][9] > > \setupcolumnsetlines[One][2][1][9] > > \setupcolumnsetlines[One][2][2][9] > > > > \definecolumnset[Two][n=2] > > \setupcolumnsetlines[Two][1][1][9] > > \setupcolumnsetlines[Two][1][2][9] > > \setupcolumnsetlines[Two][2][1][9] > > \setupcolumnsetlines[Two][2][2][9] > The second argument expects the page number of the column where want > to change the number of lines. In your example the second environment > starts at page 3 but you change the lines only for the first and second > page. > > Wolfgang > > > Op 17 augustus 2019 om 17:00 schreef Wolfgang Schuster <wolfgang.schuster.lists(a)gmail.com>: > > > Denis Maier schrieb am 17.08.2019 um 16:45: > > Ok. So no need to load the module first. Good. > > > > So the second argument is an absolute pagenumber, not relative to > > where to columnset starts... But then, this here should work: > No, you set relative numbers (I checked it) but the first columnset > environment ends on the third page because you leave just enough > space on the second page to fit the text which produces an empty > third page. > > Wolfgang > >

1 0

lmtx setuparranging
by jkitz＠inradius.net 17 Aug '19

17 Aug '19

Booklet layout 2UP is not working with lmtx for me. MWE: under mkiv I get all 4 booklet pages laid out for two-sided print and fold. \setuppapersize[A5][A4,landscape] \setuparranging[2UP,doublesided] \starttext \dorecurse{4}{\input tufte \blank} \dorecurse{3}{\input bryson \blank} \dorecurse{3}{\input ward \blank} \stoptext context —version: mtx-context | main context file: /users/kitz/ctxmkiv/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2019.04.25 10:36 MNWE: When I switch to lmtx, only booklet pages 1 and 4 are set and repeated on next page. context —version: mtx-context | main context file: /users/kitz/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2019.08.17 12:16 There seems to be flushing of pages going on under lmtx. Thanks for any help. Kitz

1 0

Re: [NTG-context] \setupcolumnsetlines does not work
by Wolfgang Schuster 17 Aug '19

17 Aug '19

Denis Maier schrieb am 17.08.2019 um 17:49: > Ok. > With this I don't get the empty page. But the setupcolumnsetlines has > still no effecgt for the second environment. > > === > > \definecolumnset[One][n=2] > > \setupcolumnsetlines[One][1][1][9] > > \definecolumnset[Two][n=2] > > \setupcolumnsetlines[Two][1][1][5] > > \starttext > > \startcolumnset[One] > > \input knuth > > \stopcolumnset > > \startcolumnset[Two] > > \input knuth > > \stopcolumnset > > \stoptext > The settings for the second columnset work when the first columnset goes over of two or more pages. Wolfgang

1 0

Re: [NTG-context] \setupcolumnsetlines does not work
by Wolfgang Schuster 17 Aug '19

17 Aug '19

Denis Maier schrieb am 17.08.2019 um 16:45: > Ok. So no need to load the module first. Good. > > So the second argument is an absolute pagenumber, not relative to > where to columnset starts... But then, this here should work: No, you set relative numbers (I checked it) but the first columnset environment ends on the third page because you leave just enough space on the second page to fit the text which produces an empty third page. Wolfgang

1 0

\setupcolumnsetlines does not work
by Sytse Knypstra 17 Aug '19

17 Aug '19

In an effort to balance columns in a columnset layout, I found that in the following minimal example this effect is not obtained. After commenting out the first three lines after \starttext the result is ok. I am wondering what I overlooked this time. \definecolumnset[Two][n=2]  \starttext  \startcolumnset[Two]  \input knuth  \stopcolumnset  \page \setupcolumnsetlines[Two][1][1][9]  \startcolumnset[Two]  \input knuth  \stopcolumnset  \stoptext  Thank you for your suggestions, Sytse Knypstra

3 5

ConTeXt Meeting 2019 registration details and tshirts
by Taco Hoekwater 17 Aug '19

17 Aug '19

Hi all, Because I received some email requests on whether registration is still open for the ConTeXt meeting in Bassenge and what to do about day visits et cetera, here is the nitty gritty on that: * As of today, there is room left for 10 extra participants, so late registrations are still possible. * Nevertheless, if you are certain you want to attend; better make sure to register shortly. You’ll be sorry if there is a sudden influx of dozens of new ConTeXt users from CCCamp and registrations have to be closed because of lack of room ;) * There are no single rooms available any more. * Registration will be closed on Sunday September 8 even if we are not full up by then, as some dinner ingredients need to be ordered in advance. * Day visits and partial attendance are both possible, but must be announced before September 8 if you want to stay for dinner and/or overnight (see above). Note further that overnight stays are subject to availability of empty beds. Fees for such visits: Lunch: €10; Dinner: €30; Overnight stay: €40. * The registration form can be used for day visits and partial attendance as well as for “normal” registration: https://meeting.contextgarden.net/2019/register.shtml but emailing me personally works fine as well. I hope that covers everything. Feel free to contact me directly if I forgot something. Then, there is a note on T-shirts needed: At the moment, we do not have enough registrations for a balanced budget. This means we had to cancel the free conference T-shirt, sorry! However, all is not lost: Pavneet Arora will be producing T-shirts for those that are willing to pay cash on delivery at Bassenge. Expected price is around €15 per shirt. Because of production times, reservation is both required and urgent. The production order should be made next Monday or Tuesday at the latest, so if you want one (or more) of the T-shirts, decide quickly! Pavneet will probably post a screenshot of the final logo design later today, and I am sure he will answer any additional questions you may have. Best wishes, Taco

1 0

The odd semantics of \begincsname
by Henri Menke 17 Aug '19

17 Aug '19

Dear list, According to the LuaTeX documentation: “The \begincsname primitive is like \csname but doesn’t create a relaxed equivalent when there is no such name.” I thought it would be possible to use this fact to skip the \relax-ed definition when \def-ining a new control sequence, but the following MWE fails with \inaccessible: \expandafter\gdef\csname yes\endcsname{} \expandafter\gdef\begincsname no\endcsname{} \bye Is this a bug or is this behaviour intended? Could this be fixed by making manufacture_csname aware whether it is in a def_cmd context or not? Cheers, Henri

2 3

radiobuttons
by Henning Hraban Ramm 16 Aug '19

16 Aug '19

Hi, coming back to an old form project I find that something changed WRT to form fields. For one, some fields appear smaller and shifted upwards – I managed to fix that with setups. What I can’t change is behaviour of radiobuttons: if I click one, all rbs of one group activate, and I can’t deactivate them any more. In my project all of the fields are duplicated on other pages, and while all other fields’ contents get copied, it doesn’t work for radiobuttons; my minimal example unfortunately can’t show that. \setupinteraction[state=start] \setupfield[MMradio][ option=printable, frame=overlay, corner=round, height=1em, width=1em, align=bottom, ] \definefield[chooseTeX][radio][MMradio][rbContext,rbLatex,rbOther][rbContext] \definesubfield[rbContext][][] \definesubfield[rbLatex][][] \definesubfield[rbOther][][] \starttext I want to use \field[rbContext] \CONTEXT\ \field[rbLatex] \LaTeX\ \field[rbOther] other. \page Just to confirm: I want to use \field[rbContext] \CONTEXT\ \field[rbLatex] \LaTeX\ \field[rbOther] other. \stoptext Greetlings, Hraban

3 8