August 2023 - ntg-context - NTG Mailing Lists

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

Applying \sc for smallcaps across styles
by Hamid,Idris 19 Aug '23

19 Aug '23

Dear gang, Consider the following typescript template: \definefontfeature [myfont-tf-sc] [mode=node,script=latn,language=dflt,trep=no, protrusion=quality,expansion=quality, compose=yes,combine=yes,tlig=yes, kern=yes,liga=yes,onum=yes,cpsp=yes,smcp=yes, % smcp activie trnsl=force] % synonym mapping \starttypescript [serif] [myfont] [name] \loadfontgoodies[myfontlfg] \definefontsynonym [Serif] [MyFontRegular] [features=myfont-tf] \definefontsynonym [SerifItalic] [MyFontItalic] [features=myfont-it] \definefontsynonym [SerifBold] [MyFontBold] [features=myfont-tf] \definefontsynonym [SerifBoldItalic] [MyFontBoldItalic] [features=myfont-it] \definefontsynonym [SerifCaps] [MyFontRegular] [features=myfont-tf-sc] \definefontsynonym [SerifCapsItalic] [MyFontItalic] [features=myfont-it-sc] \definefontsynonym [SerifCapsBold] [MyFontBold] [features=myfont-tf-sc] \definefontsynonym [SerifCapsBoldItalic] [MyFontBoldItalic] [features=myfont-it-sc] \stoptypescript % font mapping \starttypescript [serif] [myfont] \loadfontgoodies[myfontlfg] \definefontsynonym [MyFontRegular] [file:MyFont-Regular] % [features=myfont-tf] \definefontsynonym [MyFontItalic] [file:MyFont-It] % [features=myfont-it] \definefontsynonym [MyFontBold] [file:MyFont-Bold] % [features=myfont-tf] \definefontsynonym [MyFontBoldItalic] [file:MyFont-BoldIt] % [features=myfont-it] \stoptypescript As is well known, \sc selects the small caps only from the Serif font, not from SerifBold etc. But MyFont has smallcaps for every style. So in the typescript we make that explicit and apply the smcp=yes fontfeature to SerifCapsBold etc. But this does not work: \sc still only applies to Serif or SerifCaps. Now I can load a goodies file myfontlfg and do something like this: local smallcaps = { smcp = yes, } But that does not change the behavior of \sc. Yes, there is an easy workaround: \definefontfeature[smallcaps][smcp=yes] \define\sc{\addff{smallcaps}} This works for all styles that have the smcp feature, but I don't like having to redefine a system command. So the questions are: 1) Is there a recommended\better way to get \sc to work across all styles? 2) Are there any edits you would recommend to the above typescript template? Once we're clear on this, will update this quite obsolete page: https://wiki.contextgarden.net/Bold_small_caps Thank you in advance. Best wishes Idris PS Sometimes these inquiries may appear more verbose than needed. That is because I'm trying to write as clearly as possible, not only for the experts and masters, but also for beginners and intermediate users who may run into these things one day, search the archives, etc.. -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

3 7

[ export to svg ]
by vm 19 Aug '23

19 Aug '23

Is there a (simple) way to export the results of a \startMPpage ... \stopMPpage directly to a svg file? My current route is to import the pdf into inkscape, group path objects by stroke color, then save the result as svg and translate that into a hpgl format for the pen plotter. I guess/hope there is some hidden switch dumping the MPpage directly into a hpgl file ;-) .Floris

2 2

Enable interaction on custom apa cite variant
by Jethro Djan 19 Aug '23

19 Aug '23

Hi, I would like a variant of cite per the APA specification that removes the bracket when quoted in mathematical definitions, theorems, etc. I could of course do it manually for reach using right= and left= but I didn't want to do it every time. I have come up with this MWE: \startbuffer[ref] @book{burago2022course, title={A course in metric geometry}, author={Burago, Dmitri and Burago, Yuri and Ivanov, Sergei}, volume={33}, year={2022}, publisher={American Mathematical Society} } \stopbuffer \setupinteraction[state=start, color=blue] \setupcolors[state=start] \usebtxdataset[ref.buffer] \usebtxdefinitions[apa] \definebtx [apa:cite:theorem] [apa:cite] \startsetups btx:apa:cite:theorem \btxflushauthorname{author} \btxcomma \btxflush{year} \fastsetup{btx:cite:righttext} \stopsetups \setupenumeration[ before={\blank[medium]}, after={\blank[medium]}, alternative=serried, right=, headcommand=\groupedcommand{}{.}, distance=0.5em, width=fit, headstyle=bold, titlestyle=bold, way=bytext, conversion=numbers, prefix=chapter, list=all, title=yes, indentnext=no, ] \defineenumeration[definition][ text=Defintion, style=normal, number=no, ] \starttext \startdefinition{\cite[righttext={{ p.\nbsp 1}}, alternative=theorem][burago2022course]} This is something \stopdefinition \startsubject[title={References}] \placelistofpublications \startsubject \stoptext The problem with this is that the citation is not interactive like it would be if I used apa:cite:authoryear and just removed the parentheses in the options. How do I get it to highlight blue and be interactive like the default behaviour when you turn on interaction? Also this is probably overkill so if there is a better way to achieve this... Jethro

1 0

An error which is not in .log file
by Xavier B. 19 Aug '23

19 Aug '23

After trying to compile a long file with LMTX (previously with MKIV all compiles perfectly), I get an error structures > bookmark: Referències structure > sectioning > chapter @ level 2 : 0.1 -> Referències publications > list > collecting entries using method 'global' and sort order 'default' pages > flushing realpage 296, userpage 294, subpage 296 structures > bookmark: Índex alfabètic structure > sectioning > chapter @ level 2 : 0.2 -> \headtext {index} pages > flushing realpage 297, userpage 295, subpage 297 structures > end of sectionblock 'backpart' close source > level 1, order 147, name './ng-exercicis.conTeXt' (\end occurred inside a group at level 8) 8:0: semisimple group entered at line 276: \begingroup 7:0: semisimple group entered at line 5: \begingroup 6:0: semisimple group entered at line 5: \begingroup 5:0: semisimple group entered at line 114: \begingroup 4:0: semisimple group entered at line 114: \begingroup 3:0: semisimple group entered at line 5: \begingroup 2:0: semisimple group entered at line 5: \begingroup 1:0: semisimple group entered at line 27: \begingroup 0:0: bottomlevel mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua mkiv lua stats > used cache path: /home/xan/bin/context-current/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e mkiv lua stats > resource resolver: loadtime 0.004 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 240 found files, scanned paths: <none> mkiv lua stats > stored bytecode data: 512 modules (0.181 sec), 105 tables (0.010 sec), 617 chunks (0.191 sec) mkiv lua stats > traced context: maxstack: 1715, freed: 2, unreachable: 1713 mkiv lua stats > cleaned up reserved nodes: 85 nodes, 11 lists of 671 mkiv lua stats > node memory usage: 291 attribute, 62 dir, 91 glue, 3281 gluespec, 1 glyph, 1 hlist, 1 kern, 2 math, 645 mathspec, 4 penalty, 18 rule, 2 temp, 66305 whatsit mkiv lua stats > node list callback tasks: 16 unique task lists, 18 instances (re)created, 119367 calls mkiv lua stats > h-node processing time: 0.653 seconds including kernel mkiv lua stats > attribute processing time: 0.119 seconds front- and backend mkiv lua stats > driver time: 0.693 seconds mkiv lua stats > used backend: pdf mkiv lua stats > jobdata time: 0.054 seconds saving, 0.000 seconds loading mkiv lua stats > callbacks: file: 69204, saved: 309548, direct: 957, function: 244605, value: 7598, message: 0, bytecode: 617, late 0, total: 632529 (0 per page) mkiv lua stats > randomizer: initialized with value 0.45060333164985 mkiv lua stats > v-node processing time: 0.259 seconds mkiv lua stats > loaded tex modules: 4 requested, 1 found (*-tikz), 3 missing (*-pgfmat *-pgfmath *-pgfrcs) mkiv lua stats > loaded patterns: ca::65 en::1, load time: 0.000 mkiv lua stats > interactive elements: 74 references, 950 destinations mkiv lua stats > loaded fonts: 13 files: latinmodern-math.otf, lmmono10-regular.otf, lmroman10-bold.otf, lmroman10-italic.otf, lmroman10-regular.otf, lmromancaps10-regular.otf, lmromanslant10-regular.otf, lmsans10-bold.otf, lmsans10-boldoblique.otf, lmsans10-regular.otf, texgyreschola-bold.otf, texgyreschola-math.otf, texgyreschola-regular.otf mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 68 instances, 51 shared in backend, 8 common vectors, 43 common hashes, load time 1.181 seconds mkiv lua stats > body font sizes: defined: 10pt 11pt 12pt 14.4pt 17.3pt 20.7pt 4pt 5pt 6pt 7pt 8pt 9pt, undefined: 11.2pt 12.8pt 14pt 16.8pt 16pt 19.2pt 24pt 30pt 36pt mkiv lua stats > metapost: 0.000 seconds, loading: 0.033, execution: 0.000, n: 3, average: 0.011, instances: 1, luacalls: 14196 (file: 13784, text: 0, script: 393, log: 19), memory: 3.881 M mkiv lua stats > math tweaking time: 0.474 seconds, 84 math goodie tables mkiv lua stats > math processing time: 0.292 seconds mkiv lua stats > graphics processing time: 1.768 seconds including tex, 268 processed images, 57 unique asked, 27 bad names mkiv lua stats > publications load time: 0.005 seconds, 2963 bytes, 11 definitions, 0 shortcuts mkiv lua stats > pdf annotations: 74 links (74 unique), 0 special mkiv lua stats > font embedding time: 0.018 seconds, 13 fonts mkiv lua stats > result saved in file: ng-exercicis.pdf, compresslevel 1, objectcompresslevel 3 mkiv lua stats > positions: 311 collected, 0 deltas, 307 shared partials, 133 partial entries mkiv lua stats > cross referencing: 713 identified, 269 unknown mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64 mkiv lua stats > used engine: luametatex version: 2.10.10, functionality level: 20230803, format id: 697, compiler: gcc mkiv lua stats > tex properties: 806417 hash slots used of 2097152, 70025 control sequences, approximate memory usage: 82 MB mkiv lua stats > lua properties: engine: lua 5.4, used memory: 213 MB, ctx: 198 MB, max: 306 MB, symbol mask: utf (τεχ) mkiv lua stats > runtime: 20.941 seconds, 297 processed pages, 297 shipped pages, 14.183 pages/second mtx-context | fatal error: return code: 1 but this not appear in .log file. What can I do for seeing what happens? Thanks in advance, Xavier PS: I could share my sourcecode with public git repo if you prefer.

6 15

Some very simple cld - loading a module
by Hamid,Idris 18 Aug '23

18 Aug '23

Dear gang, The following, simple MWE gives an undefined control sequence error: ======= % \usemodule[translate] % \enableinputtranslation \startluacode -- context.usemodule({translate}) context.usemodule{translate} context.enableinputtranslation() context.darkgreen() \stopluacode \startTEXpage[offset=1em] \translateinput[Hermes][Idris] Hermes \disableinputtranslation Hermes \stopTEXpage ======= tex error > tex error on line 14 in file ./test-luacode.tex: Undefined control sequence <line 3.12> \translateinput [Hermes][Idris] ======= The reason for the error is that the module is not being loaded. Toggling back to context syntax, of course, works. Reference: ConTeXt Lua Documents by Hans Hagen, page 22. The following analogous code works: \startluacode context.startchapter{first} \stopluacode So how do we properly load the module from within a luacode environment? Thank you in advance. Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

2 2

Table head/body via lua
by Alexey Kryukov 18 Aug '23

18 Aug '23

Hi, I am trying to generate a table representation for some xml source. As the data structure doesn't directly correspond to the desired table structure, some manipulations via lua are required. So far everything works OK except table sectioning commands, like \bTABLEhead, \eTABLEhead, bTABLEbody or \eTABLEbody: it seems impossible to incapsulate them into lua functions. For example, the following is not compiled: \starttext \bTABLE \ctxlua{context.bTABLEbody()} \bTR \bTD Cell 1\eTD \bTD Cell 2\eTD \eTR \ctxlua{context.eTABLEbody()} \eTABLE \stoptext Can anybody suggest a workaround (except changing the source XML of course)? -- Regards, Alexey Kryukov <anagnost at yandex dot ru> Moscow State University Faculty of History

2 4

Re: Experiments with \doloopoverlist
by Andres Conrado Montoya 18 Aug '23

18 Aug '23

I was using an old LMTX copy, and that was the issue. Thanks to Hans for pointing that out. Now I'm trying to expand my solution a little more. Is there any way to retrieve an element in a dataset by using the key? For example, given an "authors" dataset, I would like to do something similar to: %% Given this data structure ... \setdataset[authors][ nombre={Andrés Conrado Montoya Acosta}, bio={This is a bio, it could be two or three paragraphs long}, email={loremipsum(a)email.edu.co}, cvlac={ https://scienti.minciencias.gov.co/cvlac/visualizador/generarCurriculoCv.do… }, orcid={https://orcid.org/0009-0007-0765-4241}, gscholar={ https://scholar.google.com/citations?user=GpYTTU0AAAAJ&hl=es&authuser=1}, ] %% I want to do something like.... \startGetAuthor[nombre={Andrés Conrado Montoya Acosta}] \datasetentry{bio}\par email: \mailhref{\datasetentry{email}} \stopGetAuthor So, if my name is found in the dataset, get the data for that name. Is something like that possible? Thank you for your time. -- 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

1 0

Re: breakpoints in verbatim text
by Hans Hagen 18 Aug '23

18 Aug '23

On 8/18/2023 1:02 PM, Wolfgang Schuster wrote: > Alex Leray schrieb am 18.08.2023 um 12:19: >> Hello Wolfgang, >> >> Le 17/08/23 à 18:56, Wolfgang Schuster a écrit : >>> Is it correct all your listing are HTML code and you need line breaks >>> for the entries of the href attributes? >> >> The content is from a dutch net-artist artist from the early days of >> the public web, and is often (volontary) mixing different natural nd >> machine langages. Not all snippets are HTML, but most of them are some >> sort of HTML pidgin. > > > I see, the typing environment is in this case the safest option to > ensure special characters like % remain i the output. > > For simple text without special characters you could have switched to > the lines environment and use a monospaced but > I wouldn't trust it here (even when you enable \asciimode). > > >>> Syntax highlighting of the code listing isn't needed in your case. >> >> No, I don't need syntax highlighting >> >> My problem is solved using manual zero width spaces at the moment but >> I'd be interested to find a more structural solution. >> >> Checking at the Context source code I would have thought that >> breakpoints were possible withing typing env. See >> >> https://source.contextgarden.net/tex/context/base/mkiv/buff-ver.mkiv?search… >> >> It would be interesting to document on the wiki that behavior, which I >> can do later when my understanding is better. > > The typing environment disables the breakpoint (and a few other) > mechanism because they can lead to undesired > side effects but Hans suggestion to provide a hook which can be used to > re-enable the feature, e.g. > > \startsetups [typing:mine] > \setbreakpoints[compound] > \stopsetups > > \setuptyping [CUSTOM] [setups=typing:mine] > > The only flaw I can see in the suggestion is the use of the > \everyinitializeverbatim register because it is used for > inline and display verbatim. A better place to add the option is > \buff_verbatim_initialize_typing_two for \starttyping > and \buff_verbatim_initialize_type_two for \type. ok -- ----------------------------------------------------------------- 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 0