ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: directory structure
Date: Tue, 12 Jun 2012 14:35:30 +0200	[thread overview]
Message-ID: <20120612143530.48349318@homerow> (raw)
In-Reply-To: <op.wfkvmul8yxxkfz@pohanka-pc>

On 2012-06-08 "Jan Pohanka" <xhpohanka@gmail.com> wrote:

> Is it also possible to set some global path, where context will
> search the  env files and not to use the full path in document
> file?

Put the files in your local texmf directory: $HOME/texmf/

> Is enviroment  good aproach to define templates?

For general document templates I create modules. They define the
entire document layout. Everything except the content. This makes
sense if the layout is likely to be reused.

I use environments to define individual parts of the layout eg. font
setups, header setup, etc. If the document layout unique to this
particular document I often only use environments.

> template file in some directory on the system: \startenvironment
> myreport ... \setupexternalfigures[directory=???]
> \setupfootertexts[{\externalfigure[mypic]}] ... \stopenvironment

External figures are also found in the local texmf directory.


Marco


___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2012-06-12 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  9:36 Jan Pohanka
2012-06-12 12:35 ` Marco [this message]

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=20120612143530.48349318@homerow \
    --to=netuse@lavabit.com \
    --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).