Bug#1072682: luametatex: context 2024.04 and luametatex 2.11 no longer build PDF via Pandoc. (+ workaround)
On 7 June 2024 00:39 Preuße, Hilmar, wrote:
> On 06.06.2024 16:03, Gijs Hillenius wrote:
>
> Hi Gijs,
>
>> The log tells me what I reported:
>>
>> " Running pandoc with args: (-f org -t context -o /path/somedocument.pdf --standalone /path/somedocument.tmp44bTvt.org)
>>
>> I can run the same command in a non Emacs terminal:
>>
>
> Are you able to compile a minimal context file e.g.?
>
> \starttext
> Hello, World!
> \stoptext
>
> (call context as "context input.tex") Currently I'm not in my chroot,
> b/c building the format file fails:
>
> tex error > tex error on line 924 in file spac-ali.mkxl: Undefined
> control sequence
>
> <line 3.924>
> \frozen\linebreakcriterion
> \defaultlinebreakcriterion
>
> I'm pretty sure this worked once, else I wouldn't have uploaded that
> stuff to Debian.
Context is at version 2024.04.01.20240428+dfsg-2
and Luametatex is at versoin 2.11.02+ds-4
Here is a silly org-file example, "silly.org"
--8<---------------cut here---------------start------------->8---
#+TITLE: A silly file example
#+AUTHOR: Name
#+BEGIN_EXPORT context
\setupcolors[state=start]
\defineoverlay[WatermarkOverlay]
[{\framed[frame=off,foregroundcolor=Silly!]
{\scale[sx=15,sy=15]
{\rotate[rotation=20.0]{Draft}}}}]
\setupbackgrounds[page][background=WatermarkOverlay]
#+END_EXPORT
There is really nothing to read here. It's just a few random words to
make a sentence, and a paragraph. Add a few more words.
1. This is the first item of a list
2. And this is the second item
http://example.net
--8<---------------cut here---------------end--------------->8---
For which the Emacs org-mode pandoc exporter *today* returns
Running pandoc with args: (-f org -t context -o /home/gijs/tmp/test.pdf --standalone /home/gijs/tmp/test.tmpEL6wFy.org)
Error occured.
Error producing PDF.
tex error > tex error on line 924 in file spac-ali.mkxl: Undefined control sequence
Yesterday it would not mention that" tex error" line. I don't
immediately see which software package/version made that difference.
Reply to: