March 2016 - ntg-context - NTG Mailing Lists

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

01 Apr '16

> Jan Tosovsky <mailto:j.tosovsky@email.cz> > 31. März 2016 um 21:28 > > 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. The \leftboundary command uses a new LuaTeX primitive which means you can’t find it in a TeX [1] reference. spac-ver.mkiv: \unexpanded\def\leftboundary {\boundary\plusone} \unexpanded\def\rightboundary {\boundary\plustwo} Wolfgang

3 2

Re: [NTG-context] Recent changes in paragraph composing
by Schmitz Thomas A. 01 Apr '16

01 Apr '16

> On 31 Mar 2016, at 22:17, Jan Tosovsky <j.tosovsky(a)email.cz> wrote: > > 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, The example is missing the language setup: \setuplanguage [en] [patterns={en,agr}] \mainlanguage [en] Thomas

2 1

[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

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

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

Bug/change in fillinrules
by Mari Voipio 31 Mar '16

31 Mar '16

Hello, after I updated to about newest ConTeXt, I found out that \fillinrules doesn't work any more as expected, i.e. instead of filling the rest of the first line, the rule now starts on the second line, below the text that precedes \fillinrules. This doesn't match the behaviour indicated in http://wiki.contextgarden.net/Command/fillinrules . Is this a bug or should I change something in my code? Now I have \setupfillinrules [n=1, %one rule per command \fillinrules width=broad] %leaves some space between the text and the line \starttext \fillinrules{Refractometer serial no:} \fillinrules{Customer:} \fillinrules{Address:} \fillinrules{Fax:} \fillinrules{Email:} \fillinrules{Sample description:} \fillinrules{Solvent (water/other):} \fillinrules{Laboratory method:} \fillinrules{Date:} \fillinrules{Data collected by:} \stoptext The resulting pdf is attached. Thank you for your help, Mari

3 3