bug in latest beta?

bug in latest beta?

[Pablo Rodriguez]

Hans,

the following sample gives a Lua error with latest beta (2016.09.04 13:46):

    \setupinteraction[state=start]
    \define[1]\myurl{{\tt\goto{\hyphenatedurl{#1}}[url(#1)]}}

    \starttext
    \input knuth \myurl{http://wiki.contextgarden.net}.
    \stoptext

Compilation is fine with beta from 2016.07.18 16:46.

Is this a bug or am I missing something?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[josephcanedo]

[-- Attachment #1.1: Type: text/plain, Size: 230 bytes --]

Dear all,

Sounds like  a typo in file tex/texmf-context/tex/context/base/mkiv/node-nut.lua line 238

find_tail should be findtail I think.

BTW this new rangedimension function is helpful.

Joseph

De : Pablo Rodriguez

[-- Attachment #1.2: Type: text/html, Size: 4080 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 09/05/2016 08:36 AM, josephcanedo@gmail.com wrote:
> Dear all,
> 
> Sounds like  a typo in file
> tex/texmf-context/tex/context/base/mkiv/node-nut.lua line 238
> 
> find_tail should be findtail I think.

Hi Joseph,

sorry for overlooking your message.

Of course, you are right. (I cannot code, but defining a local variable
in line 233 and using it with an underscore in line 238 doesn’t make
sense even to me.)

I’m afraid that the typo is present in the newer beta from today
(2016.09.05 10:28).

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 09/05/2016 05:10 PM, Pablo Rodriguez wrote:
> [...]
> I’m afraid that the typo is present in the newer beta from today
> (2016.09.05 10:28).

The issue has been fixed in latest beta (2016.09.06 00:28).

Hans, many thanks for the fix.


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 11/01/2017 02:18 PM, Pablo Rodriguez wrote:
> [...]
>     $ ./first-setup.sh --modules=all
>     receiving incremental file list
> 
>     sent 29 bytes  received 155 bytes  122.67 bytes/sec
>     total size is 8,660,630  speedup is 47,068.64
>     ./bin/mtxrun:5878: attempt to call local 'ln' (a nil value)

Hans,

many thanks for your fast fix.

After the newer beta I get another bug:

  $ mtxrunjit --generate
  ~/ctxbeta/tex/texmf-linux/bin/mtxrun:633: attempt to index local
    'searchers' (a nil value)

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

bug in latest beta?

[Pablo Rodriguez]

Hans,

I have tried to update the ConTeXt Suite to latest beta and I got the
following message:

    $ ./first-setup.sh --modules=all
    receiving incremental file list

    sent 29 bytes  received 155 bytes  122.67 bytes/sec
    total size is 8,660,630  speedup is 47,068.64
    ./bin/mtxrun:5878: attempt to call local 'ln' (a nil value)

I think there may be a bug there.

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 09/05/2016 04:44 PM, luigi scarso wrote:
> On Mon, Sep 5, 2016 at 4:33 PM, Pablo Rodriguez wrote:
>> [...]
>> Luigi, would it be possible that all platforms have the latest LuaTeX
>> version included?
> 
> experimental is, well, experimental, so not trunk and not even a tag
> (i.e. a new version).
> But you can easily compile it from svn, it's a matter of
> ./build.sh --parallel --jit

Sorry for the noise, Luigi.

I have corrected the variable (as described in
https://mailman.ntg.nl/pipermail/ntg-context/2016/086761.html) and it
works fine.

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[luigi scarso]

On Mon, Sep 5, 2016 at 4:33 PM, Pablo Rodriguez <oinos@gmx.es> wrote:
> On 09/05/2016 10:39 AM, Akira Kakuto wrote:
>>> the following sample gives a Lua error with latest beta (2016.09.04 13:46):
>>
>> Compilation is fine in the latest luatex 0.98.4 with
>> mtx-context     | current version: 2016.09.04 13:46.
>>
>
> Hi Akira,
>
> it seems that luatex-0.98.4 has been released for Windows today.
>
> I will wait for the release in the Linux 32bit platform.
>
> Luigi, would it be possible that all platforms have the latest LuaTeX
> version included?

experimental is, well, experimental, so not trunk and not even a tag
(i.e. a new version).
But you can easily compile it from svn, it's a matter of
./build.sh --parallel --jit


-- 
luigi
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 09/05/2016 10:39 AM, Akira Kakuto wrote:
>> the following sample gives a Lua error with latest beta (2016.09.04 13:46):
> 
> Compilation is fine in the latest luatex 0.98.4 with
> mtx-context     | current version: 2016.09.04 13:46.
> 

Hi Akira,

it seems that luatex-0.98.4 has been released for Windows today.

I will wait for the release in the Linux 32bit platform.

Luigi, would it be possible that all platforms have the latest LuaTeX
version included?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

bug in latest beta?

[Akira Kakuto]

> the following sample gives a Lua error with latest beta (2016.09.04 13:46):

Compilation is fine in the latest luatex 0.98.4 with
mtx-context     | current version: 2016.09.04 13:46.

-- 
Akira

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Otared Kavian]

> On 01 Jun 2015, at 09:28, Pablo Rodriguez <oinos@gmx.es> wrote:
> 
> […]
> Hi Otared,
> 
> having only three theorems my guess will be probably wrong, but I’ll try it.
> 
> The theorem that doesn’t cause a wrong pagebreak is preceeded by a
> single line paragraph.
> 
> In order to confirm whether this is the pattern, I would remove some
> words from the last paragraph on page 19, so that there has only one
> line. And I would add some words to the pagraph before theorem 2.3.2 on
> page 31, so this pargraph contains two lines.
> 
> Could you check this?
> 
> 
> Pablo
> -- 
> http://www.ousia.tk

Hi Pablo,

Actually I have done what you suggest by adding or removing text, but at the end when the document changes all of a sudden the bad pagebreaks appear or disappear.
The second definition of « proclaim » I sent you suppresses the bad pagebreaks, but in some other situations still I have other bad pagebreaks… Until I have not made a rela minimal example the problem cannot be understood and permanently solved.

Best regards: OK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 06/01/2015 08:45 AM, Otared Kavian wrote:
> Hi Pablo,
> 
> Indeed the document I was talking about has been typeset with
> various versions of mkiv, but now I observe that sometimes the
> pagebreaks are made in a very strange way. Since I can’t make a
> minimal example, I put on the following link an excerpt of the PDF
> document where the bad pagebreaks can be seen:
> 
>   https://dl.dropboxusercontent.com/u/4316076/bad-pagebreak.pdf
> 
> (Please see pages 19 and 32). It seems that this happens, sometimes,
> but as far as I can say from my experiments the bad pagebreak happens
> always before a « proclaim » which is defined as follows:
> [...]
> However it would be better to understand why the first definition
> does not work properly, in a rather random way.

Hi Otared,

having only three theorems my guess will be probably wrong, but I’ll try it.

The theorem that doesn’t cause a wrong pagebreak is preceeded by a
single line paragraph.

In order to confirm whether this is the pattern, I would remove some
words from the last paragraph on page 19, so that there has only one
line. And I would add some words to the pagraph before theorem 2.3.2 on
page 31, so this pargraph contains two lines.

Could you check this?


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Otared Kavian]

Hi Pablo,

Indeed the document I was talking about has been typeset with various versions of mkiv, but now I observe that sometimes the pagebreaks are made in a very strange way. Since I can’t make a minimal example, I put on the following link an excerpt of the PDF document where the bad pagebreaks can be seen: 

	https://dl.dropboxusercontent.com/u/4316076/bad-pagebreak.pdf

(Please see pages 19 and 32). It seems that this happens, sometimes, but as far as I can say from my experiments the bad pagebreak happens always before a « proclaim » which is defined as follows:

\defineenumeration[proclaim]
	[text=,
	before={\blank\startbackground[frame=off,leftframe=on,
				rulethickness=2pt,framecolor=darkred,
				background=color,
				backgroundcolor=screen]},
	after={\stopbackground\blank},
	style=slanted,
	title=yes,
	titleleft=,
	titleright={.},
	alternative=hanging,
	width=fit,
	right={~},
	way=bysection,
	prefix=yes,
	prefixsegments={chapter:section}]

Actually I found a workaround for this by changing the above definition into:

\defineenumeration[proclaim]
	[text=,
	before={\blank\startmarginrule[rulethickness=1pt,rulecolor=darkred]},
	after={\stopmarginrule},
	style=slanted,
	title=yes,
	titleleft=,
	titleright={.},
	alternative=hanging,
	width=fit,
	right={~},
	way=bysection,
	prefix=yes,
	prefixsegments={chapter:section}]

However it would be better to understand why the first definition does not work properly, in a rather random way.

Best regards: OK


> On 01 Jun 2015, at 00:16, Hans Hagen <pragma@wxs.nl> wrote:
> 
> On 5/31/2015 1:56 PM, Pablo Rodriguez wrote:
>> On 05/28/2015 07:10 PM, Hans Hagen wrote:
>>> On 5/27/2015 10:38 PM, Pablo Rodriguez wrote:
>>>> [...]
>>>> Compiling it with beta from 2015.03.25 22:13, page break is fine.
>>>> 
>>>> But with latest beta from 2015.05.24 12:42 (or even with beta from
>>>> 2015.05.15 11:42 includes a wrong page break. The setups for widow and
>>>> orphan lines move the two last lines to the next page.
>>>> 
>>>> Could anyone confirm this bug?
>>> 
>>> i wonder if it's a bug or just tex's decision ... you can use
>>> 
>>> \showmakeup[penalty]
>>> 
>>> and see what penalties get injected
>>> 
>>> are the linebreaks identical, i.e. same hyphenation?
>> 
>> Many thanks for your reply, Hans.
>> 
>> Hyphenation is the same in both documents.
>> 
>>> btw, brokenpenalty 1 gives a different result
>> 
>> Page break is wrong when any of the three values (brokenpenalty,
>> widowpenalty or clubpenalty) is 0 or above 9999.
>> 
>> I replacing \subsection with \section gives the right page break:
>> 
>>     \showframe\showgrid
>>     \setuplayout[setups=*lessstrict]
>>     \startsetups[*lessstrict]
>>         \setup[reset]
>>         \widowpenalty=10000
>>         \clubpenalty=10000
>>         \brokenpenalty=0
>>     \stopsetups
>>     \setupbodyfont[pagella, 12.6pt]
>>     \starttext
>>     \chapter{Quotes}
>>     \section{Zapf}
>>     \dorecurse{4}{\input zapf\par}
>>     \section{Knuth}
>>     \input knuth
>>     \stoptext
>> 
>> Why does \subsection cause a different page break than \section?
> 
> because there are penalties related to (sub)sections in a way that keeps them together but at the same time still permits breaks in case of too many successive ones .. and penalties determine the way the page is broken
> 
> Hans
> 
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>                                             | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@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
> ___________________________________________________________________________________

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Hans Hagen]

On 5/31/2015 1:56 PM, Pablo Rodriguez wrote:
> On 05/28/2015 07:10 PM, Hans Hagen wrote:
>> On 5/27/2015 10:38 PM, Pablo Rodriguez wrote:
>>> [...]
>>> Compiling it with beta from 2015.03.25 22:13, page break is fine.
>>>
>>> But with latest beta from 2015.05.24 12:42 (or even with beta from
>>> 2015.05.15 11:42 includes a wrong page break. The setups for widow and
>>> orphan lines move the two last lines to the next page.
>>>
>>> Could anyone confirm this bug?
>>
>> i wonder if it's a bug or just tex's decision ... you can use
>>
>> \showmakeup[penalty]
>>
>> and see what penalties get injected
>>
>> are the linebreaks identical, i.e. same hyphenation?
>
> Many thanks for your reply, Hans.
>
> Hyphenation is the same in both documents.
>
>> btw, brokenpenalty 1 gives a different result
>
> Page break is wrong when any of the three values (brokenpenalty,
> widowpenalty or clubpenalty) is 0 or above 9999.
>
> I replacing \subsection with \section gives the right page break:
>
>      \showframe\showgrid
>      \setuplayout[setups=*lessstrict]
>      \startsetups[*lessstrict]
>          \setup[reset]
>          \widowpenalty=10000
>          \clubpenalty=10000
>          \brokenpenalty=0
>      \stopsetups
>      \setupbodyfont[pagella, 12.6pt]
>      \starttext
>      \chapter{Quotes}
>      \section{Zapf}
>      \dorecurse{4}{\input zapf\par}
>      \section{Knuth}
>      \input knuth
>      \stoptext
>
> Why does \subsection cause a different page break than \section?

because there are penalties related to (sub)sections in a way that keeps 
them together but at the same time still permits breaks in case of too 
many successive ones .. and penalties determine the way the page is broken

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 05/28/2015 07:10 PM, Hans Hagen wrote:
> On 5/27/2015 10:38 PM, Pablo Rodriguez wrote:
>> [...]
>> Compiling it with beta from 2015.03.25 22:13, page break is fine.
>>
>> But with latest beta from 2015.05.24 12:42 (or even with beta from
>> 2015.05.15 11:42 includes a wrong page break. The setups for widow and
>> orphan lines move the two last lines to the next page.
>>
>> Could anyone confirm this bug?
> 
> i wonder if it's a bug or just tex's decision ... you can use
> 
> \showmakeup[penalty]
> 
> and see what penalties get injected
> 
> are the linebreaks identical, i.e. same hyphenation?

Many thanks for your reply, Hans.

Hyphenation is the same in both documents.

> btw, brokenpenalty 1 gives a different result

Page break is wrong when any of the three values (brokenpenalty,
widowpenalty or clubpenalty) is 0 or above 9999.

I replacing \subsection with \section gives the right page break:

    \showframe\showgrid
    \setuplayout[setups=*lessstrict]
    \startsetups[*lessstrict]
        \setup[reset]
        \widowpenalty=10000
        \clubpenalty=10000
        \brokenpenalty=0
    \stopsetups
    \setupbodyfont[pagella, 12.6pt]
    \starttext
    \chapter{Quotes}
    \section{Zapf}
    \dorecurse{4}{\input zapf\par}
    \section{Knuth}
    \input knuth
    \stoptext

Why does \subsection cause a different page break than \section?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 05/28/2015 04:59 PM, Otared Kavian wrote:
> Hi Pablo,
> 
> I tested your sample with
> 
>   ConTeXt ver: 2014.05.21 22:04 MKIV beta fmt: 2015.3.31 int: english/english
> 
> (which is from TeXLIve 2014) and also with
> 
>   ConTeXt ver: 2015.05.21 13:39 MKIV beta fmt: 2015.5.21 int: english/english
> 
> and I get exactly the same result, with the last two line of page 1
> pushed to the second page.
> 
> However with mmkii, thta is
> 
>   ConTeXt ver: 2013.06.07 17:34 MKII fmt: 2015.5.21 int: english/english
> 
> the penalties act correctly and page one has all the lines expected,
> while page 2 begins with a new section.
> 
> Actually I hav enoticed that recent versions of mkiv create strange page
> breaks in some of documents containing maths, but up to now I have not
> succeeded to reproduce this bad behavior in a short (and minimal) example.

Many thanks for your testing, Otared.

It seems that different MkIV betas may give different results.

I noticed it by compiling the same source with different MkIV betas.

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Hans Hagen]

On 5/27/2015 10:38 PM, Pablo Rodriguez wrote:
> Dear list,
>
> I have the following sample:
>
>      \showframe\showgrid
>      \setuplayout[setups=*lessstrict]
>      \startsetups[*lessstrict]
>          \setup[reset]
>          \widowpenalty=10000
>          \clubpenalty=10000
>          \brokenpenalty=0
>      \stopsetups
>      \setupbodyfont[pagella, 12.6pt]
>      \starttext
>      \chapter{Quotes}
>      \section{Zapf}
>      \dorecurse{4}{\input zapf\par}
>      \subsection{Knuth}
>      \input knuth
>      \stoptext
>
> Compiling it with beta from 2015.03.25 22:13, page break is fine.
>
> But with latest beta from 2015.05.24 12:42 (or even with beta from
> 2015.05.15 11:42 includes a wrong page break. The setups for widow and
> orphan lines move the two last lines to the next page.
>
> Could anyone confirm this bug?

i wonder if it's a bug or just tex's decision ... you can use

\showmakeup[penalty]

and see what penalties get injected

are the linebreaks identical, i.e. same hyphenation?

btw, brokenpenalty 1 gives a different result

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Otared Kavian]

Hi Pablo,

I tested your sample with

	ConTeXt  ver: 2014.05.21 22:04 MKIV beta  fmt: 2015.3.31  int: english/english

(which is from TeXLIve 2014) and also with

	ConTeXt ver: 2015.05.21 13:39 MKIV beta fmt: 2015.5.21 int: english/english

and I get exactly the same result, with the last two line of page 1 pusged to the second page.

However with mmkii, thta is

	ConTeXt ver: 2013.06.07 17:34 MKII fmt: 2015.5.21 int: english/english

the penalties act correctly and page one has all the lines expected, while page 2 begins with a new section.

Actually I hav enoticed that recent versions of mkiv create strange page breaks in some of documents containing maths, but up to now I have not succeeded to reproduce this bad behavior in a short (and minimal) example.

Best regards: OK
	


> On 27 May 2015, at 22:38, Pablo Rodriguez <oinos@gmx.es> wrote:
> 
> Dear list,
> 
> I have the following sample:
> 
>    \showframe\showgrid
>    \setuplayout[setups=*lessstrict]
>    \startsetups[*lessstrict]
>        \setup[reset]
>        \widowpenalty=10000
>        \clubpenalty=10000
>        \brokenpenalty=0
>    \stopsetups
>    \setupbodyfont[pagella, 12.6pt]
>    \starttext
>    \chapter{Quotes}
>    \section{Zapf}
>    \dorecurse{4}{\input zapf\par}
>    \subsection{Knuth}
>    \input knuth
>    \stoptext
> 
> Compiling it with beta from 2015.03.25 22:13, page break is fine.
> 
> But with latest beta from 2015.05.24 12:42 (or even with beta from
> 2015.05.15 11:42 includes a wrong page break. The setups for widow and
> orphan lines move the two last lines to the next page.
> 
> Could anyone confirm this bug?
> 
> Many thanks for your help,
> 
> 
> Pablo
> -- 
> http://www.ousia.tk
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@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
> ___________________________________________________________________________________

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

bug in latest beta?

[Pablo Rodriguez]

Dear list,

I have the following sample:

    \showframe\showgrid
    \setuplayout[setups=*lessstrict]
    \startsetups[*lessstrict]
        \setup[reset]
        \widowpenalty=10000
        \clubpenalty=10000
        \brokenpenalty=0
    \stopsetups
    \setupbodyfont[pagella, 12.6pt]
    \starttext
    \chapter{Quotes}
    \section{Zapf}
    \dorecurse{4}{\input zapf\par}
    \subsection{Knuth}
    \input knuth
    \stoptext

Compiling it with beta from 2015.03.25 22:13, page break is fine.

But with latest beta from 2015.05.24 12:42 (or even with beta from
2015.05.15 11:42 includes a wrong page break. The setups for widow and
orphan lines move the two last lines to the next page.

Could anyone confirm this bug?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 05/14/2015 10:46 PM, Pablo Rodriguez wrote:
> Hans,
> 
> after upgrading to beta from 2015.05.13 23:52, the compilation of most
> of my documents crashes.
> 
> I get two different errors depending on the document:
> 
> error: .../ctxbeta/tex/texmf-context/tex/context/base/typo-itc.lua:148:
> attempt to call global 'setfield' (a nil value)

Hans,

here you have a sample that triggers the error in that line:

    \definefontfeature
        [default]
        [default]
        [script=latn,
         itlc=yes]

    \setupitaliccorrection
        [always]

    \definefontfamily
        [mainface]
        [serif]
        [TeX Gyre Pagella]

    \starttext
    \it a
    \stoptext

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

bug in latest beta?

[Pablo Rodriguez]

Hans,

after upgrading to beta from 2015.05.13 23:52, the compilation of most
of my documents crashes.

I get two different errors depending on the document:

error: .../ctxbeta/tex/texmf-context/tex/context/base/typo-itc.lua:148:
attempt to call global 'setfield' (a nil value)

error: .../ctxbeta/tex/texmf-context/tex/context/base/typo-itc.lua:159:
attempt to call global 'setfield' (a nil value)

I cannot provide a minimal sample now. I wonder whether the error itself
might be enough to fix the issue.

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 12/10/2014 08:14 PM, Hans Hagen wrote:
> On 12/10/2014 7:51 PM, Pablo Rodriguez wrote:
>> Hans,
>>
>> after updating to latest beta I get an error when compiling the sample
>> bellow with beta from 2014.12.09 13:03:
>>
>>     \setupitaliccorrection[global,always]
>>     \definefontfamily[mainface][serif][TeX Gyre Pagella]
>>     \setupbodyfont[mainface,15pt]
>>
>>     \def\ConTeXt{Con\-\TeX{}t}
>>
>>     \starttext
>>     \itc The Book on \ConTeXt
>>     \medskip
>>     \tfa\setupinterlinespace[2.6ex] {\sc The Author}
>>     \par
>>     \currentdate
>>     \stoptext
>>
>> Beta from 2014.11.26 21:43 compiles it without problems.
>>
>> Is this a bug or am I missing something?
> 
> It's a bug (I updated some discretionary related code so ther might be a 
> few more border cases not handled well). I'll make a new beta.

Many thanks for the fast fix, Hans.


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Hans Hagen]

On 12/10/2014 7:51 PM, Pablo Rodriguez wrote:
> Hans,
>
> after updating to latest beta I get an error when compiling the sample
> bellow with beta from 2014.12.09 13:03:
>
>     \setupitaliccorrection[global,always]
>     \definefontfamily[mainface][serif][TeX Gyre Pagella]
>     \setupbodyfont[mainface,15pt]
>
>     \def\ConTeXt{Con\-\TeX{}t}
>
>     \starttext
>     \itc The Book on \ConTeXt
>     \medskip
>     \tfa\setupinterlinespace[2.6ex] {\sc The Author}
>     \par
>     \currentdate
>     \stoptext
>
> Beta from 2014.11.26 21:43 compiles it without problems.
>
> Is this a bug or am I missing something?

It's a bug (I updated some discretionary related code so ther might be a 
few more border cases not handled well). I'll make a new beta.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

bug in latest beta?

[Pablo Rodriguez]

Hans,

after updating to latest beta I get an error when compiling the sample
bellow with beta from 2014.12.09 13:03:

   \setupitaliccorrection[global,always]
   \definefontfamily[mainface][serif][TeX Gyre Pagella]
   \setupbodyfont[mainface,15pt]

   \def\ConTeXt{Con\-\TeX{}t}

   \starttext
   \itc The Book on \ConTeXt
   \medskip
   \tfa\setupinterlinespace[2.6ex] {\sc The Author}
   \par
   \currentdate
   \stoptext

Beta from 2014.11.26 21:43 compiles it without problems.

Is this a bug or am I missing something?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 05/26/2014 10:24 AM, Hans Hagen wrote:
> On 5/26/2014 7:47 AM, Pablo Rodriguez wrote:
>> [...]
>> Page break is wrong if \section is enabled (or I am missing something
>> extremely basic).
>>
>> I guess it might be worth fixing it also for ConTeXt in TeX Live 2014.
>>
>> Many thanks for your help,
> 
> It has to do with trying to improve the 'keep together' successive 
> head/text 'without deadlock' issue; I'll try to improve that bit but for 
> a while it will be somewhat experimental (it's one of the things I'm 
> trying to improve).

Many thanks for the fix, Hans.

I have another wrong page break, but I’m afraid I need some time to
elaborate the sample.

Many thanks again for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Hans Hagen]

On 5/26/2014 7:47 AM, Pablo Rodriguez wrote:
> Dear list,
>
> I’m afraid there is a bug (I think it was) introduced in beta from
> 2014.05.21 22:04:
>
>      \showframe
>      \setuppapersize[A6]
>      \starttext
>      \dorecurse{23}{This is only a random sentence. }
>
>      \section{Section}
>
>      \input zapf
>      \stoptext
>
> Page break is wrong if \section is enabled (or I am missing something
> extremely basic).
>
> I guess it might be worth fixing it also for ConTeXt in TeX Live 2014.
>
> Many thanks for your help,

It has to do with trying to improve the 'keep together' successive 
head/text 'without deadlock' issue; I'll try to improve that bit but for 
a while it will be somewhat experimental (it's one of the things I'm 
trying to improve).

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

bug in latest beta?

[Pablo Rodriguez]

Dear list,

I’m afraid there is a bug (I think it was) introduced in beta from
2014.05.21 22:04:

    \showframe
    \setuppapersize[A6]
    \starttext
    \dorecurse{23}{This is only a random sentence. }

    \section{Section}

    \input zapf
    \stoptext

Page break is wrong if \section is enabled (or I am missing something
extremely basic).

I guess it might be worth fixing it also for ConTeXt in TeX Live 2014.

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Pablo Rodriguez]

On 03/18/2014 06:39 PM, Wolfgang Schuster wrote:
> Am 18.03.2014 um 18:30 schrieb Pablo Rodriguez:
>> Dear list,
>>
>> I cannot compile the following sample with latest beta:
>>
>> \definefontfamily[mainface][serif][TeX Gyre Pagella]
>> \setupbodyfont[mainface,14pt]
>>
>> \starttext
>> \startitemize
>>
>> \item First item.
>>
>> \item Second item.
>>
>> \stopitemize
>>
>> \stoptext
>>
>>
>> This worked fine with previous beta. Isn’t it a bug?
> 
> You have to load a math font because the bullets for the items are
> taken by default from the math font.

Many thanks for your help, Wolfgang.

It works fine now.


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Wolfgang Schuster]

Am 18.03.2014 um 18:30 schrieb Pablo Rodriguez <oinos@gmx.es>:

> Dear list,
> 
> I cannot compile the following sample with latest beta:
> 
> \definefontfamily[mainface][serif][TeX Gyre Pagella]
> \setupbodyfont[mainface,14pt]
> 
> \starttext
> \startitemize
> 
> \item First item.
> 
> \item Second item.
> 
> \stopitemize
> 
> \stoptext
> 
> 
> This worked fine with previous beta. Isn’t it a bug?

You have to load a math font because the bullets for the items are taken by default from the math font.

BTW: When you have a font related bug check first if it happens also with \definetypeface.

\definetypeface[mainface][rm][serif][pagella][default]
\definetypeface[mainface][mm][math] [pagella][default] % comment to get the error

\setupbodyfont[mainface]

\starttext
\symbol[bullet]
\stoptext

Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

bug in latest beta?

[Pablo Rodriguez]

Dear list,

I cannot compile the following sample with latest beta:

\definefontfamily[mainface][serif][TeX Gyre Pagella]
\setupbodyfont[mainface,14pt]

\starttext
\startitemize

\item First item.

\item Second item.

\stopitemize

\stoptext


This worked fine with previous beta. Isn’t it a bug?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@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
___________________________________________________________________________________

Re: bug in latest beta?

[Hans Hagen]

Chen Shen wrote:
> Hi all,
> 
> the following code used to work, but broke in the latest beta. \at
> works well, but \in appears as a math "member of set" symbol ( ∈ ).
> 
> ========================
> \starttext
> \placefigure[here][abc]{xyz}{123}
> 
> abc \at[abc].
> abc \in[abc].
> 
> \stoptext
> ========================

fixed in current beta

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: bug in latest beta?

[Chen Shen]

Thanks a lot for the insights. I reverted to the 2008.10.31 version
for the moment.

shenchen

On Mon, Nov 10, 2008 at 7:59 PM, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
>
> Am 10.11.2008 um 10:55 schrieb Chen Shen:
>
>> Hi all,
>>
>> the following code used to work, but broke in the latest beta. \at
>> works well, but \in appears as a math "member of set" symbol ( ∈ ).
>
> You could use the last stable for the moment.
>
>> ========================
>> \starttext
>> \placefigure[here][abc]{xyz}{123}
>>
>> abc \at[abc].
>> abc \in[abc].
>>
>> \stoptext
>> ========================
>
>
> If you still want to use the last beta use the following patch,
> Hans removed a few lines of code from enco-ini.mkiv and this
> breaks the \in command because it is redefined later in the core
> from the math commands.
>
> \def\definecommand#1 #2 %
>   {\setvalue{\string#1}{\dohandlecommand{#1}}%
>    \setvalue{\characterencoding\string#1}{#2}}
>
> \def\dohandlecommand#1%
>    {\csname
>       \ifcsname\characterencoding#1\endcsname
>         \characterencoding
>       \else
>         \nocharacterencoding
>       \fi
>     #1\endcsname}
>
> \definecommand in    {\doinatreference\currenttextreference}
>
> Wolfgang
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: bug in latest beta?

[Wolfgang Schuster]

Am 10.11.2008 um 10:55 schrieb Chen Shen:

> Hi all,
>
> the following code used to work, but broke in the latest beta. \at
> works well, but \in appears as a math "member of set" symbol ( ∈ ).

You could use the last stable for the moment.

> ========================
> \starttext
> \placefigure[here][abc]{xyz}{123}
>
> abc \at[abc].
> abc \in[abc].
>
> \stoptext
> ========================


If you still want to use the last beta use the following patch,
Hans removed a few lines of code from enco-ini.mkiv and this
breaks the \in command because it is redefined later in the core
from the math commands.

\def\definecommand#1 #2 %
   {\setvalue{\string#1}{\dohandlecommand{#1}}%
    \setvalue{\characterencoding\string#1}{#2}}

\def\dohandlecommand#1%
    {\csname
       \ifcsname\characterencoding#1\endcsname
         \characterencoding
       \else
         \nocharacterencoding
       \fi
     #1\endcsname}

\definecommand in    {\doinatreference\currenttextreference}

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

bug in latest beta?

[Chen Shen]

Hi all,

the following code used to work, but broke in the latest beta. \at
works well, but \in appears as a math "member of set" symbol ( ∈ ).

========================
\starttext
\placefigure[here][abc]{xyz}{123}

abc \at[abc].
abc \in[abc].

\stoptext
========================

I am using

$ context --version
MtxRun | main context file:
/opt/home/hash/context/tex/texmf-context/tex/context/base/context.tex
MtxRun | current version: 2008.56.06 19:11

$ luatex -v
This is LuaTeX, Version snapshot-0.30.2-2008102016, build unknown

any suggestions? Thanks a lot.

best regards,
shenchen
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________