Hi, I uploaded a beta (with an seeindex fix). If you use betas for production, best save your current one as there are some changes deep down in the pdf inclusion. This relates to upcoming luatex using different pdf inclusion code in the backend (plus a new pdf library that replaces the current one). I don't expect real problems but i might have touched some context code in the process with possible side effects. Nothing that can't be fixed easily. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Tested with my setup, which -- you know -- is quite complex. This is the only error: lua error > lua error on line 6 in file /home/massi/context/latest/tex/texmf- context/tex/context/base/mkiv/cont-yes.mkiv: ...est/tex/texmf-context/tex/context/base/mkiv/grph-inc.lua:1398: image.ownerpassword can not be set stack traceback: [C]: in function 'img.new' ...est/tex/texmf-context/tex/context/base/mkiv/grph- inc.lua:1398: in function <...est/tex/texmf- context/tex/context/base/mkiv/grph-inc.lua:1364> (...tail calls...) The error is triggered by this line: context( "\\setlayer[layername]{\\externalfigure[figure.pdf][scale=900]}" ) Since it's a pdf figure, it should be linked to the new pdf library. Best wishes, Massi
MF mailto:massifr@fastwebnet.it 22. Juni 2018 um 16:36 Tested with my setup, which -- you know -- is quite complex. This is the only error:
lua error > lua error on line 6 in file /home/massi/context/latest/tex/texmf- context/tex/context/base/mkiv/cont-yes.mkiv:
...est/tex/texmf-context/tex/context/base/mkiv/grph-inc.lua:1398: image.ownerpassword can not be set stack traceback: [C]: in function 'img.new' ...est/tex/texmf-context/tex/context/base/mkiv/grph- inc.lua:1398: in function <...est/tex/texmf- context/tex/context/base/mkiv/grph-inc.lua:1364> (...tail calls...)
The error is triggered by this line:
context( "\\setlayer[layername]{\\externalfigure[figure.pdf][scale=900]}" )
Since it's a pdf figure, it should be linked to the new pdf library.
Do you get the same error message with the following minimal example: \starttext \externalfigure[figure] \stoptext Wolfgang
MF mailto:massifr@fastwebnet.it 22. Juni 2018 um 17:46
Yes, of course, same error; BTW, the pdf i'm using is not password protected.
I’m getting the same message as you when I try to insert pdf file created by context itself %%%% begin example \starttext \startbuffer Can this file be loaded? \stopbuffer \typesetbuffer[scale=500] \stoptext %%%% end example or when I try to insert cow.pdf %%%% begin example \setupexternalfigure[location=default] \starttext \externalfigure[cow] \stoptext %%%% end example Wolfgang
Am Fri, 22 Jun 2018 17:30:46 +0200 schrieb Wolfgang Schuster:
...est/tex/texmf-context/tex/context/base/mkiv/grph-inc.lua:1398: image.ownerpassword can not be set stack traceback:
Do you get the same error message with the following minimal example:
I get the same error after the update with \starttext \externalfigure[A] \stoptext where A.pdf is in the current folder. I'm on windows 10. -- Ulrike Fischer http://www.troubleshooting-tex.de/
On 6/22/2018 4:36 PM, MF wrote:
Tested with my setup, which -- you know -- is quite complex. This is the only error:
lua error > lua error on line 6 in file /home/massi/context/latest/tex/texmf- context/tex/context/base/mkiv/cont-yes.mkiv:
...est/tex/texmf-context/tex/context/base/mkiv/grph-inc.lua:1398: image.ownerpassword can not be set stack traceback: [C]: in function 'img.new' ...est/tex/texmf-context/tex/context/base/mkiv/grph- inc.lua:1398: in function <...est/tex/texmf- context/tex/context/base/mkiv/grph-inc.lua:1364> (...tail calls...)
The error is triggered by this line:
context( "\\setlayer[layername]{\\externalfigure[figure.pdf][scale=900]}" )
Since it's a pdf figure, it should be linked to the new pdf library. no, more to a bit strick checking in image settings in the old bin (less strct in latest bin)
i'll fix it ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Am Fri, 22 Jun 2018 16:09:26 +0200 schrieb Hans Hagen:
I uploaded a beta (with an seeindex fix).
I still get an error about a missing function registersplit when using the new generic loader together with luaotfload. Looking at the code I can see that there is an "if context" switch around the relevant part (around line 34058): definers.makespecification=makespecification if context then --<<<<<<<<< local splitter,splitspecifiers=nil,"" ... Removing this (and the "end" naturally) then it worked fine. -- Ulrike Fischer http://www.troubleshooting-tex.de/
On 6/22/2018 6:07 PM, Ulrike Fischer wrote:
Am Fri, 22 Jun 2018 16:09:26 +0200 schrieb Hans Hagen:
I uploaded a beta (with an seeindex fix).
I still get an error about a missing function registersplit when using the new generic loader together with luaotfload.
Looking at the code I can see that there is an "if context" switch around the relevant part (around line 34058):
definers.makespecification=makespecification if context then --<<<<<<<<< local splitter,splitspecifiers=nil,"" ...
Removing this (and the "end" naturally) then it worked fine. don't use register split in luaotfload ... look in luatex-fonts.lua etc to soo how to analyze the name .. splitters are something context specific
Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Am Sat, 23 Jun 2018 12:12:05 +0200 schrieb Hans Hagen:
don't use register split in luaotfload ... look in luatex-fonts.lua etc to soo how to analyze the name .. splitters are something context specific
It looks as if we managed to get it working in luaotfload. We are trying to setup test files. But normalization of the log-files are complicate as the fontloader uses in various places texio.write. E.g texio.write(format("(load luc: %s)",lucname)) Would it be possible to change this to some log-function which could be adapted for the tests (so that e.g. newlines could be inserted and the path stripped from file names)? -- Ulrike Fischer http://www.troubleshooting-tex.de/
participants (4)
-
Hans Hagen -
MF -
Ulrike Fischer -
Wolfgang Schuster