- ntg-context - NTG Mailing Lists

Skipped figure numbers
by Aidan Nichol 30 Mar '16

30 Mar '16

I have been looking at various options for controlling how figures are placed on a page and based on answers to similar questions in this mailing list I tried various options. The most flexible one seems to be using tables e.g. \setupexternalfigures[location={default}] \starttext \placefigure[]{}{\externalfigure[hacker][height=1in]} \startxtable[frame=off,align=low] \startxrow \startxcell[ny=2] \placefigure[force][]{left twoup}{\externalfigure[mill][height=4in]} \stopxcell \startxcell \placefigure[force][]{the first}{\externalfigure[spider][height=1.5in]} \stopxcell \stopxrow \startxrow \startxcell \placefigure[force][]{the second}{\externalfigure[cow][height=1.5in]} \stopxcell \stopxrow \stopxtable It seems to work well except that figure numbers are being skipped. In this example hacker=1 mill=8, spider=9 and cow=10. Varying the contents of the table reveals that It is skipping two times the number of figures in the table. Is this an invalid combination of features I’m using or am I doing something wrong?

2 1

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 30 Mar '16

30 Mar '16

On 3/30/2016 9:23 PM, Jan Tosovsky wrote: > On 2016-03-26 Hans Hagen wrote: >> >> I added final|2*final|3*final|4*final >> >> where final is a hspace of one em by default >> >> the only purpose of this feature is to ensure a gap at the end (handy >> when there is no indentation) >> > > Does this settings just set \parfillskip XX plus 1fil or there is more complex magic in the background? no magic > I'd like to extend a description here: > http://wiki.contextgarden.net/Paragraph_last_line_control > > Anyway, this related issue could be closed now: > > http://tracker.luatex.org/view.php?id=885 > > Thanks, Jan > > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] Protrusion cancellation by index term
by Hans Hagen 30 Mar '16

30 Mar '16

On 3/21/2016 10:59 PM, Jan Tosovsky wrote: > On 2014-02-23 Hans Hagen wrote: >> On 2/22/2014 2:38 PM, Jan Tosovsky wrote: >>> On 2014-02-22 Jan Tosovsky wrote: >>>> >>>> when a punctuated phrase appears at the beginning of the line, >>>> it is not protruded correctly when preceded by an index term. >>>> >>>> ... \index{foo}>Bar< ... >>>> >>>> A minimal example is available at >>>> http://drifted.in/other/sample.tex >>>> >>>> I cannot place the space character between these two parts >>>> (which helps) as I sometimes need to join this and the previous >>>> phrase with the non-breaking space. >>>> >>> >>> It is more serious issue than expected. Consider next two >>> variants: >>> >>> (1) sentence, \index{primary}>Primary< >>> (2) sentence,\index{primary} >Primary< >>> >>> When the line is broken after a comma: >>> ad 1) starting guillemet is not protruded >>> ad 2) ending comma is not protruded >>> >>> When \index is surrounded by spaces from both sides, the space is >>> rendered at the beginning of the next line (resulting in >>> 'indenting'). >>> >>> I'd be grateful for ignoring any non document content preceding >>> punctuation to avoid its influence on protrusion. >> >> well, think of it like this: >> >> [something]<text>[something else] >> >> with [something] being bound to < ... so that is then the boundary of >> the word, not < ... i might know a solution (but such -major- changes >> have to fit into my schedule) > > are there any improvements here with revamped token processing implemented > in recent versions? it's not that trivial - for the index we can cheat a bit but then i also need to check lots of other cases for possible interference - for the footnote case there is no real solution as the heuristics of finding a protrusion character cannot be tricked too much without breaking it in other cases but ... i think i can cook up something extra in the engine to drive the process; i'll play with it but again. it will take a lot of testing so it will then probably be an option for a while Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 30 Mar '16

30 Mar '16

On 3/25/2016 10:57 PM, Jan Tosovsky wrote: > On 2016-03-25 Hans Hagen wrote: >> On 3/25/2016 2:40 PM, Jan Tosovsky wrote: >>> On 2016-03-24 Hans Hagen wrote: >>>> On 3/24/2016 8:36 PM, Jan Tosovsky wrote: >>>>> >>>>> We basically need: >>>>> <text><glue min-width='XX' max-width='hsize-3*indent'> >>>>> >>>>> and I thought this is exactly what \parfillskip ensures >>>>> \parfillskip XX plus (hsize - 3*indent) >>>>> >>>> >>>> the fil is taken into account when calculating the best break >>>> points and then the XX is fixed but plus/minus can lead to if >>>> being less or more, all relative to other fill (distributed) >>>> >>>> so, XX plus (hsize - 3*indent) is not a fixed value, it's XX or >>>> more >>>> >>>> take this: >>>> >>>> \ruledhbox to 10cm {x\hskip0pt plus 1cm x} >>>> >>>> the skip will stretch more than 1cm >>> >>> I can see. >>> >>> But sorry for my ignorance, as far as I understand, \parfillskip >>> is added to the end of the paragraph, so we have rather >>> \ruledhbox to 10cm {x\hskip0pt plus 1cm} % without that 'x' at the >>> end, so no 'glue' distribution is performed >> >> there is but not enough stretch so there will be a warning ... you >> can see it from >> >> \ruledhbox to 10cm {x} >> \ruledhbox to 10cm {x\hskip0pt plus 1cm} >> \ruledhbox to 10cm {x\hskip0pt plus 1fill} >> > > I get it, thanks. > >>> If '\parfillskip 2em plus (hsize - 3*(2em) - 2em)' is specified, I >>> still think we should get space of width at least 2em '####' which >>> can be extended as indicated by hyphens '-' here: >>> >>> emememememememememememememememememememem >>> emememememem------------------------#### >>> >>> So there are two last line lengths extrems: >>> (shortest) >>> emememememememememememememememememememem >>> emememememem >>> >>> (longest) >>> emememememememememememememememememememem >>> emememememememememememememememememem >> >> you always add a 2em skip so there will never be a word touching the >> right margin in the last line; > > yes, but this is my goal (!) > > See https://mailman.ntg.nl/pipermail/ntg-context/2016/084858.html - case (2) > > I am afraid I hasn't been clear enough yet. > > >>> Can I somehow define command globally which takes local block widths? >>> >>> \parfillskip #1 plus \localhsize-#1-#2, where >>> #1 gap width >>> #2 shortest line width >> >> \availablehsize >> > > > So the following \parfillskip specification finally seems to be what I was looking for as it covers both cases in my original question: > > \setupindenting[yes,2em] > > \newdimen\lastlineminlength > \newdimen\lastlinemingap > > \lastlineminlength=3em > \lastlinemingap=1em > > \parfillskip \lastlinemingap plus \dimexpr\availablehsize-\lastlineminlength-\lastlinemingap\relax > > \edef\ward{\cldloadfile{ward}} > > \starttext > > \dorecurse{100}{ > \hsize\dimexpr\textwidth-#1mm\relax > \ward \par > \ward \par > \startnarrower[left] > \ward \par > \ward \par > \stopnarrower > \page > } > > \stoptext try \ward{}okay i.e. a short word at the end and you'll see theh \parfillskip \lastlinemingap plus 1fill works just as well > As it can be done in one place globally and in almost single line, no special new command is necessary (as requested originally). i've removed the one|two|three and added final|2*final|3*final|4*final where final is a hspace of one em by default the only purpose of this feature is to ensure a gap at the end (handy when there is no indentation) for your case i see no solution apart from heuristic lua magic Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 2

Error - font-otj.lua:1503: attempt to perform arithmetic on local 'rightkern'
by Jan Tosovsky 30 Mar '16

30 Mar '16

Dear All, when generating example from http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV I am getting the following error in the latest beta (0.90): error: ...ext/tex/texmf-context/tex/context/base/mkiv/font-otj.lua:1503: attempt to perform arithmetic on local 'rightkern' (a table value) tex error > tex error on line 28 in file D:/db/foot.tex: ? \typo_paragraphs_stop_cell_yes ...dstrut \endgraf \fi \paragraphsparameter \... \stopparagraphscell ->\typo_paragraphs_stop_cell \let \typo_paragraphs_stop_... \stopTwoColumns ->\stopparagraphscell \egroup \paragraphsparameter \c!after ... l.28 \stopTwoColumns 27 \getbuffer[Plato] 28 >> \stopTwoColumns 29 Nothing crucial, just verifying the behaviour in the latest beta. Jan

1 0

Re: [NTG-context] Alignment for narrower text
by Jan Tosovsky 30 Mar '16

30 Mar '16

On 2014-01-30 Jan Tosovsky wrote: > > I'd expect that starting french quote sign outside the left text edge - > similarly like it is aligned the main flow when the hanging feature is > enabled. > > Now I've found it works as expected when the indenting is disabled... > http://tracker.luatex.org/view.php?id=884 After recent improvements I've tested this older issue, but it is still problematic. When that \setupindenting is uncommented, french quote is not hanged. Just updating the status :-) Jan

1 0

help on def & buffer
by Erik Margraf 30 Mar '16

30 Mar '16

Dear List, please help me with my problem here .... I - probably naively - tried the following: ------------------------ \starttext \def\Buffer#1#2 { \startbuffer[#1] \input #2 \stopbuffer } \Buffer{bla}{knuth} \stoptext ------------------------- Context gives me the following error on this: tex error > tex error on line 9 in file C:/Users/emargraf/Documents/buffer.tex: ! Undefined control sequence \Buffer ...startbuffer [#1] \input #2 \stopbuffer l.9 \Buffer{bla}{knuth} ----------------------- Kind regards Erik

4 5

Nested floatcombinations
by Aidan Nichol 30 Mar '16

30 Mar '16

Based on answers to previous questions the easiest way to arrange figures on a page in a simple tabular arrangement is to use \startfloatcombination etc. and indeed works well I wanted to get a single tall figure on the left and two on the right above one another. I tried nesting i.e. \setupexternalfigures[location={default}] \definefloat[floatA][floatAs] \definefloat[floatB][floatBs] \setupcaption[floatA][number=yes,location=top] \setupcaption[floatB][number=no] \starttext \startplacefloatA[title={Using figures in nested float combinations}] \startfloatcombination[nx=2,ny=1] \startplacefigure[title={left two rows}] \externalfigure[mill][height=4in] \stopplacefigure \startplacefloatB \startfloatcombination[nx=1,ny=2] \startplacefigure[title={right top}] \externalfigure[spider][height=1.5in] \stopplacefigure \startplacefigure[title={right bot}] \externalfigure[cow][height=1.5in] \stopplacefigure \stopfloatcombination \stopplacefloatB \stopfloatcombination \stopplacefloatA \stoptext This just gave the three figures in a sort of single column down the page. Are nested floatcombinations not allowed or have I done it wrong?

1 0

adding font feature tnum in the TOC
by Willi Egger 30 Mar '16

30 Mar '16

Hi, hm, I am a little puzzled… If I am correct then one should be able to enable the font feature tnum for the page-numbers with “pagecommand=“. I have \setuphead [section] [aftersection=\page, textstyle=\bfd, numberstyle=\bfd, align=middle, after={\godown[-1\lineheight]}, number=no] \setuplist[section][pagecommand={\addfeature[tnum]#1\subtractfeature[tnum]}] However if I do this then I get the pagenumber prefixed with ‘section’ e.g. bbb bar buch bühne section3 What am I doing in the wrong way? Kind regards Willi

3 9

Re: [NTG-context] Hanging punctuation misalignment in footnotes
by Hans Hagen 30 Mar '16

30 Mar '16

On 3/29/2016 11:07 PM, Jan Tosovsky wrote: > I can't reproduce the original issue in the latest beta (0.90). Was there > something improved in this regard? yes, some improvements in the engine and (so far only in a few places) adaption to that in context > It looks really great! it looks consistent; if it looks 'great' is a matter of taste Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0