Re: [NTG-context] Get list of all buffer names from lua

On 8/01/19 2:29 PM, Stanislav Sokolenko wrote: > That's perfect, thank you! I did see the cache variable in buff-ini.lua > but didn't realize it was being used as an upvalue in a closure. Is > there a specific reason for using the --debug flag rather than just > loading the debug module directly

Re: [NTG-context] Get list of all buffer names from lua

On 2019-01-07 9:06 p.m., Henri Menke wrote: On 8/01/19 1:37 PM, Stanislav Sokolenko wrote: Dear list, As the subject line states, I am looking for a means of retrieving a table of all saved buffer names from lua. A MNWE would looks like: It's not so easy because ConTeXt stores the buffers in

Re: [NTG-context] Get list of all buffer names from lua

On 8/01/19 1:37 PM, Stanislav Sokolenko wrote: > Dear list, > > As the subject line states, I am looking for a means of retrieving a > table of all saved buffer names from lua. A MNWE would looks like: It's not so easy because ConTeXt stores the buffers in a local variable `cache` which is an

[NTG-context] Get list of all buffer names from lua

Dear list, As the subject line states, I am looking for a means of retrieving a table of all saved buffer names from lua. A MNWE would looks like: \starttext \startbuffer[ex1] Buffer 1 \stopbuffer \startbuffer[ex2] Buffer 2 \stopbuffer % Should return {ex1, ex2} or similar

Re: [NTG-context] Problem with grid alignment and paragraph

Luca Donetti schrieb am 07.01.19 um 21:21: On Sun, Jan 6, 2019 at 2:53 PM Wolfgang Schuster > wrote: Luca Donetti schrieb am 14.12.18 um 22:14: > Dear list, > > I am facing a problem with grid alignment when using paragraphs. I >

Re: [NTG-context] Problem with grid alignment and paragraph

On Sun, Jan 6, 2019 at 2:53 PM Wolfgang Schuster < wolfgang.schuster.li...@gmail.com> wrote: > Luca Donetti schrieb am 14.12.18 um 22:14: > > Dear list, > > > > I am facing a problem with grid alignment when using paragraphs. I > > think it could be a bug because the MWE below produces lines

[NTG-context] Process file with '#' in the file name

Hello, is there a way to process a file with '#' in the file name by ConTeXt? E.g. file "T#.mkiv" with \starttext A \stoptext fails - not so surprisingly; but anyway - is there a way or "trick" to process it? Bets regards, Lukas

Re: [NTG-context] Update problems

On Mon, 7 Jan 2019 18:57:41 +0100 Hans Hagen wrote: > looking at this pdf file it makes sense to save as pdf from > illustrator because now you basically use the illustrator edit file > (with a lot of crap in it) and also some versioning (i suspect that the > xref is also bad so then you

Re: [NTG-context] Fwd: issue: multiple viewer layers

On 1/7/2019 3:37 PM, User 19087 wrote: Layers are not properly closed when using more than one layer, so that each layer subsumes all subsequent content. Tested in Adobe Reader 11. I first mentioned this at https://tex.stackexchange.com/a/467005/174577, so I'm basically rehashing all the

Re: [NTG-context] Update problems

On Mon, Jan 7, 2019 at 6:47 PM Weber, Matthias wrote: > > I still don’t know what’s going on with PDF inclusion. The ones that cause > trouble are kind of old (from 2005), and I could “upgrade” > > fixing it now -- luigi

Re: [NTG-context] Update problems

On 1/7/2019 6:47 PM, Weber, Matthias wrote: Update: The page setup works after Hans’ fix. Thanks, that was a relief. I still don’t know what’s going on with PDF inclusion. The ones that cause trouble are kind of old (from 2005), and I could “upgrade” we found the reason but anyway, looking

Re: [NTG-context] Update problems

Update: The page setup works after Hans’ fix. Thanks, that was a relief. I still don’t know what’s going on with PDF inclusion. The ones that cause trouble are kind of old (from 2005), and I could “upgrade” Them manually and things work now for this document. I have others that might cause

[NTG-context] Update problems

Dear List, After a while I decided updating my ConTeXt installation to ConTeXt ver: 2019.01.07 10:07 MKIV beta fmt: 2019.1.7. With an old document of mine I ran into two issues so far: Some of my old pdf images are not accepted as figures anymore. Example: \starttext

Re: [NTG-context] papersize problem with latest beta

> On 7. Jan 2019, at 17:07, Hans Hagen wrote: > > i uploaded a fix Sorry, didn’t see the new upload. Thanks, issue is fixed! Thomas ___ If your question is of interest to others as well, please add an entry to

Re: [NTG-context] papersize problem with latest beta

On 1/7/2019 4:49 PM, Thomas A. Schmitz wrote: Hi Hans, the latest and greatest (2019.01.07 10:07) has a problem with papersizes. MWE: \setuppapersize[A6] \showframe \starttext Hello world \stoptext All best i uploaded a fix Hans

[NTG-context] papersize problem with latest beta

Hi Hans, the latest and greatest (2019.01.07 10:07) has a problem with papersizes. MWE: \setuppapersize[A6] \showframe \starttext Hello world \stoptext All best Thomas ___ If your question is of interest to

[NTG-context] Fwd: issue: multiple viewer layers

Layers are not properly closed when using more than one layer, so that each layer subsumes all subsequent content. Tested in Adobe Reader 11. I first mentioned this at https://tex.stackexchange.com/a/467005/174577, so I'm basically rehashing all the examples: When \showallmakeup is enabled, all

[NTG-context] Fwd: issue: "printable" viewer layers lack compatibility

In 2017 ghostscript added support for the /Print and /View keys of the Optional Content /Usage dictionary[1]. The use of '-dPrinted' should display the print-only layer, per the documentation[2]: gs -o output.pdf -sDEVICE=pdfwrite -dPrinted input.pdf >From their repository you can see that