From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with letter module
Date: Sat, 21 Jan 2012 10:12:11 +0100 [thread overview]
Message-ID: <E154BBAD-5995-4BA9-ABC5-76F426C4D4CB@googlemail.com> (raw)
In-Reply-To: <201201202244.45697.romain.diss@yahoo.fr>
Am 20.01.2012 um 22:44 schrieb Romain Diss:
> Just by curiosity, if none of the t-letter.* files are loaded, how does context
> know that it have to load the s-cor-* files when I type \usemodule[letter]?
When you load a module with \usemodule[<name>] context looks first
if it can find a file with the name t-<name>, s-<name> etc. and it does
also check for any file which this naming system with different extensions
(e.g. *.mkiv and *.tex for MkIV) but there is another search method.
When you take a look into the base folder you can see that Hans
presentation styles have names in the form s-pre-xx.tex where xx
is a number but the wiki says you load them with \usemodule[pre-<name>]
where <name> can be “fuzzy” or “shade”. The mapping from s-pre-fuzzy.tex
(the synonym) to s-pre-05.tex (the file name) is done with the
\definefilesynonym command where you can give files a symbolic name.
There is no a additional step when you load a module, \usemodule
looks first if the name of the module you requested is a synonym and
when this is the case it looks for the real file again with the lookup method
given in the first paragraph. When take a look into cont-fil.mkiv you can
see that there is also a synonym for the letter module
\definefilesynonym [letter] [cor-01]
which loads the file s-cor-01.mkvi when you write \usemodule[letter].
Wolfgang
___________________________________________________________________________________
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:[~2012-01-21 9:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 20:14 Romain Diss
2012-01-18 23:21 ` Wolfgang Schuster
2012-01-19 14:28 ` Romain Diss
2012-01-19 19:52 ` Wolfgang Schuster
2012-01-19 22:06 ` Romain Diss
2012-01-19 22:24 ` Wolfgang Schuster
2012-01-19 22:57 ` Romain Diss
2012-01-19 23:05 ` Wolfgang Schuster
2012-01-19 23:20 ` Romain Diss
2012-01-19 23:59 ` Wolfgang Schuster
2012-01-20 21:44 ` Romain Diss
2012-01-21 0:16 ` Hans Hagen
2012-01-21 9:12 ` Wolfgang Schuster [this message]
2012-01-19 14:28 ` Romain Diss
2012-01-19 22:08 ` Wolfgang Schuster
2012-02-05 23:05 ` Henning Hraban Ramm
2012-02-06 11:40 ` Wolfgang Schuster
[not found] <mailman.1854.1326987164.4232.ntg-context@ntg.nl>
2012-01-19 17:47 ` Michael Green
2012-01-19 20:12 ` Romain Diss
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 8:41 problem " Henning Hraban Ramm
2011-09-19 10:35 ` Hans Hagen
2011-09-19 12:13 ` Henning Hraban Ramm
2011-09-19 20:02 ` Wolfgang Schuster
2011-09-19 21:34 ` Henning Hraban Ramm
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=E154BBAD-5995-4BA9-ABC5-76F426C4D4CB@googlemail.com \
--to=schuster.wolfgang@googlemail.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).