March 2022 - ntg-context - NTG Mailing Lists

Make footnote/endnote number not superscript?
by Bruce Horrocks 21 Mar '22

21 Mar '22

I'm editing a book that will be printed, however the authors have included URLs which will no doubt suffer from "bit rot" in no time at all. I think it will make the main text cleaner if I use endnotes rather than include the URL in-line in the text or as a (distracting) footnote. So when the author writes "See my video at <long Youtube URL>" I will print "See my video at link 1". At the back of the book, in an appendix somewhere, I then use \placenotes to display a table of the actual URLs for any readers that want to type them in. I want the "link 1" bit to be normal text rather than superscript so it's more visible. Using the \setupnote[textstyle=...] command I can change the style of the number but not the superscript placing. Is there a way to remove the superscript placing, please? Alternative solutions welcome: the URLs printed in the book will be mirrored on a web page associated with the book for as long as possible so that content that vanishes over time can be replaced with Internet Archive links as they are discovered. However the order of the book isn't finalised yet so I'd like the numbering to be sequential regardless of whether I move a chapter around later on. This is partly the reason for using \endnote because I can use a reference elsewhere in the text if necessary. Thanks in advance. — Bruce Horrocks Hampshire, UK

5 5

Small bug in publ-imp-aps.mkvi
by Jack Hill 21 Mar '22

21 Mar '22

Hi everyone, Just letting you know that there is an extra . (full stop) on the end of lines 732 and 734 of publ-imp-aps.mkvi which causes references to be typeset like "p.. 417" and "pp.. 417--418". Thanks, Jack

1 0

Metafun, difficulty with graphical element in the margin
by Willi Egger 21 Mar '22

21 Mar '22

Good evening! I have a dictionary where I would like to include thumb-pictures in the margin. — When I use the attached code with a single \startchapter...\stopchapter, it works. However if I add another \startchapter…\stopchapter before loading the setups for the thumb-picture metafun throws an error about not having complete information for performing a transformation. I am currently using the before last version of LMTX-ConTeXT (January 21st 2022). Could someone try to compile? Thanks, kind regards Willi

5 12

\setupheadertexts for chapters with different authors
by jbf 20 Mar '22

20 Mar '22

I thought this should work, since \structurelistuservariable{author} works fine to call the author name into the TOC, but the same does not work for header texts it seems: \setupheadertexts [{\hfill\getmarking[\structurelistuservariable{author}]\hfill}][] [{\hfill\documentvariable{metadata:title}\hfill}][] But it doesn't. What am I doing wrong? Julian

3 8

Metafun, difficulty with graphical element in the margin, again.
by Willi Egger 19 Mar '22

19 Mar '22

Hello, I am a little desperate… I have installed in a new directory the latest version of ConTeXt. I run the sample file I provided before. After enabling a second chapter-section before the \setups{Thumb-picture} the metafun error reoccurs. — Looking at the log I do net get really wiser, lacking the background of the implementation… So here follows the section of the log with the error: metafun > log > metafun > log > error: Transform components aren't all known metafun > log > metapost > trace > <error> (0,0,mfun_page_hsize[-4],0,0,1) metapost > trace > <to be read again> yscaled metapost > trace > <for(-4)> mfun_page_field [ (EXPR 0) ] [ (-40) ] := unitsquare xscaled mfun_page_hsize [ (EXPR 0) ] yscaled mfun_page_vsize [ (-40) ] shifted ( mfun_page_hstep [ (EXPR 0) ] , mfun_page_vstep [ (-40) ] ) ; mfun_page_field [ (-40) ] [ (EXPR 0) ] := mfun_page_field [ (EXPR 0) ] [ (-40) ] ; ENDFOR metapost > trace > <for(-40)> for HorPos = LeftEdge step 1 until RightEdge : mfun_page_field [ HorPos ] [ (EXPR 0) ] := unitsquare xscaled mfun_page_hsize [ HorPos ] yscaled mfun_page_vsize [ (EXPR 0) ] shifted ( mfun_page_hstep [ HorPos ] , mfun_page_vstep [ (EXPR 0) ] ) ; mfun_page_field [ (EXPR 0) ] [ HorPos ] := mfun_page_field [ HorPos ] [ (EXPR 0) ] ; endfor ; ENDFOR metapost > trace > <macro> mfun_check_page_field -> -> mfun_check_page_dimensions;for.VerPos=Top.step10until.Bottom:for.HorPos=LeftEdge.step1until.RightEdge:mfun_page_field[HorPos][VerPos]:=unitsquare.xscaled.mfun_page_hsize[HorPos]yscaled.mfun_page_vsize[VerPos]shifted(mfun_page_hstep[HorPos],mfun_page_vstep[VerPos]);mfun_page_field[VerPos][HorPos]:=mfun_page_field[HorPos][VerPos];endfor;endfor; metapost > trace > <argument> mfun_check_page_field ; metapost > trace > <macro> hide -> (TEXT0)-> exitif.numeric.begingroup(TEXT0);endgroup; metapost > trace > <macro> Field -> -> hide(mfun_check_page_field;)mfun_page_field metafun > log > metafun > log > I'm unable to apply a partially specified transformation except to a fully known pair or transform. Proceed, and I'll omit the transformation. metafun > log > How to interprete, wha tto try next? Kind regards Willi

1 0

Tex capacity exceeded...
by jbf 17 Mar '22

17 Mar '22

Thanks Hans, and Rik. Perhaps I need to take a much closer look at this file to see if I have created some grouping issues. The removal of the .tuc file is a very handy tip that I hadn't thought of, and I assume it is associated with the way Hans put it, namely, 'looks like you load the same file...' Julian

1 0

TeX capacity exceeded.... but....
by jbf 17 Mar '22

17 Mar '22

I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. Julian

3 2

Calling in chapter number in list={}
by jbf 17 Mar '22

17 Mar '22

I wonder if there is a way I can call in the chapter number in the TOC, although that number is not used for chapters as such. I know the chapter number is 'remembered' anyway, so there is probably a way I can call it in just for the TOC. The context for this question is the layout for book which comprises individual contributions, and each contribution has its own author/copyright (hence the individual chapters bear a title without a number, but the editor who has compiled these wants them numbered in the TOC). I currently call the author name in the TOC with: \define[1]\SectionTocEntry{% \leftaligned{#1}\par% title. \leftaligned is needed \hskip1cm\relax\doifnot{\structurelistuservariable{author}}{}{\structurelistuservariable{author}}% } \setuphead[chapter] of course includes number=no. \setuplist[chapter] is currently set as: [label=yes,distance=1.2cm,style=normal,before=\blank,after=\blank,textstyle=normal,alternative=c,textcommand=\SectionTocEntry,] And for the moment I simply use, as part of the \startchapter[] description: list={1. This is the rather long title of the first chapter, with the number included at the beginning}. While that gives me the number of the chapter, it does not give me correct indentation when the chapter title runs to more than one line. What I would prefer to do is to be able to call the chapter number automatically with placing 1., 2., etc. in list={}. Julian

3 4

Force a hyphenation
by Willi Egger 17 Mar '22

17 Mar '22

Hi, at the moment I am dealing with a German text. Although I have \mainlanguage[de] in the preamble the word 'des Eiweißes' is hyphenated as 'des Eiwei-ßes'. Of course this should be 'des Eiweis-ses'. How can I make sure that ConTeXt is hyphenating this corerctly? Kind regards Willi

5 5

new upload
by Hans Hagen 16 Mar '22

16 Mar '22

Hi, It has been a while since there was an updaste but there it is. The most significant 'changes' are: - more automatic adaption to double sided page properties in metafun (lmtx) ... blame sreeram and me for messing up - more extensibve support for indic fonts which sreeram has documented on the wiki (fonts, translutaration etc) and - improved math rendering to be documented by by mikael in an upcoming manual ... it tooks a couple of months so it is supposed to have some impact. before we move on the the structural compoments and see what can be done beter there, we decided to release the first stage that deals with: = fixing font properties; we don't expect fonts to be improved so that's the route we follow = extensive inter atom spacing (we have many more math classes, some in the engine, some in context) and everything can be controlled (the old pairwise spacing primitives have been replaced by a more general mechanism, including support for fast setup of categories and inhertance from other classes) = idem for inter class penalties, including granular control over line breaks using a system of (in/de)creasing penalties = auto-fenced inline material across lines and linebreaks in molecules (read: complex atoms) = taking stretch and shrink in encapsulated atoms into account in linbreaks (using some new box related mechanism that is also available in text and will be explained later) = spacing at the edges that should not be there but always was there as side effect of the engine is now removed; as with other new features this can be controlled (we have rulesets for atoms to which we can add more in the future) = more detailed control over (skewed) fractions, (flattened) accents, (sized) fences, radicals ... there was already a lot there but it now combines with mentioned spacing (when relevant the context macros have been adapted to control this which is a bit cleaner) = we have a new built in muskip (tiny) but as we have an inheritance system as well as binding to variables one can set up extensive spacing models register and constant binding; the currently set values are based on math typesetting references; in the future we might have additional ones = although we did handle primes already rather transparent in mkiv / lmtx, inconsistency in fonts made us decide to make primes first class properties of atoms and molecules which means that we now have: pre super/subscripts, post super/subscripts and primes; this permits nicer anchoring under parameter control = there are more font parameters to control matters (they are not in open type but we sort of assume they are); the options that we had to control how the engine deals with fonts are now driving the process (without them being set not much is applied) and we basically assume open type fonts (where one can enable engine options for those kind of fonts but also for traditional); some experimental options for testing are gone = in the process tracing for what is done in math by the engine has been extended (mostly for ourselves) = instead of auto patching math fonts most is now under control of the goodie files; user can (as usual) make their own, but also ask Mikael to add missing bits and pieces (wrt dimensions) = most known math fonts are dealt with but there are a few exceptions: we no longer consider asana to be useful (it doesn't pass our qa and needs too much patching); erewhon is also troublesome (dimensions, missing shaped) as is concrete (idem) so we decided not to waste too much time on them now = we probably need to freeze math fonts in the distribution and only update when we know what has been changed = we got rid of quite some artifacts that normally go unnoticed (like tiny added spaces that result from always applied spacing even if not needed and/or to compensate for glyph features like too much or little side bearing): by fixing inconsistencies in fonts we could get rid of all and therefore inter atom spacing is what does the job; once you know it, you see it and there is no going back = because we zoom in we notice these things but much went unnoticed (or was just accepted) for years; it means that we think some of the things we did qualify as math micro typography (like it or not) and it does mean that documents can render differently (unlikely for display, propably also for inline unless you have plenty of math in a paragraph) == our objective has been to make it easier for users and to get rid of explicit spacing; for that we also introduced commands for differentials (that have their own class), imaginary numbers (also have their class) and we added exponential as class; fwiw, digits and factorial are classes too so again spacing has been optimized for them = whatever i forgot in the meantime mikael will add to this list There is a rough description in the 'ontarget' document. We hope you enjoy it, at least we did (and so, as we're not finished yet). 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 -----------------------------------------------------------------

10 25