[NTG-context] Paranormal bug in TL 2016

Henri Menke henrimenke at gmail.com
Wed Oct 12 11:19:15 CEST 2016


I got it working using the patch below.  One has to rebuild the format using

context --make; contextjit --make; mtxrun --script plain --make; mtxrunjit --script plain --make

for the changes to take effect.


--- typo-brk.lua        2016-10-12 11:15:31.769189346 +0200
+++ typo-brk.lua        2016-10-12 11:16:16.897979419 +0200
@@ -272,6 +272,7 @@
                 if map then
                     local cmap = map[char]
                     if cmap then
+                        setattr(current,a_breakpoints,unsetvalue) -- should not be needed
                         -- for now we collect but when found ok we can move the handler here
                         -- although it saves nothing in terms of performance
                         local lang = getfield(current,"lang")
@@ -301,7 +302,6 @@
                         else
                             current = getnext(current)
                         end
-                        setattr(start,a_breakpoints,unsetvalue) -- should not be needed
                     else
                         current = getnext(current)
                     end


On 10/11/2016 03:45 PM, Mojca Miklavec wrote:
> On 11 October 2016 at 15:33, Henri Menke wrote:
>> On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
>>> On 10 October 2016 at 15:31, Henri Menke wrote:
>>>> I have found another thread reporting the same problem
>>>>
>>>> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>>>>
>>>> However, Hans only replied with »has been fixed already«.
>>>>
>>>> Does anyone know how to find the fix?
>>>
>>> Unless Hans remembers what he fixed exactly, my only idea is doing a
>>> bisection over
>>>     https://bitbucket.org/phg/context-mirror/commits/all
>>
>> Okay.  This does not make *any* sense!  I started merging files until the bug disappeared and it happened when I merged cont-new.mkiv.  The diff is
>>
>> -\newcontextversion{2016.05.17 10:06}
>> +\newcontextversion{2016.07.01 16:28}
>>
>> So this is basically the version number.  Can someone enlighten me what is going on?
> 
> I would suspect that changing the version number triggers regenerating
> the formats. Most likely one of the other files fixed the problem, but
> the problem only disappeared once you regenerated the format. That's
> pure guesswork though.
> 
> Mojca
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context at ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 



More information about the ntg-context mailing list