From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Moving the old book-structure to a recent ConTeXt
Date: Thu, 15 Jul 2021 12:19:42 +0200 [thread overview]
Message-ID: <D87F701A-81AF-43BC-B7A1-542BB57C1D55@rna.nl> (raw)
In-Reply-To: <12327120-143B-4E12-AE37-0B75654099A9@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 1464 bytes --]
> On 12 Jul 2021, at 12:15, Henning Hraban Ramm <texml@fiee.net> wrote:
>
>
>
>> Am 12.07.2021 um 10:25 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>>
>> Years ago I wrote a book (Chess and the Art of Enterprise Architecture) using ConTeXt.
>>
>> The setup was (I think Taco’s) basic book project setup, with a chapters, environments, products, etc. subdirectory where you work in the chapters directory and can both produce individual chapters and the whole book. The main tool to produce was texexec.
>>
>> ConTeXt has moved on considerably since then (2014-2015).
>>
>> So, I tried teh old project to see if it still works, but found out it didn’t. There still is a texexec in my MacTeX, but the compilation fails:
>>
>> texexec --pdf --mode=SCREEN ../products/prd_book.tex
>> resolvers | initialization | fatal error: kpse library is accessed (key: original)
>>
>> Is there a new ‘book’ project structure/template for the modern/standalone ConTeXt?
>
> The project struture with project/product/environment/components is still the same.
>
> "texexec" is MkII, you must call "context" for MkIV (with --luatex) and LMTX.
>
> You will probably need to update several setups, there were many changes since MkII.
So, just for confirmation that I understand this correctly, I need to simply change the command from texexec to context --luatex and fix all settings in my setup until I get it working again?
G
[-- Attachment #1.2: Type: text/html, Size: 2286 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2021-07-15 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 8:25 Gerben Wierda
2021-07-12 10:15 ` Henning Hraban Ramm
2021-07-15 10:19 ` Gerben Wierda [this message]
2021-07-15 14:00 ` Henning Hraban Ramm
2021-07-16 13:51 ` Gerben Wierda
2021-07-18 10:37 ` Wolfgang Schuster
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=D87F701A-81AF-43BC-B7A1-542BB57C1D55@rna.nl \
--to=gerben.wierda@rna.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).