From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/115718
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Denis Maier via ntg-context <ntg-context@ntg.nl>
Newsgroups: gmane.comp.tex.context
Subject: Suggestions for project structures,
 environment inheritance, local overrides
Date: Wed, 17 Aug 2022 10:00:09 +0000
Message-ID: <d4e09ad75a0147b7837ddb342cc3b97f@unibe.ch>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============9007639361351304608=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="18219"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: denis.maier@unibe.ch
To: <ntg-context@ntg.nl>
Original-X-From: ntg-context-bounces@ntg.nl Wed Aug 17 12:02:06 2022
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1oOFsE-0004YK-JO
	for gctc-ntg-context-518@m.gmane-mx.org; Wed, 17 Aug 2022 12:02:06 +0200
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 0881C2A3F73;
	Wed, 17 Aug 2022 12:00:22 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2N7QUeG0V-Es; Wed, 17 Aug 2022 12:00:21 +0200 (CEST)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id F0C8B2A3F77;
	Wed, 17 Aug 2022 12:00:19 +0200 (CEST)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id CDF8C2A3F77
 for <ntg-context@ntg.nl>; Wed, 17 Aug 2022 12:00:17 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id pXLVA6ZB3BwN for <ntg-context@ntg.nl>;
 Wed, 17 Aug 2022 12:00:16 +0200 (CEST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=130.92.0.83;
 helo=mailhub-lb2.unibe.ch; envelope-from=denis.maier@unibe.ch;
 receiver=<UNKNOWN> 
Original-Received: from mailhub-lb2.unibe.ch (mailhub-lb2.unibe.ch [130.92.0.83])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 39DCF2A3F76
 for <ntg-context@ntg.nl>; Wed, 17 Aug 2022 12:00:16 +0200 (CEST)
X-Virus-Scanned: By University of Bern - MGW
Original-Received: from mail.campus.unibe.ch (aai-edge-02.campus.unibe.ch
 [130.92.13.148])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mailhub-lb2.unibe.ch (Postfix) with ESMTPS id EADCE50009D
 for <ntg-context@ntg.nl>; Wed, 17 Aug 2022 12:00:09 +0200 (CEST)
Original-Received: from aai-mail-04.campus.unibe.ch (130.92.13.169) by
 AAI-EDGE-02.campus.unibe.ch (130.92.13.148) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id
 15.1.2507.9; Wed, 17 Aug 2022 12:00:03 +0200
Original-Received: from aai-mail-03.campus.unibe.ch (130.92.13.41) by
 aai-mail-04.campus.unibe.ch (130.92.13.169) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id
 15.1.2507.9; Wed, 17 Aug 2022 12:00:09 +0200
Original-Received: from aai-mail-03.campus.unibe.ch ([172.18.73.17]) by
 aai-mail-03.campus.unibe.ch ([172.18.73.17]) with mapi id 15.01.2507.009;
 Wed, 17 Aug 2022 12:00:09 +0200
Thread-Topic: Suggestions for project structures, environment inheritance,
 local overrides
Thread-Index: AdiyHnrc5/W7Cj7MRf2uFHz5ZfKfdA==
Accept-Language: de-CH, en-US
Content-Language: de-DE
x-originating-ip: [130.92.13.161]
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:115718
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/115718>

--===============9007639361351304608==
Content-Language: de-DE
Content-Type: multipart/alternative;
	boundary="_000_d4e09ad75a0147b7837ddb342cc3b97funibech_"

--_000_d4e09ad75a0147b7837ddb342cc3b97funibech_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi everyone

One of my current main projects where I use ConTeXt is typesetting journal =
articles from xml sources. As the journal appears only online, we've decide=
d to publish each article individually. I have a working setup, but I occas=
ionally ponder whether I could make things more smootly. Currently, my fold=
er structure looks roughly like this :

2022
-- _assets
-- article1
---- source
---- md
---- xml
---- pdf
---- html
-- article2
etc.

Usually, I receive Word files that get transformed via pandoc to markdown, =
polished, and from there to XML. HTML is produced via XSLT, PDF via ConTeXt=
. Transformations are performed with the help of a makefile.

The _assets folder contains a bunch of helper files, scripts, and two envir=
onment files used by ConTeXt :
jats.tex -> contains the setup for JATS XML
layout.tex -> contains layout settings

Now, this mostly works, but I sometimes struggle with things like overrides=
/additions for specific articles. Say, I have the global definitions, but I=
 need to make small changes for one specific article? Or, I need to add som=
ething to one specific article, but I don't want to add this to the  <envir=
onment> files. I guess my question is something like this :

- How could a painless solution for such a scenario look like?
- Should you just load multiple environment files and override earlier sett=
ings? (How would that work with xml setups?)

Best,
Denis

--_000_d4e09ad75a0147b7837ddb342cc3b97funibech_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"DE-CH" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi everyone<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">One of my current main projects=
 where I use ConTeXt is typesetting journal articles from xml sources. As t=
he journal appears only online, we&#8217;ve decided to publish each article=
 individually. I have a working setup, but
 I occasionally ponder whether I could make things more smootly. Currently,=
 my folder structure looks roughly like this&nbsp;:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">2022<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">-- _assets<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">-- article1<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">---- source<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">---- md<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">---- xml<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">---- pdf<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">---- html<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">-- article2<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">etc.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Usually, I receive Word files that get transformed v=
ia pandoc to markdown, polished, and from there to XML.
<span lang=3D"FR-CH">HTML is produced via XSLT, PDF via ConTeXt. Transforma=
tions are performed with the help of a makefile.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">The _assets folder contains a b=
unch of helper files, scripts, and two environment files used by ConTeXt&nb=
sp;:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">jats.tex -&gt; contains the set=
up for JATS XML<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">layout.tex -&gt; contains layou=
t settings<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">Now, this mostly works, but I s=
ometimes struggle with things like overrides/additions for specific article=
s. Say, I have the global definitions, but I need to make small changes for=
 one specific article? Or, I need to
 add something to one specific article, but I don&#8217;t want to add this =
to the&nbsp; &laquo;environment&raquo; files. I guess my question is someth=
ing like this&nbsp;:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">- How could a painless solution=
 for such a scenario look like?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH">- Should you just load multiple=
 environment files and override earlier settings? (How would that work with=
 xml setups?)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CH"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Best,<o:p></o:p></p>
<p class=3D"MsoNormal">Denis<o:p></o:p></p>
</div>
</body>
</html>

--_000_d4e09ad75a0147b7837ddb342cc3b97funibech_--

--===============9007639361351304608==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cHM6Ly93d3cubnRnLm5sL21haWxtYW4v
bGlzdGluZm8vbnRnLWNvbnRleHQKd2VicGFnZSAgOiBodHRwczovL3d3dy5wcmFnbWEtYWRlLm5s
IC8gaHR0cDovL2NvbnRleHQuYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHBzOi8vYml0YnVja2V0
Lm9yZy9waGcvY29udGV4dC1taXJyb3IvY29tbWl0cy8Kd2lraSAgICAgOiBodHRwczovL2NvbnRl
eHRnYXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============9007639361351304608==--