- ntg-context - Mailing Lists

[OT] Bash comes to Windows
by Mojca Miklavec 01 Apr '16

01 Apr '16

It seems that we'll have to extend the support of our bash installation script to support Windows: https://www.youtube.com/watch?v=kJGqZHQzNRo (Note that this video was uploaded on 30th March, not the 1st April.) Mojca

2 1

Re: [NTG-context] Skipped figure numbers
by Aidan Nichol 01 Apr '16

01 Apr '16

> On Thu, 31 Mar 2016 21:49:56 -0400 (EDT) > Aditya Mahajan <adityam(a)umich.edu> wrote: > > On Thu, 31 Mar 2016, Alan BRASLAU wrote: > >> On Thu, 31 Mar 2016 17:51:07 -0400 >> Aditya Mahajan <adityam(a)umich.edu> wrote: >> >>> @Hans: Does it make sense to disable \incrementcounter if >>> \trialtypesetting is active? >> >> I was going to suggest such things... > > My motivation is different. If you have any macro in a table (or anything > that requires multiple runs to get the size right) that uses a counter > (e.g., enumeration), then the numbers will be off. That would not happen > if a counter is frozen when trialtypesetting is on. > >> P.S. Would not the use of \startcombination\stopcombination be an >> alternative to the placefigures within a table? And \startcombination\stopcombination fails when you use \placefigure instead of \externalfigure because you want the captions to be numbered and included in the list of figures. You get an error like this one > tex error on line 7 in file virtual: . . . ! You can't use `\prevdepth' in restricted horizontal mode Using \startfloatcombinations\stopfloatcombination (which appears to be undocumented) avoids this error. > > combinations only give regular grid. Sometimes you want an irregular grid. > For example, the OP wanted > > +-------+------+ > | | | > | | Fig2 | > | Fig1 +-------+ > | | Fig3 | > | | | > +------+-------+ > > Such layouts are not possible using combinations. I thought that nesting combinations might enable this type of combination but it didn’t work. see https://mailman.ntg.nl/pipermail/ntg-context/2016/084926.html <https://mailman.ntg.nl/pipermail/ntg-context/2016/084926.html> Using tables is a better solution because it has the syntax to handle figures that span rows or columns > > Aditya > Lots of things seem to work well with external figures but as soon as you embed them in a \placefigure, which makes them a float, you make things more complex and run into the possibility of triggering the restricted horizontal mode error. It seems to me that once you place an object that is normally a float inside another float you want the inner one to lose it floating characteristics. Is there a way do this explicitly i.e. instead of creating an inner float with \placefigure[force][ref1]{this is the caption }{\externalfigure[cow][width=3in,height=1in]} could we create a non-floating version with something explicit like \externalfigure[cow][width=3in,height=1in] \addcaption[figure][ref1]{this is the caption } Aidan

2 1

figures in tables
by Hans Hagen 01 Apr '16

01 Apr '16

Hi, I've added support for \starttext \useMPlibrary[dum] \bTABLE \bTR \bTD \placefigure{}{\externalfigure[dummy][width=4cm]}% \eTD \eTR \eTABLE \bTABLE[split=yes] \dorecurse{10}{ \bTR \bTD \placefigure{}{\externalfigure[dummy][width=4cm]} \eTD \bTD \placefigure{}{\externalfigure[dummy][width=4cm]} \eTD \eTR \bTR \bTD[nx=2] \placefigure{}{\externalfigure[dummy][width=12cm,height=3cm]} \eTD \eTR \bTR \bTD \placefigure{}{\externalfigure[dummy][width=4cm]} \eTD \bTD[ny=2] \placefigure{}{\externalfigure[dummy][width=4cm,height=8cm]} \eTD \eTR \bTR \bTD \placefigure{}{\externalfigure[dummy][width=4cm]} \eTD \eTR } \eTABLE \stoptext somewhat experimental (and I will not support floats in all kind of constructs ... after all, they are floats) (btw, \placefigure[force,always] is pretty much a local float) 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

Re: [NTG-context] Skipped figure numbers
by Aidan Nichol 01 Apr '16

01 Apr '16

Thanks Aditya That solved the problem > > > On Wed, 30 Mar 2016, Aidan Nichol wrote: > >> 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? > > The contents of a table are typeset multiple times to get an idea of the > height and width. Here is one option: > > \useMPlibrary[dum] > > \starttext > > \bTABLE[frame=off,align=low] > \bTR > \bTD[ny=2] > \placefigure[here,\iftrialtypesetting nonumber \fi] > []{left twoup}{\externalfigure[mill][width=2in,height=4in]} > \eTD > \bTD > \placefigure[here,\iftrialtypesetting nonumber \fi] > []{the first}{\externalfigure[spider][width=2in,height=2in]} > \eTD > \eTR > \bTR > \bTD > \placefigure[here,\iftrialtypesetting nonumber \fi] > []{the second}{\externalfigure[cow][width=2in,height=2in]} > \eTD > \eTR > \eTABLE > \stoptext > > Aditya >

4 5

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

01 Apr '16

On 3/31/2016 9:28 PM, Jan Tosovsky wrote: > On 2016-03-31 Hans Hagen wrote: >> On 3/30/2016 9:53 PM, Jan Tosovsky wrote: >>> On 2016-03-22 Hans Hagen wrote: >>>> 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'd be grateful for ignoring any non document content >>>>>>> preceding punctuation to avoid its influence on protrusion. >>>> >>>> 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 >> >> you can try to do this: >> >> \leftboundary\hbox{\index{foo}}.... > > Wow, I am quite satisfied with this solution. > > Btw, I couldn't find any details for that \leftboundary command either in TeX [1] or ConTeXt [2] command references. > > I've tried it just with \hbox{} and it works as well. > > Couldn't this be generalized in a way - if you want protrusion even in edge cases, any inline commands have to be wrapped in \hbox{} ? because for instance you wouldn't want to protrude into a constructed compound hyphen which is a inline construct, just as you don't want to protrude into a formula or something explicitely boxed 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

Recent changes in paragraph composing
by Jan Tosovsky 31 Mar '16

31 Mar '16

Dear All, when generating example in the following article, I can't get rid of overfull in Old greek paragraph even if the tolerance is set to 'verytolerant'. http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV In time of producing the result image it was sufficient to set the tolerance to 'strict'. (1) How can this be fixed efficiently? (2) What has changed internally? Thanks for any hints, Jan

1 0

Re: [NTG-context] Error - font-otj.lua:1503: attempt to perform arithmetic on local 'rightkern'
by Hans Hagen 31 Mar '16

31 Mar '16

On 3/30/2016 9:11 PM, Jan Tosovsky wrote: > 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): not related to 0.90 ... fixed in next beta (kerning with spaces is new and still somewhat untested) you can try \definefontfeature[default][default][spacekern=no] 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] Alignment for narrower text
by Hans Hagen 31 Mar '16

31 Mar '16

On 3/30/2016 8:55 PM, Jan Tosovsky wrote: > 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 :-) indenting prohibits protrusion 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] Protrusion cancellation by index term
by Hans Hagen 31 Mar '16

31 Mar '16

On 3/30/2016 9:53 PM, Jan Tosovsky wrote: > On 2016-03-22 Hans Hagen wrote: >> 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 >>>>>> >>>>> 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 >> > > Can you roughly estimate when this could be further investigated? > Between 0.90-0.95, later or after 1.0? further handling is unrelated to the engine because at that level it is not know what protrusion is expected (there are probably as many cases where you don't want to protrude as where you might want and hard coding solutions / heuristics is no option > I hope there will be some way to fix it in ConTeXt one day. non trivial so very stepwise ... adding all kind of hacks just for protrusion can interfere with other mechanisms you can try to do this: \leftboundary\hbox{\index{foo}}.... ----------------------------------------------------------------- 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

beta / current
by Hans Hagen 31 Mar '16

31 Mar '16

Hi, As texlive code freeze is on the horizon, we are close to a new current release. The current beta will probably not change much till that moment. We now have luatex 0.90 but might as well end up with 0.95 in texlive 2016 (because as usual we can test it with the garden distribution). 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