From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Input order of modular environment files
Date: Tue, 28 Jul 2015 23:15:50 +0200 [thread overview]
Message-ID: <55B7F106.1020603@wxs.nl> (raw)
In-Reply-To: <55B7C35D.6080605@mailbox.org>
On 7/28/2015 8:01 PM, juh wrote:
> Hi all,
>
> inspired by [1] I want to setup modular environment files and include
> them on demand with the option --environment.
>
> I think that I will have separate files for general settings, for fonts
> and for different papersizes, so that I can typeset with different
> settings on-the-fly.
>
> Is there an order in which definitions must be made, for eg. fonts
> first, pagelayouts second etc...?
in most cases the order of settings is irrelevant as for instance colors
and styles are delayed and related dimensions are synchronized
> Do you have any recommendations how I should structure the environments?
>
> I am going to compile XML files, so I will also have an environment file
> which defines the XML-TeX mapping.
>
> Ciao
> juh
>
> [1] http://pragma-ade.com/general/magazines/mag-1101.pdf
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-07-28 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 18:01 juh
2015-07-28 21:15 ` Hans Hagen [this message]
2015-07-29 6:07 ` juh
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=55B7F106.1020603@wxs.nl \
--to=pragma@wxs.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).