Re: [NTG-context] Bug in matrices/alignment (LMTX)

Nice. When I add empty braces ((}) the example works. Just curious: is that a bug or expected behaviour? Thank you a lot, Wolfgang. Cordially, Jairo :) El sáb., 14 de nov. de 2020 a la(s) 14:34, Wolfgang Schuster ( wolfgang.schuster.li...@gmail.com) escribió: > Jairo A. del Rio schrieb am

Re: [NTG-context] Bug in matrices/alignment (LMTX)

Jairo A. del Rio schrieb am 14.11.2020 um 20:10: Hi everyone. The following example works in ConTeXt MkIV but fails in ConTeXt LMTX: \def\rgeq{\vcenter{\rotate[rotation=270]{$>$}}} \definemathmatrix[void][left=,right=,simplecommand=voidmatrix] \starttext \startformula \voidmatrix{% G_{1,1},

[NTG-context] Bug in matrices/alignment (LMTX)

Hi everyone. The following example works in ConTeXt MkIV but fails in ConTeXt LMTX: \def\rgeq{\vcenter{\rotate[rotation=270]{$>$}}} \definemathmatrix[void][left=,right=,simplecommand=voidmatrix] \starttext \startformula \voidmatrix{% G_{1,1}, >, G_{1,2}, >, G_{1,3}, >, G_{1,4}, \ldots, G_1;

Re: [NTG-context] Bug in overprint? (was: how to set overprint)

> > may I ask someone, who understands knockout and overprint in the printing > press, to check test cases in the attached file from the test suite, if > overprint is working or not in Mark IV, please? > > Regards, > Jano > > Hi Jano, as far as I can check with my pdf editors, it seems

[NTG-context] Bug in overprint? (was: how to set overprint)

Hello, may I ask someone, who understands knockout and overprint in the printing press, to check test cases in the attached file from the test suite, if overprint is working or not in Mark IV, please? Regards, Jano On Fri, 30 Oct 2020 at 11:02, Jano Kula wrote: > > > On Thu, 29 Oct 2020 at

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On Thu, 5 Nov 2020 at 12:07, Taco Hoekwater wrote: > > > > On 5 Nov 2020, at 11:48, Sylvain Hubert wrote: > > > > After dozens of compilations of various minimal examples using the newly > installed context, the problem reappeared. > > > > Removing tex/texmf-cache does not help. > > > > Does

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On 11/5/2020 11:48 AM, Sylvain Hubert wrote: After dozens of compilations of various minimal examples using the newly installed context, the problem reappeared. Removing tex/texmf-cache does not help. Removing firefoxe does ... when I open e.g. the cnn website in firefox (for instance to keep

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> On 5 Nov 2020, at 11:48, Sylvain Hubert wrote: > > After dozens of compilations of various minimal examples using the newly > installed context, the problem reappeared. > > Removing tex/texmf-cache does not help. > > Does anyone know what files context modifies apart from tex/texmf-cache?

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

After dozens of compilations of various minimal examples using the newly installed context, the problem reappeared. Removing tex/texmf-cache does not help. Does anyone know what files context modifies apart from tex/texmf-cache? Sylvain On Wed, 4 Nov 2020 at 16:01, Sylvain Hubert wrote: >

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

The problem disappeared after a fresh installation of context with everything else untouched. On Thu, 29 Oct 2020 at 11:29, Sylvain Hubert wrote: > Hi, > > sorry if this is not the best place to file a bug but I found no working > bug tracker for context. > > Environment: > Manjaro 20.1.2,

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On 10/30/2020 7:48 PM, Sylvain Hubert wrote: Hi Bruce, > Could you please try their steps to reproduce - namely view a video in Firefox - and do so from a fresh reboot without starting or invoking ConTeXt so we can be sure that it is excluded from the equation? Thanks for the suggestion

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On 10/30/2020 8:14 PM, Sylvain Hubert wrote: A few new experiments: 1. `firefox --headless` stays quite no matter what 2. when `gimp` is running, `context --help` causes a rise of cpu usage of gimp up to 60% for ~1s 3. when only xfce4-terminal is running, I tried `context --help` for a few

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

A few new experiments: 1. `firefox --headless` stays quite no matter what 2. when `gimp` is running, `context --help` causes a rise of cpu usage of gimp up to 60% for ~1s 3. when only xfce4-terminal is running, I tried `context --help` for a few times and for each time, one of the following

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

Hi Bruce, > Could you please try their steps to reproduce - namely view a video in Firefox - and do so from a fresh reboot without starting or invoking ConTeXt so we can be sure that it is excluded from the equation? Thanks for the suggestion but firefox here has never had any issue playing a

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> You could test that theory by switching to a text terminal for running the ‘context’ command (assuming the text-only terminal is still accessible in Manjaro) and see whether the output of ‘context —help’ causes lag there as well. If I understand you correctly, here's what I've tried: 1. open

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> On 30 Oct 2020, at 09:34, n...@scorecrow.com wrote: > > Hi Sylvain, > > This bug tracker report > describes lagging / > freezing (which are symptoms of excessive CPU usage, of course) for versions > of Firefox from 70 to 74 inclusive

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

Hi Sylvain, This bug tracker report describes lagging / freezing (which are symptoms of excessive CPU usage, of course) for versions of Firefox from 70 to 74 inclusive on Manjaro. They also report Chromium seeing the same problem. These

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On 10/29/2020 5:44 PM, Sylvain Hubert wrote: So it seems likely that there is something special going on with exactly your computer or your context installation. Still, I fail to see what this implies. In particular, I find it not the most professional to assume a dust-proof environment for a

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

Hi aditya, > It is possible for you to check on a fresh install of manjaro in a virtual machine to rule out the possibility that something else in your system is causing this behavior. I remember trying context while browsing the wiki before so it should work normally in a brand new environment,

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> So it seems likely that there is something special going on with exactly your computer or your context installation. Still, I fail to see what this implies. In particular, I find it not the most professional to assume a dust-proof environment for a real-world product, and even unreasonable to

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On Thu, 29 Oct 2020, Sylvain Hubert wrote: > Hi, > > sorry if this is not the best place to file a bug but I found no working > bug tracker for context. > > Environment: > Manjaro 20.1.2, context 2020.09.20 23:02, firefox 82.0 > > Step to reproduce: > 1. `firefox --safe-mode # start firefox

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> On 29 Oct 2020, at 15:14, Sylvain Hubert wrote: > > > But it seems to be a big problem only on your machine > I fail to see what this implies. The point is that if this was a common problem, many users would complain or at least respond to your message with a “me too”. So it seems likely

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

On 10/29/2020 3:18 PM, Sylvain Hubert wrote: I would consider it more constructive to admit the existence of the bug and find a way look into the source code of luametatex, since `context --help` is obviously not a terribly complicated routine to investigate. As taco mentioned, it's very

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

I would consider it more constructive to admit the existence of the bug and find a way look into the source code of luametatex, since `context --help` is obviously not a terribly complicated routine to investigate. On Thu, 29 Oct 2020 at 13:56, Taco Hoekwater wrote: > > > > On 29 Oct 2020, at

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> But it seems to be a big problem only on your machine I fail to see what this implies. > What hardware are you running on? Is it a Raspberry PI? No, it's Core i5 + 8G ram + ssd. > Like any TeX-related program, ConTeXt does a fair bit of disk access while starting up. But none of the other

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> On 29 Oct 2020, at 12:44, Sylvain Hubert wrote: > > I've just tried chromium which behaves a bit better but still experiences a > sudden raise of cpu usage from <10% to >70% during ~1s. > I've also noticed that, even without any browser running, each time after I > compile a file with

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

I've just tried chromium which behaves a bit better but still experiences a sudden raise of cpu usage from <10% to >70% during ~1s. I've also noticed that, even without any browser running, each time after I compile a file with `context`, my terminal get stuck for ~1s. So I'm pretty sure this is a

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> On 29 Oct 2020, at 12:19, Sylvain Hubert wrote: > > And using safe mode here is just to make sure that the problem is not caused > by extensions. > The annoyance started long before I bothered opening firefox with an extra > argument. I am baffled then. I do not see the connection, at

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

Update: `mtxrun --script # without more arguments` triggers the same problem. On Thu, 29 Oct 2020 at 12:02, Taco Hoekwater wrote: > > > > On 29 Oct 2020, at 11:29, Sylvain Hubert wrote: > > > > Hi, > > > > sorry if this is not the best place to file a bug but I found no working > bug tracker

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

And using safe mode here is just to make sure that the problem is not caused by extensions. The annoyance started long before I bothered opening firefox with an extra argument. On Thu, 29 Oct 2020 at 12:02, Taco Hoekwater wrote: > > > > On 29 Oct 2020, at 11:29, Sylvain Hubert wrote: > > > >

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

Hi Taco, thanks for the suggestions, but as mentioned earlier, `mtxrun --script font --list --all` triggers the same problem as `context` does. I guess the problem might have something to do with fonts, but since `context` aka `luametatex` is not open source yet, I can't analyse further. Best,

Re: [NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

> On 29 Oct 2020, at 11:29, Sylvain Hubert wrote: > > Hi, > > sorry if this is not the best place to file a bug but I found no working bug > tracker for context. Should you not be looking for a bug tracker for firefox instead? It looks like firefox in safe mode is perhaps trying to do

[NTG-context] Bug: context/mtxrun makes Firefox eat up cpu

Hi, sorry if this is not the best place to file a bug but I found no working bug tracker for context. Environment: Manjaro 20.1.2, context 2020.09.20 23:02, firefox 82.0 Step to reproduce: 1. `firefox --safe-mode # start firefox without add-ons` 2.a`context --version # or --help, or without

[NTG-context] Bug(s)(?) in \processwords (Mark IV)

The following: \starttext \unexpanded\def\lol#1% { \begingroup \let\processword\inframed \processwords{#1}% \endgroup } \lol{nice $x^2$} %see what happens with the superscript \stoptext works with ConTeXt LMTX, but fails with ConTeXt MkIV:

Re: [NTG-context] bug with hz in LMTX?

On 10/13/2020 4:47 PM, Pablo Rodriguez wrote: On 10/13/20 1:36 PM, Hans Hagen wrote: On 10/12/2020 4:59 PM, Pablo Rodriguez wrote: [...] On page 36 (https://pdf.ousia.tk/wrong-font-expansion.pdf#page=36), lines 4, 11 and 20 are wrong. Current LMTX (LuaTeX 2.07 20200920 + ConTeXt MkIV

Re: [NTG-context] bug with hz in LMTX?

On 10/13/20 1:36 PM, Hans Hagen wrote: > On 10/12/2020 4:59 PM, Pablo Rodriguez wrote: >> [...] >> On page 36 (https://pdf.ousia.tk/wrong-font-expansion.pdf#page=36), >> lines 4, 11 and 20 are wrong. >> >> Current LMTX (LuaTeX 2.07 20200920 + ConTeXt MkIV 2020.09.20 23:02) has >> the issue, while

Re: [NTG-context] bug with hz in LMTX?

On 10/12/2020 4:59 PM, Pablo Rodriguez wrote: Dear list, I have the following sample: \showframe\showgrid \setuplayout[width=middle] \definefontfamily[mainface][rm][TeX Gyre Pagella] [features={default, quality}] \setupbodyfont[mainface, 20pt] \setupalign[hanging, hz]

[NTG-context] bug with hz in LMTX?

Dear list, I have the following sample: \showframe\showgrid \setuplayout[width=middle] \definefontfamily[mainface][rm][TeX Gyre Pagella] [features={default, quality}] \setupbodyfont[mainface, 20pt] \setupalign[hanging, hz] \starttext \dorecurse{25}{\input{zapf}\input{cuomo}}

Re: [NTG-context] [BUG] \registerexternalfigure doesn't work

Henri Menke schrieb am 20.08.2020 um 07:05: Dear list, To get properties of a figure without actually typesetting it, it is handy to use \registerexternalfigure. However, trying to use it fails. Consider the following MWE: \starttext \registerexternalfigure[cow.pdf] \stoptext

[NTG-context] [BUG] \registerexternalfigure doesn't work

Dear list, To get properties of a figure without actually typesetting it, it is handy to use \registerexternalfigure. However, trying to use it fails. Consider the following MWE: \starttext \registerexternalfigure[cow.pdf] \stoptext Looking at the definition in grph-inc.mkiv

Re: [NTG-context] Bug with \wordright in LMTX version 2020-08-03 14:25

Fabrice Couvreur schrieb am 05.08.2020 um 19:33: Hello, I also use a square to complete a demonstration. I tried this without success Thank you Fabrice \definesymbol[Fin][\mathematics{\square}] \def\qed{\strut\wordright{\symbol[Fin]}} \defineenumeration   [proof]   [...,    

Re: [NTG-context] Bug with \wordright in LMTX version 2020-08-03 14:25

Hello, I also use a square to complete a demonstration. I tried this without success Thank you Fabrice \definesymbol[Fin][\mathematics{\square}] \def\qed{\strut\wordright{\symbol[Fin]}} \defineenumeration [proof] [text=Démonstration, alternative=serried, distance=\zeropoint,

Re: [NTG-context] Bug with \wordright in LMTX version 2020-08-03 14:25

Hi Hans, Thanks for the hint which consists in adding an \ifmmode to the definition of \qed. However, as you suggest, one needs some other mechanism in math mode, since with your new definition of \qed the alignment of the formula changes when one adds this close symbol:

Re: [NTG-context] bug in current latest (2019.10.11 15:57)?

On 8/3/2020 7:26 PM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 03.08.2020 um 19:06: Hi Hans, the following sample complains about an undefined command with ConTeXt latest (2019.10.11 15:57):     \starttext     {\em æb}     \stoptext I think this might be a bug in LMTX. The

Re: [NTG-context] Bug with \wordright in LMTX version 2020-08-03 14:25

On 8/3/2020 10:10 PM, Otared Kavian wrote: Hi Hans, A file which used to be typeset correctly with the previous versions of lmtx, now produces an error. Despite the error message being extremely cryptic: Error ! Missing number, treated as zero I could guess the origin of the bug, which

[NTG-context] Bug with \wordright in LMTX version 2020-08-03 14:25

Hi Hans, A file which used to be typeset correctly with the previous versions of lmtx, now produces an error. Despite the error message being extremely cryptic: Error ! Missing number, treated as zero I could guess the origin of the bug, which seems to be \wordright, but although the

Re: [NTG-context] bug in current latest (2019.10.11 15:57)?

On 8/3/20 7:26 PM, Wolfgang Schuster wrote: > Pablo Rodriguez schrieb am 03.08.2020 um 19:06: >> Hi Hans, >> >> the following sample complains about an undefined command with ConTeXt >> latest (2019.10.11 15:57): >> >> \starttext >> {\em æb} >> \stoptext >> >> I think this might be a

Re: [NTG-context] bug in current latest (2019.10.11 15:57)?

Pablo Rodriguez schrieb am 03.08.2020 um 19:06: Hi Hans, the following sample complains about an undefined command with ConTeXt latest (2019.10.11 15:57): \starttext {\em æb} \stoptext I think this might be a bug in LMTX. The following two constants are missing from

[NTG-context] bug in current latest (2019.10.11 15:57)?

Hi Hans, the following sample complains about an undefined command with ConTeXt latest (2019.10.11 15:57): \starttext {\em æb} \stoptext I think this might be a bug in LMTX. Many thanks for your help, Pablo -- http://www.ousia.tk

Re: [NTG-context] Bug with lmtx and color in table

Fabrice Couvreur schrieb am 22.07.2020 um 17:09: Hello, With the latest version of lmtx, the background color of cells does not work. Unrelated to tables. You can reduce xtable and natural table based examples very often to a simple \framed because both tables types inherit many features

[NTG-context] Bug with lmtx and color in table

Hello, With the latest version of lmtx, the background color of cells does not work. Thank you. Fabrice \starttext \startxtable [align={middle,lohi}, offset=0.8ex,background=color, backgroundcolor=red,frame=off] \startxrow \startxcell

Re: [NTG-context] Bug in latest LMTX

On 7/22/2020 5:43 AM, Otared Kavian wrote: Hi Hans, It seems that \cap is not anymore defined in the latest LMTX: the following gives an error \starttext $A \cap B$ \stoptext with current version: 2020.07.21 18:39. Also, I would like to place a request about the reporting of errors: can we

[NTG-context] Bug in latest LMTX

Hi Hans, It seems that \cap is not anymore defined in the latest LMTX: the following gives an error \starttext $A \cap B$ \stoptext with current version: 2020.07.21 18:39. Also, I would like to place a request about the reporting of errors: can we get back the nice reporting of errors we had

Re: [NTG-context] bug with \hyphenatedurl in latest?

On 6/12/20 2:26 PM, Pablo Rodriguez wrote: > [...] > I’m afraid I’m experiencing a problem with \hyphenatedurl: > > \starttext > \hyphenatedurl{} > \stoptext > > The sample above outuputs "tterhat". Many thanks for your fast fix in latest, Hans. Pablo -- http://www.ousia.tk

[NTG-context] bug with \hyphenatedurl in latest?

Hans, many thanks for the new latest. I’m afraid I’m experiencing a problem with \hyphenatedurl: \starttext \hyphenatedurl{} \stoptext The sample above outuputs "tterhat". Many thanks for your help, Pablo -- http://www.ousia.tk

[NTG-context] Bug in lmtx or wrong setup?

Hi all, I encountered a very strange problem. I want to have section headlines expanding the whole textarea, but the following copy text of the section shall be typeset in columns. I have this setup and it works fine. \setuphead [section] [ insidesection=\startcolumns,

Re: [NTG-context] bug in \doifinset

On 5/28/20 12:23 AM, Hans Hagen wrote: > On 5/27/2020 10:39 PM, Wolfgang Schuster wrote: >> Pablo Rodriguez schrieb am 27.05.2020 um 22:31: >>> [...] >>> I think this may be a bug, since the sample above would only get "yes" >>> with { i7}. >> >> No spaces are allowed in these lists. Older

Re: [NTG-context] bug in \doifinset

On 5/27/20 11:58 PM, luigi scarso wrote: >> On Wed, May 27, 2020 at 11:28 PM Pablo Rodriguez wrote: >> Without commas, lists are harder both to read and to write (at least, to me). > > what about > > \starttext > \startTEXpage[offset=1em] > \doifinsetelse{i7}{% > i4,% > i5,% > i7,% > } >        

Re: [NTG-context] bug in \doifinset

On 5/27/2020 10:39 PM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 27.05.2020 um 22:31: Hi Hans, the following sample: \starttext \startTEXpage[offset=1em] \doifinsetelse{i7}{i4, i5, i7} {yes}{no} \stopTEXpage \stoptext outputs "yes" with latest from

Re: [NTG-context] bug in \doifinset

Pablo Rodriguez schrieb am 27.05.2020 um 23:28: On 5/27/20 10:39 PM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 27.05.2020 um 22:31: [...] I think this may be a bug, since the sample above would only get "yes" with { i7}. No spaces are allowed in these lists. Older versions of the

Re: [NTG-context] bug in \doifinset

On Wed, May 27, 2020 at 11:28 PM Pablo Rodriguez wrote: > > Without commas, lists are harder both to read and to write (at least, to > me). > > what about \starttext \startTEXpage[offset=1em] \doifinsetelse{i7}{% i4,% i5,% i7,% } {yes}{no} \stopTEXpage \stoptext here seems to work. --

Re: [NTG-context] bug in \doifinset

On 5/27/20 10:39 PM, Wolfgang Schuster wrote: > Pablo Rodriguez schrieb am 27.05.2020 um 22:31: >> [...] >> I think this may be a bug, since the sample above would only get "yes" >> with { i7}. > No spaces are allowed in these lists. Older versions of the command > removed the spaces before the

Re: [NTG-context] bug in \doifinset

Pablo Rodriguez schrieb am 27.05.2020 um 22:31: Hi Hans, the following sample: \starttext \startTEXpage[offset=1em] \doifinsetelse{i7}{i4, i5, i7} {yes}{no} \stopTEXpage \stoptext outputs "yes" with latest from 2020.05.18 16:50, but "no" with latest from

[NTG-context] bug in \doifinset

Hi Hans, the following sample: \starttext \startTEXpage[offset=1em] \doifinsetelse{i7}{i4, i5, i7} {yes}{no} \stopTEXpage \stoptext outputs "yes" with latest from 2020.05.18 16:50, but "no" with latest from 2020.05.25 23:39. I think this may be a bug, since the

Re: [NTG-context] bug in PDF boxes? (was: Re: Trouble setting PDF boxes))

I would like to add though that even if the code you posted did work properly, Pablo, it wouldn't solve my original problem. It would be good if cropoffset, trimoffset etc. took two dimensions, one for the x direction and one for the y direction, instead of one for both. But I appreciate you

[NTG-context] bug in PDF boxes? (was: Re: Trouble setting PDF boxes))

On 4/25/20 2:37 PM, Jack Steyn wrote: > Hi, > > I am having trouble setting the PDF boxes to my desired dimensions. > Suppose I have \setuppapersize[/a/][/b/]. I want CropBox = MediaBox > =/ //b/. So far, so good: I can just use cropoffset=0mm in \setuplayout. > But I want TrimBox = /a/. However,

Re: [NTG-context] Bug (Lua) ?

Lua strings can be split across lines by using so called long brackets according to the Lua Reference Manual: [[split string]] or (very first newline ignored): [[ split string]] or with matched levels: [==[ ]==] dr. Hans van der Meer > On 19 Mar 2020, at 14:29, Aditya Mahajan wrote: >

Re: [NTG-context] Bug (Lua) ?

On Thu, 19 Mar 2020, mf wrote: Il 19/03/20 11:20, Fabrice Couvreur ha scritto: Hi, this file did not pose any problems but today yes. Thank you. Fabrice \starttext \startluacode local letters_1 = { "A", "B", "C", "D", "E", "F", "G", "H", "I", "J" } local letters_2 = { "1", "Année", "1998",

Re: [NTG-context] Bug (Lua) ?

Hi mf, Thanks ! Fabrice Le jeu. 19 mars 2020 à 11:46, mf a écrit : > Il 19/03/20 11:20, Fabrice Couvreur ha scritto: > > Hi, > > this file did not pose any problems but today yes. > > Thank you. > > Fabrice > > > > \starttext > > \startluacode > > local letters_1 = { "A", "B", "C", "D", "E",

Re: [NTG-context] Bug (Lua) ?

Il 19/03/20 11:20, Fabrice Couvreur ha scritto: Hi, this file did not pose any problems but today yes. Thank you. Fabrice \starttext \startluacode local letters_1 = { "A", "B", "C", "D", "E", "F", "G", "H", "I", "J" } local letters_2 = { "1", "Année", "1998", "1999", "2000", "2001", "2002",

Re: [NTG-context] Bug (Lua) ?

On 3/19/2020 11:20 AM, Fabrice Couvreur wrote: Hi, this file did not pose any problems but today yes. really? lua error       > lua error on line 34 in file /home/viserion/Table.tex: [ctxlua]:5: unfinished string near '"align={middle,lohi},' there is a " before align

[NTG-context] Bug (Lua) ?

Hi, this file did not pose any problems but today yes. Thank you. Fabrice \starttext \startluacode local letters_1 = { "A", "B", "C", "D", "E", "F", "G", "H", "I", "J" } local letters_2 = { "1", "Année", "1998", "1999", "2000", "2001", "2002", "2003", "2004", "2005","2006" }

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

On 3/16/20 7:00 PM, Wolfgang Schuster wrote: > [...] > A way to fix the wrong spacing here is to add a strut option to > \setuplist (or use always the upright font to set the strut values). Any of these ones would be great to avoid the corner cases. Pablo -- http://www.ousia.tk

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

Hans Hagen schrieb am 16.03.2020 um 18:42: On 3/16/2020 6:01 PM, Wolfgang Schuster wrote: Henning Hraban Ramm schrieb am 16.03.2020 um 15:42: Am 2020-03-16 um 14:35 schrieb Hans Hagen : Yes, pagella is a extreme case but when you use bold text the vertical spacing is also messed up. You

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

On 3/16/2020 6:01 PM, Wolfgang Schuster wrote: Henning Hraban Ramm schrieb am 16.03.2020 um 15:42: Am 2020-03-16 um 14:35 schrieb Hans Hagen : Yes, pagella is a extreme case but when you use bold text the vertical spacing is also messed up. You can avoid this when you use a fixed

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

Henning Hraban Ramm schrieb am 16.03.2020 um 15:42: Am 2020-03-16 um 14:35 schrieb Hans Hagen : Yes, pagella is a extreme case but when you use bold text the vertical spacing is also messed up. You can avoid this when you use a fixed lineheight (e.g. \setupinterlinespace[line=14pt])

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

> Am 2020-03-16 um 14:35 schrieb Hans Hagen : >> Yes, pagella is a extreme case but when you use bold text the vertical >> spacing is also messed up. You can avoid this when you use a fixed >> lineheight (e.g. \setupinterlinespace[line=14pt]) because the default >> distance is font dependant

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

On 3/16/2020 1:27 PM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 16.03.2020 um 10:01: On 3/15/20 10:56 PM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 15.03.2020 um 20:32: [...] Everthing is fine when italic fonts aren’t used. It can be fixed with a strut option for lists,

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

Pablo Rodriguez schrieb am 16.03.2020 um 10:01: On 3/15/20 10:56 PM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 15.03.2020 um 20:32: [...] Everthing is fine when italic fonts aren’t used. It can be fixed with a strut option for lists, e.g. \setuplist[strut=no]. The problem in this

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

On 3/15/20 10:56 PM, Wolfgang Schuster wrote: > Pablo Rodriguez schrieb am 15.03.2020 um 20:32: >> [...] >> Everthing is fine when italic fonts aren’t used. > > It can be fixed with a strut option for lists, e.g. > \setuplist[strut=no]. The problem in this case is that the ex-height for > the

Re: [NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

Pablo Rodriguez schrieb am 15.03.2020 um 20:32: Hi Hans, here you have the sample: \setuppapersize[A6] \setupinteraction[state=start] \enabledirectives[references.border] \setupbodyfont[pagella] \starttext \placelist[section] [alternative=d,

[NTG-context] (bug?) wrong interline in \placelist[alternative=d] with Pagella italics

Hi Hans, here you have the sample: \setuppapersize[A6] \setupinteraction[state=start] \enabledirectives[references.border] \setupbodyfont[pagella] \starttext \placelist[section] [alternative=d, style=\it] \section{Section 1}

Re: [NTG-context] BUG: module loading is broken

On 1/13/2020 2:26 AM, Henri Menke wrote: Here is a patch. --- a/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.lua +++ b/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.lua @@ -85,7 +85,7 @@ end function correspondence.file(environment,name)

Re: [NTG-context] BUG: module loading is broken

Here is a patch. --- a/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.lua +++ b/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-cor-00.lua @@ -85,7 +85,7 @@ end function correspondence.file(environment,name) local environment = environment local name

[NTG-context] BUG: module loading is broken

Dear Hans, Recent updates to ConTeXt broke my CV. This MWE \usemodule[letter] \starttext \stoptext fails with ...texmf-modules/tex/context/third/letter/base/s-cor-00.lua:88: attempt to call a nil value (field 'uselibrary') Here are the steps by which I can reproduce on my machine: rm -rf

Re: [NTG-context] Bug inline math in lmtx

On 12/14/2019 9:06 PM, Otared Kavian wrote: Hi Hans, It seems that the bug which was reported recently is again there: inline math does not show some symbols (lmtx version 2019.12.12 19:35). However mkiv version 2019.12.12 19:23 MKIV beta fmt: 2019.12.14 works fine. Here is a minimal

[NTG-context] Bug inline math in lmtx

Hi Hans, It seems that the bug which was reported recently is again there: inline math does not show some symbols (lmtx version 2019.12.12 19:35). However mkiv version 2019.12.12 19:23 MKIV beta fmt: 2019.12.14 works fine. Here is a minimal example. \starttext Let $f(x) := \sum_{n \geq

Re: [NTG-context] Bug: Segmentation fault

On Wed, Dec 11, 2019 at 12:10 AM Hans Hagen wrote: > On 12/11/2019 12:03 AM, luigi scarso wrote: > > I guess that we have to check if catcodetable -1 is already defined... > i already sent you a patch, probbaly also ok for trunk > Committed revision 7235. -- luigi

Re: [NTG-context] Bug: Segmentation fault

On 12/11/2019 1:28 AM, Henri Menke wrote: $ luatex <(echo '\relax\directlua{print("\string\\,")}\bye') This is LuaTeX, Version 1.11.2 (TeX Live 2020/dev)  restricted system commands enabled. (/dev/fd/63\, ) I don't even want to think about what piping adds to this (some command line

Re: [NTG-context] Bug: Segmentation fault

On Wed, Dec 11, 2019 at 1:28 AM Henri Menke wrote: > In this case I wanted to generate the thin space (\,). My expectation > (which worked elsewhere) was that full expansion will turn "\string\\," > into "\\," where the two backslashes have catcode 12 and will not be > expanded further. Then

Re: [NTG-context] Bug: Segmentation fault

On 12/11/19 12:23 PM, luigi scarso wrote: On Wed, Dec 11, 2019 at 12:10 AM Hans Hagen wrote: On 12/11/2019 12:03 AM, luigi scarso wrote: On Tue, Dec 10, 2019 at 9:27 PM Henri Menke mailto:henrime...@gmail.com>> wrote: Dear devs, The example below crashes LuaTeX with a

Re: [NTG-context] Bug: Segmentation fault

On Wed, Dec 11, 2019 at 12:10 AM Hans Hagen wrote: > On 12/11/2019 12:03 AM, luigi scarso wrote: > > > > > > On Tue, Dec 10, 2019 at 9:27 PM Henri Menke > > wrote: > > > > Dear devs, > > > > The example below crashes LuaTeX with a segmentation fault. It is

Re: [NTG-context] Bug: Segmentation fault

On 12/11/2019 12:03 AM, luigi scarso wrote: On Tue, Dec 10, 2019 at 9:27 PM Henri Menke > wrote: Dear devs, The example below crashes LuaTeX with a segmentation fault.  It is reproducible with LuaTeX 1.10.1 7143 and LuaTeX 1.11.2 7226.  To this

Re: [NTG-context] Bug: Segmentation fault

On Tue, Dec 10, 2019 at 9:27 PM Henri Menke wrote: > Dear devs, > > The example below crashes LuaTeX with a segmentation fault. It is > reproducible > with LuaTeX 1.10.1 7143 and LuaTeX 1.11.2 7226. To this end I built 7226 > from > source with --debugopt to get a backtrace, which can be found

Re: [NTG-context] Bug: Segmentation fault

On 12/10/2019 9:26 PM, Henri Menke wrote: Dear devs, The example below crashes LuaTeX with a segmentation fault.  It is reproducible with LuaTeX 1.10.1 7143 and LuaTeX 1.11.2 7226.  To this end I built 7226 from source with --debugopt to get a backtrace, which can be found below as well. i

Re: [NTG-context] Bug: Segmentation fault

On Tue, Dec 10, 2019 at 9:27 PM Henri Menke wrote: > Dear devs, > > The example below crashes LuaTeX with a segmentation fault. It is > reproducible > with LuaTeX 1.10.1 7143 and LuaTeX 1.11.2 7226. To this end I built 7226 > from > source with --debugopt to get a backtrace, which can be found

[NTG-context] Bug: Segmentation fault

Dear devs, The example below crashes LuaTeX with a segmentation fault. It is reproducible with LuaTeX 1.10.1 7143 and LuaTeX 1.11.2 7226. To this end I built 7226 from source with --debugopt to get a backtrace, which can be found below as well. Cheers, Henri ---

Re: [NTG-context] Bug: \adjustspacing=1 does not disable expansion

On 12/5/2019 1:39 AM, Henri Menke wrote: It actually seems as if the documentation of LuaTeX is wrong here, because the behaviour of `\adjustspacing=1' is compatible with `\pdfadjustspacing=1` in pdfTeX.  From the pdfTeX manual:     When \pdfadjustspacing is set to 1, font expansion is applied

Re: [NTG-context] Bug: \adjustspacing=1 does not disable expansion

It actually seems as if the documentation of LuaTeX is wrong here, because the behaviour of `\adjustspacing=1' is compatible with `\pdfadjustspacing=1` in pdfTeX. From the pdfTeX manual: When \pdfadjustspacing is set to 1, font expansion is applied after TeX’s normal paragraph breaking

Re: [NTG-context] Bug: \adjustspacing=1 does not disable expansion

Possible patch (can be directly used with `git apply') diff --git a/source/texk/web2c/luatexdir/tex/postlinebreak.c b/source/texk/web2c/luatexdir/tex/postlinebreak.c index cbc77e556..9cd76b5fa 100644 --- a/source/texk/web2c/luatexdir/tex/postlinebreak.c +++

<    1   2   3   4   5   6   7   8   9   10   >