Re: [NTG-context] Making ConTeXt stop on all or some errors
Am 06.02.19 um 19:31 schrieb Pablo Rodriguez:
> On 2/5/19 8:07 AM, Jan U. Hasecke wrote:
>> Hola Pablo,
>
> Hallo Jan-Ulrich,
>
>> I inserted this in the setupbackend command so that ConTeXt stops with
>> the unknown command \colorprofilenotfound I inserted in the else clause.
>>
>> But more and more I think that ConTeXt should fail if it does not find
>> the color profile, because if you forget to study the log file before
>> sending the pdf to the print shop you can loose a lot of money.
>
> But the scenarios in which you could loose a lot of money are many more
> than you might think.
>
> Imagine the following:
>
> \startbuffer
> A Greek sentence:
> χαλεπὰ τὰ καλά
> \stopbuffer
> \definefallbackfamily[mainface][rm][GFS Didoto]
> [preset=range:greek]
> \definefontfamily[mainface][rm][Latin Modern Roman]
> \definefallbackfamily[amainface][rm][GFS Didot]
> [preset=range:greek]
> \definefontfamily[amainface][rm][TeX Gyre Pagella]
> \definefallbackfamily[smainface][rm][GFS Didot]
> [preset=range:greek, force=yes]
> \definefontfamily[smainface][rm][TeX Gyre Pagella]
> \setupbodyfont[mainface]
> \starttext
> \startTEXpage[offset=2em]
> \getbuffer\\
> \amainface\getbuffer\\
> \smainface\getbuffer
> \stopTEXpage
> \stoptext
>
> Not embedding all glyphs for the fallback font (failing to type
> "force=yes") could lead to weird results. Not to mention when a font
> isn’t embedded at all.
>
>> And as we use ConTeXt in a group where people have different ConTeXt
>> knowledge the generation should be bullet proofed.
>
> I totally agree with that. But it mainly relies on how source documents
> are written. ConTeXt cannot type the source for us.
>
>> The behaviour of ConTeXt is AFAICS the following.
>> If you install icc-profiles in texmf-context they get lost during the
>> next update of ConTeXt. But ConTeXt will not stop the complilation only
>> warning that there is no profile file.
>>
>> ConTeXt only stops to compile if you delete a profile which was present
>> during installation/update or which was present during a "mtxrun
>> --generate" (Thanks to Mojca for this hint). Then the file is registered
>> and ConTeXt wants to access it, failing if it is not there.
>>
>> If you install profiles in texmf-local and then do a "mtxrun --generate"
>> you are quite safe as long as you do not install ConTeXt from scratch.
>
> No computer can read your mind. Or a brand-new installation cannot guess
> whether you are up to some auxiliary files (name them color profiles,
> fonts, or whatever you want).
>
>> If you want to compile a ConTeXt project on an other computer you have
>> to study the log file to see that it does not find a color profile. And
>> this is dangerous, because none expects this to be a problem. I think
>> ConTeXt should fail and stop if the profile is not there.
>
> But checking if the file exists is a safe way to know whehter it can be
> embedded in the output PDF document.
>
> Another scenario would be attaching files to a PDF document using the
> \attachment command. I have done it myself.
>
> With some of my documents, I had to attach a variable number of extra
> documents to the final PDF. The only way to secure the attachment was
> \doiffileelse{file.pdf}{\attach[file.pdf]}{\ssbf\color[red]{missing
> attachment}}.
>
> Just in case it helps,
Yes, your solution helps and I use it for now.
But I am still looking for a switch to have a nitpickier runlevel of
ConTeXt. From the documentation suite Sphinx I know such a switch which
turns warnings into errors (causing Sphinx to stop) and vice versa.
At least a missing file should make ConTeXt stop immediately.
juh
___
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: [NTG-context] Failure using --jit with latest beta
On 2/6/2019 9:24 PM, Joseph Canedo wrote: Yes, it works fine. I’ll amend my build script. it's also more efficient to call contextjit or mtxrunjit 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 - ___ 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: [NTG-context] Adjusting interlinespace in a table
Mari Voipio schrieb am 05.02.19 um 09:21:
Hello all!
This may be a really stupid question, but wiki wasn't helpful: Is
there a way of adjusting interlinespace in a table? A \setupTABLE
command would work as I want to change the line height throughout the
table to make it smaller (have the rows closer to each other than in
my running text). I don't need to set the cell height or anything like
that, I just want to adjust the text inside the cells. I'm fairly
certain there's some simple way of doing it...
\starttext
\bTABLE
\bTR
\bTD
\samplefile{tufte}
\eTD
\bTD[style={\setupinterlinespace[line=2.4ex]}]
\samplefile{tufte}
\eTD
\eTR
\eTABLE
\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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Failure using --jit with latest beta
Yes, it works fine. I’ll amend my build script. Thanks a lot Joseph Provenance : Courrier pour Windows 10 De : Hans Hagen Envoyé le :mercredi 6 février 2019 09:47 À : mailing list for ConTeXt users; Joseph Canedo Objet :Re: [NTG-context] Failure using --jit with latest beta On 2/5/2019 11:31 PM, Joseph Canedo wrote: > Dear list, > > I get a fatal error when using –jit using latest beta. > > $ ./build.sh Livre.pdf > > [1/1] context --noconsole --jit --errors Livre.tex > > FAILED: Livre.pdf > > context --noconsole --jit --errors Livre.tex > > mtx-context | run 1: luajittex > --fmt="c:/ConTeXt/test/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en" > > --jobname="Livre" > --lua="c:/ConTeXt/test/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui" > > --c:currentrun=1 --c:directives="logs.errors,logs.target=file" > --c:engine="luajittex" --c:errors --c:fulljobname="./Livre.tex" > --c:input="./Livre.tex" --c:jit --c:kindofrun=1 --c:maxnofruns=9 > --c:noconsole --c:texmfbinpath="c:/ConTeXt/test/tex/texmf-win64/bin" > "cont-yes.mkiv" > > This is LuajitTeX, Version 1.09.2 (TeX Live 2018/W32TeX) > > system commands enabled. > > *---! > c:/ConTeXt/test/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.fmt > > was written by luatex* > > *(Fatal format file error; I'm stymied)mtx-context | fatal error: > return code: 1* > > It works all fine without --lit option. Was the support LuaJitTeX > removed now ? does "contextjit ... " work? - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] right figure at bottom of page can narrow text block on whole next page
> This has come up a few times on this list. Hans has stated a reluctance > to make a change or add an option to discard the unused vertical space > (see https://www.mail-archive.com/ntg-context@ntg.nl/msg21273.html from > March 2007, and most recently > https://www.mail-archive.com/ntg-context@ntg.nl/msg86872.html in January > 2018). Thank you for those pointers. > The workaround that Hans suggests in that last post , adding the flag > 'high', almost resolves the issue in your example. Right -- or just shifting the figure upward by one paragraph or so. In a long document like a book, pagebreaks need to be adjusted by hand at the end anyway to avoid long stretches of unused bottom space. Adjusting the figure placements slightly can become part of that process. -Sanjoy ___ 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: [NTG-context] Making ConTeXt stop on all or some errors
On 2/5/19 8:07 AM, Jan U. Hasecke wrote:
> Hola Pablo,
Hallo Jan-Ulrich,
> I inserted this in the setupbackend command so that ConTeXt stops with
> the unknown command \colorprofilenotfound I inserted in the else clause.
>
> But more and more I think that ConTeXt should fail if it does not find
> the color profile, because if you forget to study the log file before
> sending the pdf to the print shop you can loose a lot of money.
But the scenarios in which you could loose a lot of money are many more
than you might think.
Imagine the following:
\startbuffer
A Greek sentence:
χαλεπὰ τὰ καλά
\stopbuffer
\definefallbackfamily[mainface][rm][GFS Didoto]
[preset=range:greek]
\definefontfamily[mainface][rm][Latin Modern Roman]
\definefallbackfamily[amainface][rm][GFS Didot]
[preset=range:greek]
\definefontfamily[amainface][rm][TeX Gyre Pagella]
\definefallbackfamily[smainface][rm][GFS Didot]
[preset=range:greek, force=yes]
\definefontfamily[smainface][rm][TeX Gyre Pagella]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=2em]
\getbuffer\\
\amainface\getbuffer\\
\smainface\getbuffer
\stopTEXpage
\stoptext
Not embedding all glyphs for the fallback font (failing to type
"force=yes") could lead to weird results. Not to mention when a font
isn’t embedded at all.
> And as we use ConTeXt in a group where people have different ConTeXt
> knowledge the generation should be bullet proofed.
I totally agree with that. But it mainly relies on how source documents
are written. ConTeXt cannot type the source for us.
> The behaviour of ConTeXt is AFAICS the following.
> If you install icc-profiles in texmf-context they get lost during the
> next update of ConTeXt. But ConTeXt will not stop the complilation only
> warning that there is no profile file.
>
> ConTeXt only stops to compile if you delete a profile which was present
> during installation/update or which was present during a "mtxrun
> --generate" (Thanks to Mojca for this hint). Then the file is registered
> and ConTeXt wants to access it, failing if it is not there.
>
> If you install profiles in texmf-local and then do a "mtxrun --generate"
> you are quite safe as long as you do not install ConTeXt from scratch.
No computer can read your mind. Or a brand-new installation cannot guess
whether you are up to some auxiliary files (name them color profiles,
fonts, or whatever you want).
> If you want to compile a ConTeXt project on an other computer you have
> to study the log file to see that it does not find a color profile. And
> this is dangerous, because none expects this to be a problem. I think
> ConTeXt should fail and stop if the profile is not there.
But checking if the file exists is a safe way to know whehter it can be
embedded in the output PDF document.
Another scenario would be attaching files to a PDF document using the
\attachment command. I have done it myself.
With some of my documents, I had to attach a variable number of extra
documents to the final PDF. The only way to secure the attachment was
\doiffileelse{file.pdf}{\attach[file.pdf]}{\ssbf\color[red]{missing
attachment}}.
Just in case it helps,
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: [NTG-context] right figure at bottom of page can narrow text block on whole next page
On 1/29/2019 06:48, Sanjoy Mahajan wrote:
\definepapersize[bookcrop][width=137mm,height=221mm]
\setuppapersize [bookcrop][bookcrop]
\setuplayout[marking=on,
location=middle,
backspace=13.5mm,
width=middle,
topspace=32bp,
header=10bp, headerdistance=26bp,
footerdistance=16bp, footer=10bp,
height=578bp,
]
\setupinterlinespace[line=1.3em]
\setupbodyfont[times,10bp]
\starttext
\input knuth
Silly para
Silly para
\placefigure[right]{}{\framed[width=100bp,height=75.75bp]{\null}}
\input knuth
\dorecurse{8}{\par Silly para}
\placefigure[right]{}{\framed[width=100bp,height=60.75bp]{\null}}
\dorecurse{32}{Silly text }
\dorecurse{3}{\input knuth \par}
\stoptext
This has come up a few times on this list. Hans has stated a reluctance
to make a change or add an option to discard the unused vertical space
(see https://www.mail-archive.com/ntg-context@ntg.nl/msg21273.html from
March 2007, and most recently
https://www.mail-archive.com/ntg-context@ntg.nl/msg86872.html in January
2018).
The workaround that Hans suggests in that last post , adding the flag
'high', almost resolves the issue in your example.
--
Rik
___
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: [NTG-context] hysteresis with content in blocks (one strike and you can be out forever)
> You can set dimensions with the measure system
>
> %\definemeasure [TestValue] [20pt]
>
> \starttext
> \measure{TestValue}
> \stoptext
>
> and other values with \setvariables
>
> %\setvariables [test] [abc=20]
Probably the .tuc hystersis can jump up and bite one in the rear end in
other ways. But \definemeasure and \setvariables do solve the issue in
my example. They were also new to me and should prove useful for my
style files. (The amount of ConTeXt still to learn is very large...)
-Sanjoy
___
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: [NTG-context] hysteresis with content in blocks (one strike and you can be out forever)
Sanjoy Mahajan schrieb am 06.02.19 um 16:53:
Apologies for the cutesy subtitle. In plainer English, the information
saved in the .tuc file can make it so that a valid ConTeXt file doesn't
compile merely because of what it contained when it was compiled before.
Here is a MIE (minimal illustrative example), on Linux amd64, 2019.01.28 beta:
1. Make the following file:
== file: testhysteresis.tex ===
\defineblock[foo]
\starttext
\def\abc{20}
\beginfoo
Use \abc
\endfoo
\useblocks[foo]
\stoptext
== stop: testhysteresis.tex ===
2. Compile it with "context --nonstopmode testhysteresis.tex" (which
will work fine).
3. Modify it so that it doesn't define or use \abc (and so that it is
still valid):
== file: testhysteresis.tex ===
\defineblock[foo]
\starttext
\beginfoo
Use
\endfoo
\useblocks[foo]
\stoptext
== stop: testhysteresis.tex ===
4. Without deleting testhysteresis.tuc, recompile with "context
--nonstopmode testhysteresis.tex". This run fails with the fatal error:
tex error > tex error on line 1 in file virtual://block.foo.1: !
Undefined control sequence
l.1 Use \abc
The cause seems to be that testhysteresis.tuc contains (from the run
it step 2 above):
utilitydata.structures.blocks.collected={
{
["data"]="Use \\abc",
["index"]=1,
["metadata"]=3,
["references"]={
["section"]=0,
},
},
}
5. Delete testhysteresis.tuc.
6. Now "context --nonstopmode testhysteresis.tex" works fine.
One workaround is always to delete the .tuc file before running context.
But that approach seems like overkill (although in my scripts that I use
for running expeirments with blocks etc., I take this approach), and
maybe there is a simpler way.
You can set dimensions with the measure system
%\definemeasure [TestValue] [20pt]
\starttext
\measure{TestValue}
\stoptext
and other values with \setvariables
%\setvariables [test] [abc=20]
\starttext
\getvariable{test}{abc}
\getvariabledefault{test}{abc}{10}
\stoptext
Both systems work even with unset values.
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] hysteresis with content in blocks (one strike and you can be out forever)
Apologies for the cutesy subtitle. In plainer English, the information
saved in the .tuc file can make it so that a valid ConTeXt file doesn't
compile merely because of what it contained when it was compiled before.
Here is a MIE (minimal illustrative example), on Linux amd64, 2019.01.28 beta:
1. Make the following file:
== file: testhysteresis.tex ===
\defineblock[foo]
\starttext
\def\abc{20}
\beginfoo
Use \abc
\endfoo
\useblocks[foo]
\stoptext
== stop: testhysteresis.tex ===
2. Compile it with "context --nonstopmode testhysteresis.tex" (which
will work fine).
3. Modify it so that it doesn't define or use \abc (and so that it is
still valid):
== file: testhysteresis.tex ===
\defineblock[foo]
\starttext
\beginfoo
Use
\endfoo
\useblocks[foo]
\stoptext
== stop: testhysteresis.tex ===
4. Without deleting testhysteresis.tuc, recompile with "context
--nonstopmode testhysteresis.tex". This run fails with the fatal error:
tex error > tex error on line 1 in file virtual://block.foo.1: !
Undefined control sequence
l.1 Use \abc
The cause seems to be that testhysteresis.tuc contains (from the run
it step 2 above):
utilitydata.structures.blocks.collected={
{
["data"]="Use \\abc",
["index"]=1,
["metadata"]=3,
["references"]={
["section"]=0,
},
},
}
5. Delete testhysteresis.tuc.
6. Now "context --nonstopmode testhysteresis.tex" works fine.
One workaround is always to delete the .tuc file before running context.
But that approach seems like overkill (although in my scripts that I use
for running expeirments with blocks etc., I take this approach), and
maybe there is a simpler way.
Best,
-Sanjoy
___
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: [NTG-context] constructing block content partly with lua
On 2019-02-05 17:21, Hans Hagen wrote:
> i'm not sure what you want but thsi might give a clue
> ...
> \startluacode
> buffers.assign("temp","test 2")
> structures.blocks.save("foo",nil,nil,"temp")
> \stopluacode
Ah, thanks, that looks like what I need, or at least part of it, and
will keep me busy making more experiments.
-Sanjoy
___
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
___
[NTG-context] Nested fences, inner one changes size with outer one
Hi,
Is it possible to automatically have the inner fence _not_ change its
size with the outer one?
/Mikael
\definemathfence[Openinterval][left="0028,right="0029,command=yes]
\definemathfence[Set][left="007B,right="007D,command=yes]
\starttext
\startTEXpage[offset=3bp]
Nothing fancy here:
\startformula
\Set{\Openinterval{-n,n}~:~n\in\mathbb N}
\stopformula
Here, I would expect the parenthesis to be of small size:
\startformula
\Set[size=1]{\Openinterval{-n,n}~:~n\in\mathbb N}
\stopformula
This works, but it would be nice not to be forced to write
\type{[size=0]} in the inner construct:
\startformula
\Set[size=1]{\Openinterval[size=0]{-n,n}~:~n\in\mathbb N}
\stopformula
\stopTEXpage
\stoptext
nestedfences.pdf
Description: Adobe PDF document
___
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: [NTG-context] text flowing around images
Am 2019-02-06 um 00:19 schrieb Aditya Mahajan : > On Tue, 5 Feb 2019, Wolfgang Schuster wrote: > Am 2019-02-04 um 11:10 schrieb Henning Hraban Ramm : > Ahoi, > > in my current project I must include a bunch of illustrations in my >> layout, and the text should flow around their irregular shapes (side >> placement in single text column only). > I got the pictures as TIFFs with alpha channel, but of course I can >> change that. > > I’m quite sure I remember that it was possible to let text flow around >> shapes somehow, but I can’t find documentation or a sample. > I’d be thankful for hints. > >> The metafun manual should have a few examples. >> > See https://tex.stackexchange.com/a/32308/323 which is based on an example in > the metafun manual. Thank you all! I guess I can reduce the flow cases to <10 and use \parshape directly; thinking in lines looks a bit easier than the MetaPost way. Calculating the MP path from the TIFF alpha channel would be interesting, but is way above my head. I guess it would work like: * preprocessing: - find the outer contour of the image (after some threshold value of color value or alpha channel) - simplify and vectorize that (I remember there were different OS tools/libraries used with FontForge or Inkscape) - convert this outline (SVG or EPS I guess) into MP * within the ConTeXt run: - place the (scaled) picture - preliminary page/paragraph breaking to find where there might be overlaps - calculate the fitting paragraph shape (rectangle minus overlapping part of the scaled outline) - probably some new line/paragraph breaking? Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD ___ 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: [NTG-context] problem with non-printing hex 0x0C
On 2/5/2019 9:28 PM, martin wrote: I had a problem that kept me busy for a few hours. A \page command had no effect, the text just continued in the pdf. The culprid turned out to be a hex 0x0C, a formfeed character. Once I removed them all was good. It got introduced by extracting the text from a PDF. I realize my files should be "clean" of control characters and ConTexT should (maybe) not be stripping those characters. Then again, they serve no purpose in the document. So... My question: Isn't some more resilience sensible so commands don't break? Or error messages? a formfeed is acting like a newline \catcode\tabasciicode \spacecatcode \catcode\endoflineasciicode \endoflinecatcode \catcode\formfeedasciicode \endoflinecatcode \catcode\spaceasciicode \spacecatcode - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Failure using --jit with latest beta
On 2/5/2019 11:31 PM, Joseph Canedo wrote: Dear list, I get a fatal error when using –jit using latest beta. $ ./build.sh Livre.pdf [1/1] context --noconsole --jit --errors Livre.tex FAILED: Livre.pdf context --noconsole --jit --errors Livre.tex mtx-context | run 1: luajittex --fmt="c:/ConTeXt/test/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en" --jobname="Livre" --lua="c:/ConTeXt/test/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui" --c:currentrun=1 --c:directives="logs.errors,logs.target=file" --c:engine="luajittex" --c:errors --c:fulljobname="./Livre.tex" --c:input="./Livre.tex" --c:jit --c:kindofrun=1 --c:maxnofruns=9 --c:noconsole --c:texmfbinpath="c:/ConTeXt/test/tex/texmf-win64/bin" "cont-yes.mkiv" This is LuajitTeX, Version 1.09.2 (TeX Live 2018/W32TeX) system commands enabled. *---! c:/ConTeXt/test/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.fmt was written by luatex* *(Fatal format file error; I'm stymied)mtx-context | fatal error: return code: 1* It works all fine without --lit option. Was the support LuaJitTeX removed now ? does "contextjit ... " work? - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
