Is it possible at the end off compile proces to move the created PDF to another
directory (subdirectory of current directory)
You can try something like this:
\startluacode
luatex.wrapup(function()
local pdf = tex.jobname .. ".pdf"
file.copy(pdf,
The TLS certificate for www.pragma-ade.com appears to have expired on
"Thu, 02 Jun 2022 07:37:56 GMT". Firefox and Chrome both give
"Certificate expired" errors when I try and connect. I can still access
the site, although I need to click through a few warnings first.
-- Max
Could anyone confirm the issue or explain me what I am missing?
Confirmed on Win64 with the same version.
But I did find a workaround: if I convert your example from NFC
(composed) to NFD (decomposed), it compiles fine.
$ xxd xml.tex
: 5c75 7365 6d6f 6475 6c65 5b73 6369 7465
Hi Pablo,
The example you gave in your first message about the Scite module, that is:
\usemodule[scite]
\starttext
\startXML ñ\stopXML
\stoptext
gives an error on my machine (MacOS 11.6.5 and Context version 2022.05.11
11:36), with Context saying: « The file ended when scanning an
> On 4 Jun 2022, at 06:21, Jaroslav Hajtmar via ntg-context
> wrote:
>
> Hello ConTeXist.
> After a long time, I turn to the conference for help.
> I use command line to batch process of many ConTeXt files. Is it possible at
> the end off compile proces to move the created PDF to another
On 6/4/22 16:13, Otared Kavian via ntg-context wrote:
> Hi Pablo,
>
> Typesetting your two examples, I can reproduce on MacOS and Context
> version 2022.05.11 11:36 what you are reporting.
Many thanks for your help, Otared.
Would you be so kind to confirm the first issue I reported earlier
Hi Pablo,
Typesetting your two examples, I can reproduce on MacOS and Context version
2022.05.11 11:36 what you are reporting.
Best regards: Otared
> On 4 Jun 2022, at 14:11, Pablo Rodriguez via ntg-context
> wrote:
>
> Dear list,
>
> I have my third sample with scite:
>
>
Dear list,
I have my third sample with scite:
\usemodule[scite]
\setuptyping[margin=yes]
\starttext
\startbuffer[b]b\stopbuffer
\startTEXpage[offset=1em]
a \sciteinlinebuffer[none][b] a\par
a \typeinlinebuffer[b][option] a
\stopTEXpage
\stoptext
I’m on Linux64 and using
Dear list,
I have the following sample (running current latest from 2022.05.11
11:36 on Linux64):
\usemodule[scite]
\starttext
\startbuffer[b]b\stopbuffer
\startTEXpage[offset=1em]
a \sciteinlinebuffer[none][b] a\par
a \typeinlinebuffer[b][option] a
\stopTEXpage
\stoptext
I get
rsync: failed to connect to rsync.pragma-ade.nl (213.125.29.165): No route to
host (113)
rsync error: error in socket IO (code 10) at clientserver.c(125)
[Receiver=3.1.2]
___
If your question is of interest to others
rsync: failed to connect to rsync.pragma-ade.nl (213.125.29.165): No route to
host (113)
rsync error: error in socket IO (code 10) at clientserver.c(125)
[Receiver=3.1.2]
___
If your question is of interest to others
Dear list,
I have this minimal sample (with current latest from 2022.05.11 11:36 on
Linux64):
\usemodule[scite]
\starttext
\startXML ñ\stopXML
\stoptext
Commenting out the first line avoids compilation error.
Replacing ñ with n also allows compilation.
I think there may be an error in
On 6/3/22 00:52, Max Chernoff via ntg-context wrote:
>> For the sake of consistency (with buff-imp-xml.lua), I think the patch
>> should read
> > [...]
>> +local alsoname = lpatterns.utf8two + lpatterns.utf8three +
>> lpatterns.utf8four
>
> I think that that pattern is a little too broad,
13 matches
Mail list logo
