ntg-context August 2023

ntg-context@ntg.nl

48 participants
97 discussions

XML processing beginner's question
by Michael Löscher 22 Aug '23

22 Aug '23

Hello list, having the xml data at the bottom, I would like to process it so that the result is like this: --- What it is (e.g. bold formatted) date: 2023-08-01 (italic) Description (small font size) Another text (small font size) hd1 - Header 1 § 1 First (A first short description) AAAAAAAAAA BBBBBBBBBB § 2 Second (A second short description) CCCCCCCCCC DDDDDDDDDD § 3 Third (A third short description) EEEEEEEEEE FFFFFFFFFF --- How can I process the <element>s differently? The first element contains a <date> tag and so it differs from the other ones. The second element's <name> tag contains the word "Header" which makes it different again. The other elements contain a <shortdescription> tag that they all have in common. What could be the appropriate xml setups to generate the above output? Michael --- xml data: \startbuffer[xmlcontent] <?xml version="1.0" encoding="UTF-8" ?> <document> <element> <mdata> <name>What it is</name> <date>2023-08-01</date> </mdata> <tdata> <content> Description Another text </content> </tdata> </element> <element> <mdata> <num>hd1</num> <name>Header 1</name> </mdata> <tdata> <content> Text of Header 1 </content> </tdata> </element> <element> <mdata> <num>1</num> <name>First</name> <shortdescription>A first short description</shortdescription> </mdata> <tdata> <content> AAAAAAAAAA BBBBBBBBBB </content> </tdata> </element> <element> <mdata> <num>2</num> <name>Second</name> <shortdescription>A second short description</shortdescription> </mdata> <tdata> <content> CCCCCCCCCC DDDDDDDDDD </content> </tdata> </element> <element> <mdata> <num>3</num> <name>Third</name> <shortdescription>A third short description</shortdescription> </mdata> <tdata> <content> EEEEEEEEEE FFFFFFFFFF </content> </tdata> </element> </document> \stopbuffer

5 6

Low res output possible?
by Benjamin Buchmuller 22 Aug '23

22 Aug '23

Hi Julian, I had the same question a couple of days ago and I found a thread on the mailing list, which I'm reposting here. Although this worked for me, I found downsampling of the pdf with gs more convenient. Hope this helps, Benjamin %%%%% if not modules then modules = { } end modules ['grph-downsample'] = { version = 1.101, comment = "companion to grph-inc.mkiv", author = "Peter Münster", -- adapted to LMTX by Hraban copyright = "PRAGMA ADE / ConTeXt Development Team", license = "see context related readme files" } assert(not figures.getinfo2) figures.getinfo2 = function(name, page) -- [ [NTG-context] Pdf info with Lua/Ctx API ] if type(name) == "string" then name = { name = name, page = page } end if name.name then local data = figures.push(name) local info = figures.identify() if info.status.status ~= 0 then figures.check() -- !Counts pages here! end figures.pop() return --data info end end local format = string.format -- figures.cachepaths.path = "cache" -- should be setup-option local function sample_down(oldname, newname, resolution) print("DOWNSAMPLE sample_down " .. oldname .. " to " .. newname) local request = figures.current().request local width = request.width local height = request.height if resolution == "" then -- or (not width and not height) then print(format("DOWNSAMPLE Nothing to do: %s, %s, %s dpi, %s x %s px", oldname, newname, resolution, width, height)) return end local TEXpt = 65536 local inch = 72.27 -- MkIV: -- local image = img.scan{filename = oldname} -- LMTX: local image = figures.getinfo(oldname,1) image = image.status.private local xy = image.xsize / image.ysize if (not width and not height) then -- no size requested? use default width width = 300 * TEXpt end if not width then height = height / TEXpt width = height * xy end if not height then width = width / TEXpt height = width / xy end width = math.floor(width) height = math.floor(height) print(format("DOWNSAMPLE image size %dx%dpx. requested %dx%d?", image.xsize, image.ysize, width, height)) local xsize = math.floor(resolution * width / inch) local ysize = math.floor(resolution * height / inch) print(format("DOWNSAMPLE size %d x %d to %d x %d", image.xsize, image.ysize, xsize, ysize)) if xsize < image.xsize or ysize < image.ysize then local s = format("gm convert -resize %dx%d -resample %dx%d \"%s\" \"%s\"", xsize, ysize, resolution, resolution, oldname, newname) print("DOWNSAMPLE Conversion: " .. s) os.execute(s) else print(format("DOWNSAMPLE Nothing to do: %s, %s, %s dpi, %d x %d px", oldname, newname, resolution, width, height)) print(format("DOWNSAMPLE xsize = %d, ysize = %d", xsize, ysize)) end end local formats = {"png", "jpg", "gif"} for _, s in ipairs(formats) do figures.converters[s] = figures.converters[s] or {} figures.converters[s]["lowres." .. s] = sample_down end local function sample_down_pdf(oldname, newname, resolution) print("DOWNSAMPLE sample_down " .. oldname .. " to " .. newname) -- MkIV: -- local image = img.scan{filename = oldname} -- LMTX: local image = figures.getinfo(oldname,1) image = image.status.private local s = format("gs \ -o \"%s\" \ -sDEVICE=pdfwrite \ -dDownsampleColorImages=true \ -dDownsampleGrayImages=true \ -dDownsampleMonoImages=true \ -dColorImageResolution=%s \ -dGrayImageResolution=%s \ -dMonoImageResolution=%s \ -dColorImageDownsampleThreshold=1.0 \ -dGrayImageDownsampleThreshold=1.0 \ -dMonoImageDownsampleThreshold=1.0 \ \"%s\"", oldname, resolution, resolution, resolution, newname) print("DOWNSAMPLE Conversion: " .. s) os.execute(s) end figures.converters["pdf"]["lowres." .. "pdf"] = sample_down_pdf %%%%% \loadluafile[grph-downsample] \doifmodeelse{print}{% \def\Resolution{300} }{% \def\Resolution{96} }%

2 1

Re: XML processing beginner's question
by Thomas A. Schmitz 22 Aug '23

22 Aug '23

On 8/21/23 18:36, Michael Löscher wrote: > Thank you so far. But what I would like to understand first ist how the > different setups work togehter. How are they processed? What is the > order of processing, which are the stets taken by the enginge when > processing an xml document? Without understanding how that works, it is > not possible to apply certain tests on the xml nodes. > As the manual mk.pdf, chapter XVII states: it's a mixture of streaming parser and tree manipulation. The whole xml document is transformed into a Lua table and then processed. But I definitely get the "do my homework for me" vibe, so this will be all from me. Thomas

3 3

Not getting a page break in the ToC
by Andres Conrado Montoya 22 Aug '23

22 Aug '23

I'm trying to force a page break in a table of contents, using what is recommended at https://wiki.contextgarden.net/Table_of_Contents#Forced_Page_Break However, it does not work. Here's a MWE: \definelistextra[page][before=\page] \starttext \starttitle[title={Table of contents}] \placecontent[extras={2=page}] \stoptitle \startchapter[title={First chapter}] \input knuth \stopchapter \startchapter[title={Second chapter}] \input knuth \stopchapter \startchapter[title={Third chapter}] \input knuth \stopchapter \stoptext Is there a new way of obtaining a page break before a given part, chapter or section in the ToC? Thank you in advance. -- Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

2 2

Low res output possible?
by jbf 21 Aug '23

21 Aug '23

Just wondering: in programs like InDesign, Viva Designer, it is trivial to produce a low resolution pdf output (useful when exchanging a hi-res file with authors and editors prior to pre-print is difficult). I assume it might be possible to do so in ConTeXt. Currently I use a script (gs) to achieve that once I have the ConTeXt output so it is no difficulty, but if that could be done at time of compiling it would make the process just that bit simpler. Possible? Julian

1 0

redefine space to be the same as \␣ similar to knuthian approach
by Carlos 21 Aug '23

21 Aug '23

If I have the following, with these linebreaks as in: {\par But a system cannot be successful if it is too strongly influenced by a single person. {\obeylines Once the initial design is complete and fairly robust, the real test begins as people with many different viewpoints undertake their own experiments.}} and opted to load another font, other than cmr that is, a \frenchspacing approach wouldn't be further required Bear with me here, in the current state, for example, and as long as say «…person.␣{\obeylines Once the initial is complete…» though feasible enough, leaves any prior \␣ at the mercy of whatever fontsize and/or set width happens to be. And this is just plain wrong. Likewise, if a word sequence such as \TeX\ occurs as in {\ss The separation of any of these four components would have hurt \TeX\ significantly. } The next sentence: «If I had not participated…» does not get any \nofrenchspacing which is equally and doubly problematic. It shows lack of consistency. And this ought not to be an ‹either› ‹or› scenario. But rather, an and conjunctional construct. It fails both ways. Furthermore, with the same token, if width is specified with a \setuplayout[width=15cm] Anything less than 12.895pt, especifically for that use case, wwould throw anything, particularly control sequences such as \TeX\ out of whack, and conversely, once a value of that very pt or pica or whatever is lowered, it brings that nonfrenchspacing right back on. And if width increments occur, then it follows that any control sequence kerning also gets thrown off as a result. It seems so far, that with lmtx, any standalone file, document, minimal working example that does not load cmr at the outset does not produce an acceptable outcome either. By saying acceptable I meant to say it namely from a typographical point of view. Nothing else. from the TeXbook 380-381 «\obeylines doesn’t say ‘\def^^M{\par}’, so we must make any desired changes to \par before invoking \obeylines. (2) The \uncatcodespecials operation changes a space to category 12; but the \tt font has the character ‘␣’ in the ⟨space⟩ position, so we don’t really want ␣12 . (3) The \obeyspaces macro in Appendix B merely changes the ⟨space⟩ character to category 13; active character ␣13 has been defined to be the same as \space, a macro that expands to ␣10 . This is usually what is desired; for example, it means that spaces in constructions like ‘\hbox to 10 pt {...}’ won’t cause any trouble. But in our application it has an undesirable effect, because it produces spaces that are affected by the space factor. To defeat this feature, it’s necessary either to say \frenchspacing or to redefine ␣13 to be the same as \␣. The latter alternative is better, because the former will discard spaces at the beginning of each line.» «In theory, this seems like it ought to work; but in practice, it fails in two ways. One rather obvious failure—at least, it becomes obvious when the macro is tested—is that all the empty lines of the file are omitted. The reason is that the \par command at the end of an empty line doesn’t start up a new paragraph, because it occurs in vertical mode. The other failure is not as obvious, because it occurs much less often: The \tt fonts contain ligatures for Spanish punctuation, so the sequences ?‘ and !‘ will be printed as ¿ and ¡ respectively. Both of these defects can be cured by inserting and «When INITEX creates a brand new TEX, all characters have a space factor code of 1000, except that the uppercase letters ‘A’ through ‘Z’ have code 999. (This slight difference is what makes punctuation act differently after an uppercase letter; do you see why?) Plain TEX redefines a few of these codes using the \sfcode primitive, which is similar to \catcode (see Appendix B); for example, the instructions \sfcode‘)=0 \sfcode‘.=3000 make right parentheses “transparent” to the space factor, while tripling the stretcha- bility after periods. The \frenchspacing operation resets \sfcode‘. to 1000.» -- If at first you don't succeed, you must be a programmer.

7 16

zint 2.12.0 barcode generator
by Keith McKay 21 Aug '23

21 Aug '23

Hi all, I've updated the zint barcode generator on my mac mini to 2.12.0 and now no barcode is produced. I have this vague recollection that it is only the 2.10.0 version of zint which works in ConTeXt. If I am correct, is ConTeXt likely to be updated so that 2.12.0 works? I originally installed zint with Homebrew. There is a very complicated thread on stackoverflow on how to downgrade to previous versions of a formula in homebrew, but it is far too complicated for my wee brain. Thanks Keith McKay

3 4

Penalties and overprinting in tabulate
by denis.maier＠unibe.ch 21 Aug '23

21 Aug '23

Dear list, typesetting the example below results in lines printed above each other? Without the penalties, this doesn't happen. What am I missing here? How I can use the penalties without the not wanted overprinting? Best, Denis \startsetups[mypenalties] \setdefaultpenalties \setpenalties\clubpenalties{1}{150} \setpenalties\widowpenalties{1}{10000} \setpenalties\displaywidowpenalties{1}{10000} \stopsetups \setuplayout[setups=mypenalties] \starttext \starttabulate[|p(.15\textwidth)|p|] \NC asdf \NC a asdf asdf asdf asdf asdf asdf sdf asdf asdf asdf asdf asdf asdf asdf ashjkdf askldf askdlfjöaslkdfjaösdlf \NC \NR \NC asdf \NC a asdf asdf asdf asdf asdf asdf sdf asdf asdf asdf asdf asdf asdf asdf ashjkdf askldf askdlfjöaslkdfjaösdlf \NC \NR \NC asdf \NC a asdf asdf asdf asdf asdf asdf sdf asdf asdf asdf asdf asdf asdf asdf ashjkdf askldf askdlfjöaslkdfjaösdlf \NC \NR \NC asdf \NC a asdf asdf asdf asdf asdf asdf sdf asdf asdf asdf asdf asdf asdf asdf ashjkdf askldf askdlfjöaslkdfjaösdlf \NC \NR \NC asdf \NC a asdf asdf asdf asdf asdf asdf sdf asdf asdf asdf asdf asdf asdf asdf ashjkdf askldf askdlfjöaslkdfjaösdlf \NC \NR \stoptabulate \stoptext

2 4

Inconsistent behavior: \addfontfeature and CLD local function
by Hamid,Idris 20 Aug '23

20 Aug '23

Dear gang, For \addfeature and the like, a virtual font feature defined in terms of a CLD local function behaves differently from other font features. MWE: ============== \startluacode local function squeeze(tfmdata) for k, v in next, tfmdata.characters do v.width = 1.75 * (v.height or 0) v.depth = 1.75 * (v.depth or 0) end end local specification = { name = "sqtfm", description = "test", manipulators = { base = squeeze, node = squeeze, } } fonts.handlers.otf.features.register(specification) \stopluacode \definefontfeature[forceno] [mode=node, script=latn] \definefontfeature[forceyes] [mode=node, script=latn, smcp=force, sqtfm=force] % smcp=yes, % sqtfm=yes] \showglyphs \startTEXpage[offset=1em] \definedfont[texgyretermes-regular*forceyes] % \definedfont[texgyretermes-regular*forceno] % \addfeature{forceyes} abcdefg \stopTEXpage ============== You may toggle these lines: \definedfont[texgyretermes-regular*forceyes] % \definedfont[texgyretermes-regular*forceno] % \addfeature{forceyes} With \definedfont[texgyretermes-regular*forceyes] active we get the expected result: small caps plus some negative squeeze (= spread in this case). With \definedfont[texgyretermes-regular*forceno] \addfeature{forceyes} active we get an *unexpected* result: small caps but no negative squeeze. (Similar results occur if we toggle the "=force" lines with the "=yes" lines, but the larger project of which this is the MWE uses the force key.) Clue: A CLD with a feature defined via fonts.handlers.otf.addfeature doesn't seem to have this problem: ============== \startluacode local function squeeze(tfmdata) for k, v in next, tfmdata.characters do v.width = 1.75 * (v.height or 0) v.depth = 1.75 * (v.depth or 0) end end local specification = { name = "sqtfm", description = "test", manipulators = { base = squeeze, node = squeeze, } } fonts.handlers.otf.features.register(specification) fonts.handlers.otf.addfeature { name = "stest", type = "substitution", data = { a = "X", b = "P", } } \stopluacode \definefontfeature[forceno] [mode=node, script=latn] \definefontfeature[forceyes] [mode=node, script=latn, % % smcp=force, sqtfm=force, stest=force] % % smcp=yes, % sqtfm=yes, % stest=yes] \showglyphs \startTEXpage[offset=1em] \definedfont[texgyretermes-regular*forceyes] % \definedfont[texgyretermes-regular*forceno] % \addfeature{forceyes} abcdefg \stopTEXpage ============== So only the local-function feature appears to exhibit this inconsistency. What is the explanation for this inconsistent behavior? Is there a way to get the expected result for \addfeature etc.? Thank you in advance. Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

2 2

backend not forcing 1000 width units on fonts; em size must be applied or else fails
by Carlos 20 Aug '23

20 Aug '23

Mikael, Wolfgang: This is in reference to the prior Re: redefine space to be the same as \␣ similar to knuthian approach > Maybe your system is broken? > > > > > > 2. The example below results in a correct output for \TEX. > > > > > > > Not in my end with any font other than latin modern > > Here > > \setupbodyfont[stixtwo] > > > \setuplayout[width=16cm] > \showmakeup > > \starttext > > Thus, I came to the conclusion that the designer of a new > system must not only be the implementer and first > large||scale user; the designer should also write the first > user manual. > \setupbodyfont[12.895pt] > > {\ss The separation of any of these four components would have > hurt \TeX\ significantly. If I had not participated fully in > all these activities, literally hundreds of improvements > would never have been made, because I would never have > thought of them or perceived why they were important.\par} After long hours of meditation I was going to ask you, Mikael, what exactly did you mean by «maybe your system is broken» but I chose to have chatgpt to provide me all the answers instead; just kidding :) But It seems as if any other font without the correct width units causes kerning to be thrown off most noticeably on control sequences such as \TeX\ and presumably, this, in turn, rightly so, also causes those extra spaces all over When I read the log it said that the backend > fonts > width units are being forced to be 1000, but in reality this never happened. If it had happened, I wouldnt' have had this issue with sizes say at 10pt and 11pt The permissions for these font files are 644 or read permissions only and I wrongly assumed this would be taken care of by the backend, but by the looks of it, it didn't. Anyhow. Thank you for your time Mikael, Wolfgang. you too Hans. -- Seems a computer engineer, a systems analyst, and a programmer were driving down a mountain when the brakes gave out. They screamed down the mountain, gaining speed, but finally managed to grind to a halt, more by luck than anything else, just inches from a thousand foot drop to jagged rocks. They all got out of the car: The computer engineer said, "I think I can fix it." The systems analyst said, "No, no, I think we should take it into town and have a specialist look at it." The programmer said, "OK, but first I think we should get back in and see if it does it again."

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context August 2023