From: Hans Hagen <j.hagen@xs4all.nl>
To: "ntg-context@ntg.nl >> mailing list for ConTeXt users"
<ntg-context@ntg.nl>
Subject: Re: MKIV: error, no format found with name: cont-en, aborting
Date: Wed, 13 Nov 2019 16:15:07 +0100 [thread overview]
Message-ID: <255ede31-a61c-2007-6204-97c3ebd216c4@xs4all.nl> (raw)
In-Reply-To: <1c9a7336-05fd-ec91-8225-76b9d5203e75@panix.com>
On 11/13/2019 3:01 PM, Rik Kabel wrote:
>
>
> On 11/13/2019 04:14, Hans Hagen wrote:
>> On 11/13/2019 9:51 AM, luigi scarso wrote:
>>> sent from
>>> ** context@rik.users.panix.com <mailto:context@rik.users.panix.com>
>>>
>>> Note from admin: the email is in defer state because
>>> "Message body is too big: 159549 bytes with a limit of 100 KB"
>>> I have kept the initial part.
>>>
>>> """""
>>> Dear list,
>>>
>>> Since the 20191029 update I have not been able to create a document via
>>> MKIV, suffering from the subject error message (error, no format found
>>> with name: cont-en, aborting).
>>>
>>> I have tried cache clearing, regeneration, and complete fresh installs.
>>> None work. I suspect it is something on my system, but cannot think of a
>>> relevant change except possibly a Win10-64 system update.
>>>
>>> Attached is the log from the latest install try (with filenames of
>>> copied files removed).
>>>
>>> LMTX has no problems.
>>>
>>> All suggestions welcome.
>> Also with todays version?
>>
>> Hans
>
> Yes. Just did a fresh install, getting current version: 2019.11.12
> 23:58, and have the same result.
any messages? there should be something
resolvers | formats |
resolvers | formats | format path :
c:/data/develop/tex-context/tex/texmf-cache/luatex-cache/context/764bd4e1ce0f004ab3cec90018f8b80a/formats/luametatex
resolvers | formats | luatex engine : luametatex
resolvers | formats | lua startup file :
c:/data/develop/context/sources/luat-cod.lua
resolvers | formats | context file :
c:/data/develop/context/sources/cont-en.mkxl
resolvers | formats | run time : 10.141 seconds
resolvers | formats | return value : okay
resolvers | formats |
at the end (or some not found messages)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-13 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 8:51 luigi scarso
2019-11-13 9:14 ` Hans Hagen
2019-11-13 14:01 ` Rik Kabel
2019-11-13 15:15 ` Hans Hagen [this message]
2019-11-13 15:54 ` Rik Kabel
2019-11-13 16:14 ` Hans Hagen
2019-11-13 17:09 ` Rik Kabel
2019-11-14 19:08 ` Rik Kabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=255ede31-a61c-2007-6204-97c3ebd216c4@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).