- ntg-context - Mailing Lists

ToC filler dots/leaders not aligned in LMTX
by Schister, Roman 23 Apr '21

23 Apr '21

Hello everyone I’m trying to typeset a table of contents with filler dots (list alternative C) in LMTX. Unfortunately, the dots are not vertically aligned and do not end flush on the right-hand side. If I try to use leaders in a paragraph, I get the same behaviour: the leading dots are not aligned. Compiling the same document with MkIV leads to correct alignment of the filler dots in both instances. Here is an MWE: \setuplistalternative[c][width=2em] \starttext \completecontent[alternative=c] \chapter{Short title} Lorem ipsum \hskip.5em\gleaders\hbox to .5\emwidth{\hss.\hss}\hfill\hskip.5em\relax dolor sit amet. \par Lorem \hskip.5em\gleaders\hbox to .5\emwidth{\hss.\hss}\hfill\hskip.5em\relax ipsum dolor sit amet. \chapter{Slighlty longer title} \chapter{Not so long title} \stoptext Are there any changes in LMTX that I need to take into account when typesetting a ToC/leaders? Any help is much appreciated. Thank you! Roman

2 1

setupalign[height] vs setupalign[line] in MKIV
by denis.maier＠ub.unibe.ch 23 Apr '21

23 Apr '21

Hi, I've noticed a somewhat unexpected behaviour. MWE below. \setupalign[line] adds an enormous amount of whitespace to fill a last page, but \setupalign[height] doesn't. Is that intended ? Currently this only happens with mkiv. As stated in another mail, these options seem to have no effect at all under LMTX. Best, Denis \setuppapersize[A5][A5] \showframe \setupdelimitedtext[blockquote] [before={\switchtobodyfont[small]}, spacebefore={medium,flexible},] \starttext \setupalign[line] % this here causes the last page to be filled \section{A section heading} \input knuth\par \page \setupalign[height] %this here doesn't \section{A section heading} \input knuth\par \stoptext

1 0

Page building and vertical stretching
by denis.maier＠ub.unibe.ch 22 Apr '21

22 Apr '21

Hi, in addition to my previous mails about \setupalign[height], a further question related to page building : I'm trying to understand how ConTeXt builds pages, and how this can be influenced. Regarding the example below, the aim is to have pages that always end at the same place. Now, how will ConTeXt use stretching? Blanks are set to flexible, and the interlinespacing is set to stretch. (But different values for blockquotes.) In which order will ConTeXt proceed? Interlinespacing first, then blanks? Or the other way round? Or both at the same time? And, can this be influenced somehow? Best, Denis \setuppapersize[A5][A5] \showframe \setupblank[big,flexible] \setupinterlinespace[stretch=0.03] \setuptolerance[vertical,stretch] \setupalign[height] \setuphead [section,subject] [ before={\blank[2*big,flexible]}, after={\blank[big,flexible]}, ] \setupdelimitedtext[blockquote] [ before={\tfx\setupinterlinespace[stretch=0.05]}, spacebefore={medium,flexible}, left= ] \starttext \input knuth \section{A section heading} \input knuth\par \blank \input knuth\par \startblockquote \input knuth\par \stopblockquote \input knuth\par \startblockquote \input knuth\par \stopblockquote \input knuth\par \stoptext

1 0

Change to wordright behavior?
by Rik Kabel 21 Apr '21

21 Apr '21

Dear all, At some time in the last couple of years the behavior of \wordright seems to have changed, at least in the following situation. With the following example: \starttext \hsize3cm Aaa\wordright{Aaa}\par \sc{Bbb\wordright{Bbb}}\par {\sc Ccc\wordright{Ccc}}\par \sc{Ddd}\wordright{\sc{Ddd}}\par \stoptext Produces: The second and third lines with \wordright (Bbb and Ccc) each generate two lines. They previously produced one line each. Placing each part of the line in its own \sc addresses it here (Ddd), but it does seem that it should not be necessary to do that. Was this an intentional change? -- Rik

1 1

next upload
by Hans Hagen 21 Apr '21

21 Apr '21

Hi, The *next* upload will have the following change. For a long time in mkiv and also lmtx, the tex habit of turning -- and --- into endash and emdash has been handled at the font level by a injecting a font feature. This works okay. This tlig feature is currently part of the defaults but that will change. If you want to retain that, you can add this to a cont-loc.mkxl file \definefontfeature [default] [default] [tlig=yes, trep=yes] but it should not be needed (and only introduces overhead). When it's a font feature it kicks in after hyphenation but because we're in the process of enhancing that, this traditional -- and --- replacement now kicks in before hyphenation. It can be disabled by \nohyphencollapsing, which actually happens in for instance verbatim and it can be applied locally if needed. There might be places where you expect this to happen so let me know if I missed these. The (intended) effect is that somefirst- and secondpart\blank firstpart\char"002D secondpart\blank firstpart---secondpart\blank firstpart\char"002D\char"002D secondpart\blank firstpart\char"002D\char"002D\char"002D secondpart\blank firstpart\char"2010 secondpart\blank firstpart\char"2013 secondpart\blank firstpart\char"2014 secondpart \type{firstpart---secondpart} all work as I expect (both words get hyphenated). The trep feature was already stripped to only ' replacment but in these unicode times that artifact has no place. We anyway expect users to use \quote and \quotation as it's a language dependent feature. You can of course enable it any time, but it will no longer be default, just like " already gives an upright double quote, and `` was never enabled in mkiv, from now on ' will give a single upright quote. So, when this is uploaded, keep an eye on it and let me know where things misbehave, you're warned, 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 -----------------------------------------------------------------

1 0

xml processing in latest
by Thomas A. Schmitz 21 Apr '21

21 Apr '21

Hi all, the latest has some strange problems with xml processing. The example below shows an issue with itemize. In my real file, I also get pages that are filled only two thirds and rugged right instead of justified, but I haven't been able to reproduce this in a MWE. Maybe this one can give a start; I assume it's some fundamental typo somewhere. All best Thomas \startbuffer[test] <document> <p>test</p> <numbered> <item> one </item> <item> two </item> </numbered> </document> \stopbuffer \startxmlsetups xml:testsetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{document|p|numbered|item}{xml:*} \stopxmlsetups \xmlregistersetup{xml:testsetups} \startxmlsetups xml:document \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:p \xmlflush{#1} \par \stopxmlsetups \startxmlsetups xml:numbered \startitemize [n] \xmlflush{#1} \stopitemize \stopxmlsetups \startxmlsetups xml:item \startitem \xmlflush{#1} \stopitem \stopxmlsetups \starttext \xmlprocessbuffer{main}{test}{} \stoptext

2 3

\processassignmentlist inside a \setup... or related
by Jairo A. del Rio 20 Apr '21

20 Apr '21

Hi, list! I hope my example shows clearly enough what I intend to do: \startluacode userdata = userdata or {} userdata.mydata = {} local function registermydata(data,...) table.insert(userdata.mydata, data) end interfaces.implement{ name = "registermydata", arguments = "2 strings", actions = registermydata } \stopluacode \unprotect \def\mysetups[#1]% {\getdummyparameters[#1]% \processassignmentlist[#1]\clf_registermydata} \protect \starttext \mysetups[love=nice,hate=awful]% \dummyparameter{love} \cldcontext{userdata.mydata[2]} \stoptext What I want to know is if there's a less hackish way to pass keys (yep, only keys, not values) to Lua using \getdummyparameters (actually I'm using an user-defined \setupsomething, but it's more or less the same) and \processassignmentlist. Is it possible, for instance, to automatically pass a key to Lua when it's set in \setupsomething? Thanks in advance. Jairo PS: Sorry if I missed something in the test suite again

2 3

\frac error
by thierry horsin 19 Apr '21

19 Apr '21

Hi everybody Since I updated to the last version of context , I cannot use \frac anymore in \startformula. I get the following message "I can't work with sizes bigger than about 19 feet. Continue and I'll use the largest value I can." Yet, between $ $ it is fine. Any ideas ? Many thanks.

2 5

context() does not ignore space in empty line
by Sylvain Hubert 19 Apr '21

19 Apr '21

Dear list, does anyone have an idea why, in the example below, context() starts a new paragraph at "\n\n" but not at "\n \n" with a space in between? Is there any way to fix it? \starttext Without using context(), inside the next parentheses is a new line: ( ) note that a space sits between the two line breaks. \startluacode context('Using context(), inside the next parentheses is also a new line: (\n\n) because there is *no* space between the two line breaks.\n\n') context('Using context(), inside the next parentheses is however *no* new line: (\n \n) because of the space between the two line breaks.\n\n') \stopluacode \stoptext Any help is appreciated. Best, Sylvain

2 1

Analyze hyphenations
by denis.maier＠ub.unibe.ch 18 Apr '21

18 Apr '21

Hi, a couple of weeks ago Hans has implemented a tracker that adds a list of hyphentated words to the log file. I finally managed to play with this. The result is attached to this mail. This will permit analyzing hyphenations based on a ConTeXt log file. You need to enable hyphenation tracking in the ConTeXt file with \enabletrackers[hyphenation.applied]. Then, you can run the script with lua check-hyphens.lua input_file whitelist.ending As we assume .log for the input_file, the input file should be supplied without file ending. For the (optional) whitelist a file ending has to be supplied. Maybe I should wikify this, any suggestion where that would fit? HTH, Denis

1 0