Hi Tim,
I misunderstood your goal, sorry. Proposed setup below.
But first, what I think is a bug in ConTeXt:
Neither
\setupcaptions
[counter=object]
nor
\setupcaption
[figure]
[counter=object]
work. the caption always falls back to the ‘current float counter’; figure or
table
Thank you for fixing this!
On Thu, Aug 13, 2020 at 02:31:51PM +0200, Marcel Fabian Krüger wrote:
> Hi,
>
> in the current luametatex upload, \scantokens (and also \scantextokens)
> behave odd: They seem to act like \detokenize, except that spaces get
> catcode other instead of catcode space:
>
On 8/14/2020 7:11 PM, Alan Bowen wrote:
Hi—
I have just installed (clean) the latest lmtx.
Processing
\starttext
Hello world!
\stoptext
fails with this error message:
Fatal Error > Your format does not match the base files!
Format Version > 2020.08.14 18:28 LMTX
Files Version >
Hi—
I have just installed (clean) the latest lmtx.
Processing
\starttext
Hello world!
\stoptext
fails with this error message:
Fatal Error > Your format does not match the base files!
Format Version > 2020.08.14 18:28 LMTX
Files Version > 2020.08.14 18:27
Alan
Hello Lutz,
I can confirm this. Compiling luametafun.tex (see luametafun.zip; I
included the log-file, but the log-file doesn't include all the output I
can see on the console (therefore I included the file output_console.txt
with a copy of my console-output). I used linux aarch64.
Yes,
On 8/14/2020 1:38 PM, Lutz Haseloff wrote:
Hi all
I have a similar problem compiling luametafun.tex in the doc sources.
It fails with different errorcodes on win64 and linux aarch64. On linux
aarch64 i get a bonus "Segmentation fault".
I append the console outputs of the context runs.
If i
Hi Wolfgang,
thats a little bit difficult, because the error apparently happens at a
random position in the document (you can add a syntax error in the
document an change the position of the syntax error in the document
until lmtx crashes before it detects the error to get the paragraph
where
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
in
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
in
Hello Hans,
I get the error with the newest upload too.
Jannik
Am 14.08.20 um 08:47 schrieb Hans Hagen:
> On 8/14/2020 2:38 AM, Jannik Voges wrote:
>>
>> Hello,
>>
>>
>> I have a similar problem with long context-documents (but not all long
>> context-documents are affected and I don't
Krešimir Cindrić schrieb am 14.08.2020 um 14:28:
Hello,
About a year ago, I asked on this list how to embed OpenType fonts from
files (that is, use fonts that are not installed on the system), because
one of my projects needed portability (be entirely contained in one
directory that I could
Hello,
About a year ago, I asked on this list how to embed OpenType fonts from
files (that is, use fonts that are not installed on the system), because
one of my projects needed portability (be entirely contained in one
directory that I could share). I was given a great answer by Hans and this
Hi all
I have a similar problem compiling luametafun.tex in the doc sources.
It fails with different errorcodes on win64 and linux aarch64. On linux aarch64
i get a bonus "Segmentation fault".
I append the console outputs of the context runs.
If i comment out the input of luametafun-axis and
On 8/14/2020 11:41 AM, Jannik Voges wrote:
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest
On Fri, 14 Aug 2020 at 09:43, Otared Kavian wrote:
>
> Hi Mojca,
>
> You are correct about not removing « by hands » parts of a package…
> The reason for which I wen to that extremity was that I wanted absolutely to
> be sure to be able to run ConTeXt from TeXLive2020 in order to convince a few
Jannik Voges schrieb am 14.08.2020 um 11:29:
Hello Hans,
I get the error with the newest upload too.
You have to provide a minimal example which produces the error.
Wolfgang
___
If your question is of interest
jbf schrieb am 14.08.2020 um 02:28:
I will let the people with far superior knowledge than I have work
through this, but I am following it with interest. All I can say is
that by adopting Aditya's solution, ensuring that for the unnumbered
titles I also included 'number=no', the numbered
Hi Taco,
Thanks for your example and the pointer to make a MWE.
Sadly, it doesn’t work for me. It numbers the first enumeration 1.1.1 and the
first figure _also_ 1.1.1, which I’d like to be 1.1.2.
This time, you’ll find the code and the output pdf in the attachment!
Cheers,
Tim
P.S. I’m on
On 8/14/2020 9:26 AM, Pablo Rodriguez wrote:
Latest from 2020.08.11 works fine for my huge document, but current
latest (from today) breaks compilation. So I use latest from 2020.08.11.
i really need a MWE example then .. all runs well here
Hans
Hi Mojca,
You are correct about not removing « by hands » parts of a package…
The reason for which I wen to that extremity was that I wanted absolutely to be
sure to be able to run ConTeXt from TeXLive2020 in order to convince a few
colleagues to experiment it with TeXShop.
If I type in the
On 8/14/20 8:47 AM, Hans Hagen wrote:
> On 8/14/2020 2:38 AM, Jannik Voges wrote:
>> [...]
>> I have a similar problem with long context-documents (but not all long
>> context-documents are affected and I don't know what triggers the
>> error). Sometimes, the errors (error code 139) are happening
On 8/14/2020 2:38 AM, Jannik Voges wrote:
Hello,
I have a similar problem with long context-documents (but not all long
context-documents are affected and I don't know what triggers the
error). Sometimes, the errors (error code 139) are happening on second
or third runs (but it might happen
On 8/14/2020 1:44 AM, Aditya Mahajan wrote:
On Thu, 13 Aug 2020, Wolfgang Schuster wrote:
Aditya Mahajan schrieb am 13.08.2020 um 04:53:
On Thu, 13 Aug 2020, jbf wrote:
Where running heads (headers) are concerned, if I use \chapter I have no
problems, nor should I expect any. But because I
23 matches
Mail list logo
