From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: problem with letter module
Date: Mon, 19 Sep 2011 12:35:59 +0200 [thread overview]
Message-ID: <4E771B0F.3030002@wxs.nl> (raw)
In-Reply-To: <8B261D6E-CCB4-47FC-B3F8-880FC5C3A9C5@fiee.net>
On 19-9-2011 10:41, Henning Hraban Ramm wrote:
> Hello Wolfgang,
>
> with the latest beta I get a problem with your letter module.
> If this error message is not enough, I can investigate further later today.
>
> This is LuaTeX, Version beta-0.70.1-2011051908 (rev 4277) \write18 enabled.
> ConTeXt ver: 2011.09.18 22:35 MKIV fmt: 2011.9.19 int: english/english
>
> ....
> resolvers > modules > loaded: 'letter'
> (/Users/hraban/Library/texmf/tex/texmf-modules/tex/context/third/letter/base/t-letter.tex
>
> loading > Context User Module / Framework for Letters
> resolvers > modules > loaded: 'correspondence'
> (/Users/hraban/Library/texmf/tex/texmf-modules/tex/context/third/letter/base/t-correspondence.mkiv
>
> loading > Context User Module / Correspondence
> )
> ! Undefined control sequence.
>
> system > tex > error on line 272 in file invoicesetup.tex: Undefined
> control sequence ...
>
>
> \dodododosetupcorrespondencelayer ...sname \@EAEA
interesting .. I removed that one (could not find any usage)
-----------------------------------------------------------------
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:[~2011-09-19 10:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 8:41 Henning Hraban Ramm
2011-09-19 10:35 ` Hans Hagen [this message]
2011-09-19 12:13 ` Henning Hraban Ramm
2011-09-19 20:02 ` Wolfgang Schuster
2011-09-19 21:34 ` Henning Hraban Ramm
2012-01-18 20:14 Problem " 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
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
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=4E771B0F.3030002@wxs.nl \
--to=pragma@wxs.nl \
--cc=hraban@fiee.net \
--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).