From: Romain Diss <romain.diss@yahoo.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with letter module
Date: Fri, 20 Jan 2012 22:44:45 +0100 [thread overview]
Message-ID: <201201202244.45697.romain.diss@yahoo.fr> (raw)
In-Reply-To: <2F73EC30-0BCC-489E-BC96-CBDCFAA8D3D2@googlemail.com>
Le vendredi 20 janvier 2012, Wolfgang Schuster a écrit :
> Am 20.01.2012 um 00:20 schrieb Romain Diss:
> > Le vendredi 20 janvier 2012, Wolfgang Schuster a écrit :
> >> Am 19.01.2012 um 23:57 schrieb Romain Diss:
> >>>> Do you use TeXLive or the ConTeXt Suite (minimals)?
> >>>
> >>> I use the latest beta of the ConTeXt Suite (minimals):
> >>> (...)
> >> Can show your log file, you should see something like this:
> >> (...)
> > Here is what the log looks like:
> > (...)
> The right files are loaded, i was curious because you wrote this earlier:
>
> 1. When I run context on a context letter input (like the previous minimal
> example), the log let me suppose that the \usemodule[letter] command loads
> the t-letter.mkii instead of the t-letter.mkiv. Is this the case and why.
> Moreover, t-letter.mkiv goal seems to only print an error message, even if
> my context version is more recent than the one recommended.
>
> t-letter.mkii or t-letter.mkiv aren’t loaded with the context suite, both
> files are only used with texlive 2011 but a recent context doesn’t use
> them.
Excuse me. I think I misunderstood the way the module was loaded.
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]?
All the best
--
Romain Diss
<romain.diss@yahoo.fr>
___________________________________________________________________________________
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-20 21:44 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 [this message]
2012-01-21 0:16 ` Hans Hagen
2012-01-21 9:12 ` Wolfgang Schuster
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=201201202244.45697.romain.diss@yahoo.fr \
--to=romain.diss@yahoo.fr \
--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).