ntg-context November 2020

ntg-context@ntg.nl

61 participants
170 discussions

Orphan issue with \startitemize
by Bruce Horrocks 26 Nov '20

26 Nov '20

With the following MWE: \def\Lorem{Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. } \showframe \starttext %\dorecurse{32}{ ~ \par } %\dorecurse{33}{ ~ \par } \dorecurse{34}{ ~ \par } The following items are blah blah blsh: \startitemize \sym{-} \Lorem \sym{-} \Lorem \sym{-} \Lorem \sym{-} \Lorem \stopitemize \stoptext I find that \dorecurse{32} fits two items on the bottom of the first page and two at the top of the next. This is fine. With \dorecurse{33} I get one and three - which is also fine. With \dorecurse{34} all of the items move to the second page even though only one extra line has been added and there is now quite a large gap at the bottom of the first page. Is there a setting that controls this a bit more precisely, please? (So that \dorecurse{34} and possibly even 35 would still split one and three.) -- Bruce Horrocks Hampshire, UK

2 1

Re: [NTG-context] question about frames
by Andres Conrado Montoya 26 Nov '20

26 Nov '20

Disregard that... that is the default... it doesn't work as I thought initially. Sorry for the noise.

1 0

Re: [NTG-context] question about frames
by Andres Conrado Montoya 26 Nov '20

26 Nov '20

A bit late to the party but maybe this helps... try "frameoffset": \defineframed[caja][frameoffset=\zeropoint,width=5cm,height=2cm] \starttext \dorecurse{5}{\caja[frame=on]{Hello}} \stoptext -- Andrés Conrado Montoya

1 0

Re: [NTG-context] Vertical space when surrounding with textbackground
by Johann Birnick 26 Nov '20

26 Nov '20

On Thu, 2020-11-26 at 19:39 +0100, Johann Birnick wrote: > On Thu, 2020-11-26 at 19:35 +0100, Wolfgang Schuster wrote: > > Johann Birnick schrieb am 26.11.2020 um 19:26: > > > I didn't want to copy paste it :D Just add [option=XML] to \starttext like > > > this: > > > > Why do pass a option for the typing environment to \starttext? > > > > > \definetextbackground[code][background=color, backgroundcolor=lightgray, > > > frame=off, location=paragraph] > > > > > > \setuptyping[before={\startbackground[code]}, after={\stopbackground}] > > > > > > \starttext[option=XML] > > > \starttyping > > > This is some code > > > a second line > > > \stoptyping > > > \stoptext > > > > > > When I use \definetyping[Mytyping][option=XML] and then use \startMytyping > > > ... > > > \stopMytyping nothing changes. > > ??? > > > > \definetextbackground > > [Code] > > [ frame=off, > > background=color, > > backgroundcolor=lightgray, > > location=paragraph] > > > > \definetyping > > [Mytyping] > > [option=XML] > > > > \setuptyping > > %[Mytyping] > > [before={\blank\starttextbackground[Code]}, > > after={\stoptextbackground\blank}] > > > > \starttext > > > > \startMytyping > > <empty/> > > \stopMytyping > > > > \starttyping[option=XML] > > <empty/> > > \stoptyping > > > > \stoptext > > > > Wolfgang > > > > Sorry for confusing \starttext with \starttyping. > > @Wolfgang this is exactly what I mean. It doesn't work. There is an extra line > at the end. If you remove [option=XML] it works. So what is going wrong? > > Thank you, > Johann Ah, sorry again. I use \usemodule[Scite] at the begin of the document. Removing this helps. But I need it for the C and Cpp pretty printer. So do you know what's going on with Scite module? Thanks, Johann

2 4

new upload
by Hans Hagen 26 Nov '20

26 Nov '20

Hi, A new upload. Mojca upgraded the build manager and we also updated some machines so all binaries (platforms) should be in sync now. (No binaries for apples M1 and microsofts SQ2 as we don't have these machines, so just good old intel and arm it is.) On my rusty laptop the luametatex manual takes between 10 and 10.5 sec (depending on load). On the raspberry pi 64 bit it takes 32.5 sec (ubuntu, ssd on usb 3). The Windows Linux Subsystem (version 1) takes some 11.5 seconds and the domotica fitlet with a low power AMD A10 needs 27.5 sec.) The ratios match measurements of a while ago. In the meantime the format file got smaller, memory more dynamic and the mem footprint also smaller. I expect a modern intel laptop cpu to need some 5 seconds and a decent desktop less but who knows. It's not easy to squeeze out more (the bottleneck is in the lua code as the (con)tex(t) code is pretty efficient so we pay a price for flexibility). (In the process I saw that I bugged the xetex logo but that has to wait for a next upload. Hardly critital I suspect.) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

7 13

Vertical space when surrounding with textbackground
by Johann Birnick 26 Nov '20

26 Nov '20

Hi there, in my document(s) I have enumerations (created with \defineenumeration) and "typing"s (created with \definetyping) and I need to give a specific layout to them. In particular, I want to add textbackground (created with \definetextbackground) and sometimes a sidebar (created with \definesidebar) to them. However, when I surround for example my typing with a textbackground like this \starttextbackground[code] \startCpp ... \stopCpp \stoptextbackground or by putting the textbackground commands in "before=" and "after=" of my typing, then there will be an additional empty line at the end of the typing. Same with the enumerations and when I surround it with a sidebar instead of a textbackground. Often there is even an additional line / additional space before the typing/enumeration. How to surround such things properly? I just want a background to these and a sidebar. No addition spacing / empty lines. I would greatly appreciate your help. Thank you, Johann

3 10

Strange bug with obayspaces and tagging
by Christoph Reller 26 Nov '20

26 Nov '20

Hi, With the currently latest version of ConTeXt LMTX 2020.11.25 21:42, this MNWE fails with the following error message: ---- \setuptagging[state=start] \starttext \obeyspaces\obeylines patch \stoptext ---- tex error > tex error on line 4 in file ./scratch1.tex: Valid keyword expected, likely 'plus' <line 3.4> pa tch 1 \setuptagging[state=start] 2 \starttext 3 \obeyspaces\obeylines 4 >> patch 5 \stoptext ---- This may be a bug in the tagging feature. Cheers, Christoph

2 1

Issue with tex.romannumeral output
by Joseph 25 Nov '20

25 Nov '20

4 4

Issue with LMTX and placeformula
by Jean-Philippe Rey 25 Nov '20

25 Nov '20

Dear list, \placeformula doesn't seem to work with LMTX. ================== \starttext \placeformula[F] \startformula a^2 + b^2 = c^2 \stopformula The \in[F] formula \stoptext ================== Thank you for your help. -- Jean-Philippe Rey jean-philippe.rey(a)centralesupelec.fr 91192 Gif-sur-Yvette Cedex - France Empreinte PGP : 807A 5B2C 69E4 D4B5 783A 428A 1B5E E83E 261B BF51

2 1

Fwd: Some ligatures don't work in latest LMTX
by Jairo A. del Rio 25 Nov '20

25 Nov '20

---------- Forwarded message --------- De: Jairo A. del Rio <jairoadelrio6(a)gmail.com> Date: mar, 24 de nov. de 2020 a la(s) 14:16 Subject: Re: [NTG-context] Some ligatures don't work in latest LMTX To: Hans Hagen <j.hagen(a)xs4all.nl> Thank you very much, Hans. Ligatures now work. However, diacritics aren't properly placed even using "features=arabic" (they appear below letters in LMTX). ConTeXt MkIV still gives correct output. Thank you in advance. Jairo El mar, 24 de nov. de 2020 a la(s) 12:04, Hans Hagen (j.hagen(a)xs4all.nl) escribió: > On 11/24/2020 8:12 AM, Jairo A. del Rio wrote: > > |Hi everyone. The following example works fine with MkIV, but fails with > > latest LMTX. > > | > > > > |To be specific, the lam-alif ligature isn't working. Compile with both > > to see differences. > > | > > > > |Majalla is a Windows font, so I guess it's available for testing: > > | > > > > | > > \mainlanguage[arabic] \definefontfeature [arabic] > > [mode=node,language=dflt,script=arab, > > init=yes,medi=yes,fina=yes,isol=yes, > > liga=yes,dlig=yes,rlig=yes,clig=yes, > > mark=yes,mkmk=yes,kern=yes,curs=yes] > > \definefontfamily[main][serif][sakkalmajalla][features=arabic] > > \setupbodyfont[main] \setupdirections[bidi=global] \starttext أهلاً > وسهلاً > > \stoptext > > > > | > > > > |Is that a bug or are more features to be specified? Thank you in > advance. > (you can probably best use the already define arabic featre because it > also does some contextual stuff) > > anyway, there was an issue with the state querying (isol etc) as side > effect of another thing .. fixed in next upload (there haven't been > fundamental changes to the font handling for quite a while) > > Hans > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- >

1 1

← Newer
1
2
3
4
5
6
7
...
17
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context November 2020