From romain.diss@yahoo.fr Wed Jan 18 21:14:29 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: [NTG-context] Problem with letter module
Date: Wed, 18 Jan 2012 21:14:14 +0100
Message-ID: <201201182114.15080.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1504654002275888850=="

--===============1504654002275888850==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I am writing a letter with the 'letter' module (mkiv and last beta) and the=20
\encl{} command doesn't work anymore. I know that the module has been rewrite=
n=20
recently but I can't find any doc or examples of the new syntax. I tried to=20
look at the source code but it doesn't help.

So is there any command which replace \encl{}? And is there any documentation=
=20
(even succint) of the new module?

Thanks.

--=20
Romain Diss
<romain.diss(a)yahoo.fr>

--===============1504654002275888850==--


From schuster.wolfgang@googlemail.com Thu Jan 19 00:21:35 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 00:21:29 +0100
Message-ID: <FC6BE627-C4E1-4D30-BC01-7058C5B77A92@googlemail.com>
In-Reply-To: <201201182114.15080.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0923741785481747149=="

--===============0923741785481747149==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 18.01.2012 um 21:14 schrieb Romain Diss:

> Hi,
>=20
> I am writing a letter with the 'letter' module (mkiv and last beta) and the=
=20
> \encl{} command doesn't work anymore. I know that the module has been rewri=
ten=20
> recently but I can't find any doc or examples of the new syntax. I tried to=
=20
> look at the source code but it doesn't help.
>=20
> So is there any command which replace \encl{}? And is there any documentati=
on=20
> (even succint) of the new module?

With the new version of the module I tried to get rid of a few things which l=
ead
to problems or which didn=E2=80=99t fit into context normal syntax. The \encl=
, \cc and \ps
had been such a thing and all three value can now only bet set as keyval argu=
ment,
e.g. \startletter[enclosure=3D=E2=80=A6]

There isn=E2=80=99t a new documentation yet but I=E2=80=99ll give a short ove=
rview.

There is now only one way to set values for the letter variables in this is \=
setupletter
with it=E2=80=99s keyval syntax, e.g. \setupletter[name=3D=E2=80=A6,address=
=3D=E2=80=A6]. The \setlettervalue
command from the previous version is gone and won=E2=80=99t come back.

The letter environment has now only optional argument which acts like a local
version of \setupletter where the values are only used in the environment.
When you use your document only for a single letter without anything else
you can even drop \starttext and \stoptext because this is handled by \startl=
etter
and \stopletter.

To change the labels in the reference line for the =E2=80=9CDate=E2=80=9D str=
ing you have
to use the \setuplettertext command, a special version of \setuplabeltext only
for the letter module.

Styles are still loaded with \useletterstyle but when you want to put your own
settings in a style file you have to name the file =E2=80=9Cletter-<style>.te=
x|mkiv=E2=80=9D. To load
the style you need only the <style> part as argument for the command because
the =E2=80=9Cletter-=E2=80=9D part is always added. It doesn't matter if you =
use tex or mkiv as file
extension because the file is found in either case.

Wolfgang

--===============0923741785481747149==--


From romain.diss@yahoo.fr Thu Jan 19 15:28:19 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 15:28:06 +0100
Message-ID: <201201191528.06942.romain.diss@yahoo.fr>
In-Reply-To: <FC6BE627-C4E1-4D30-BC01-7058C5B77A92@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3410657239916146654=="

--===============3410657239916146654==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Le jeudi 19 janvier 2012, vous avez =C3=A9crit :
> Am 18.01.2012 um 21:14 schrieb Romain Diss:
> > Hi,
> > (...)
> > So is there any command which replace \encl{}? And is there any
> > documentation (even succint) of the new module?
>=20
> With the new version of the module I tried to get rid of a few things which
> lead to problems or which didn=E2=80=99t fit into context normal syntax. The
> \encl, \cc and \ps had been such a thing and all three value can now only
> bet set as keyval argument, e.g. \startletter[enclosure=3D=E2=80=A6]
>=20
> There isn=E2=80=99t a new documentation yet but I=E2=80=99ll give a short o=
verview:
> (...)

Thank you for all these clarifications.
Unfortunatly, I have now another problem which I didn't notice before because=
=20
the \encl{} error didn't let me go to the end of the tex processing. The=20
following minimal example do not compile:

% example
\usemodule[letter]
\startletter
  \input tufte
\stopletter
% end

Instead, I get the following error message:

! Missing number, treated as zero.

system          > tex > error on line 100 in file letter.tex: Missing number,=
=20
treated as zero ...


<to be read again>=20
                   \relax=20
\pack_layers_set_content ..._pack_layers_x \relax=20
                                                  \d_pack_layers_y_position=20
...
\pack_layers_set_finish ...layers_set_content {#1}
                                                  \fi \fi \else \writestatus.=
..
\correspondence_layer_place ...dence_layer_direct=20
                                                  \fi \else \ifodd \c_corres.=
..
\executedefinedoverlay ...dp \the \everyoverlay #2
                                                  \else \lower=20
\d_framed_tar...
\pack_framed_process_background_indeed_external ...
                                                  \else \kern=20
-\framedbackgr...
...
l.7 \stopletter


Any idea which could help me?

Thanks in advance.

All the best.

--=20
Romain Diss
<romain.diss(a)yahoo.fr>

--===============3410657239916146654==--


From romain.diss@yahoo.fr Thu Jan 19 15:28:52 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 15:28:31 +0100
Message-ID: <201201191528.32076.romain.diss@yahoo.fr>
In-Reply-To: <FC6BE627-C4E1-4D30-BC01-7058C5B77A92@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2833847598224677450=="

--===============2833847598224677450==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Le jeudi 19 janvier 2012, vous avez écrit :
> Am 18.01.2012 um 21:14 schrieb Romain Diss:
> > Hi,
> > (...)
> > So is there any command which replace \encl{}? And is there any
> > documentation (even succint) of the new module?
> 
> With the new version of the module I tried to get rid of a few things which
> lead to problems or which didn’t fit into context normal syntax. The
> \encl, \cc and \ps had been such a thing and all three value can now only
> bet set as keyval argument, e.g. \startletter[enclosure=…]

I forgot another question: does the 'enclosure' key accept a \getbuffer 
command? I tried and it seems that it doesn't work but I am not sure because 
my input doesn't compile completely.

Thanks

--
Romain Diss
<romain.diss(a)yahoo.fr>

--===============2833847598224677450==--


From schuster.wolfgang@googlemail.com Thu Jan 19 20:52:35 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 20:52:10 +0100
Message-ID: <2B9F266F-36BD-4FFC-897C-5E1D01DA9EA0@googlemail.com>
In-Reply-To: <201201191528.06942.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6606292028699175136=="

--===============6606292028699175136==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 19.01.2012 um 15:28 schrieb Romain Diss:

> Le jeudi 19 janvier 2012, vous avez =C3=A9crit :
>> Am 18.01.2012 um 21:14 schrieb Romain Diss:
>>> Hi,
>>> (...)
>>> So is there any command which replace \encl{}? And is there any
>>> documentation (even succint) of the new module?
>>=20
>> With the new version of the module I tried to get rid of a few things which
>> lead to problems or which didn=E2=80=99t fit into context normal syntax. T=
he
>> \encl, \cc and \ps had been such a thing and all three value can now only
>> bet set as keyval argument, e.g. \startletter[enclosure=3D=E2=80=A6]
>>=20
>> There isn=E2=80=99t a new documentation yet but I=E2=80=99ll give a short =
overview:
>> (...)
>=20
> Thank you for all these clarifications.
> Unfortunatly, I have now another problem which I didn't notice before becau=
se=20
> the \encl{} error didn't let me go to the end of the tex processing. The=20
> following minimal example do not compile:

It=E2=80=99s a bug a fixed a while ago but I hadn=E2=80=99t uploaded the new =
version yet.

I put the now the current version online and it should be in the context
suite in a few hours.

Wolfgang

--===============6606292028699175136==--


From romain.diss@yahoo.fr Thu Jan 19 23:07:02 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 23:06:45 +0100
Message-ID: <201201192306.46029.romain.diss@yahoo.fr>
In-Reply-To: <2B9F266F-36BD-4FFC-897C-5E1D01DA9EA0@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6333484970564004927=="

--===============6333484970564004927==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Le jeudi 19 janvier 2012, Wolfgang Schuster a =C3=A9crit :
> Am 19.01.2012 um 15:28 schrieb Romain Diss:
> > Le jeudi 19 janvier 2012, vous avez =C3=A9crit :
> >> Am 18.01.2012 um 21:14 schrieb Romain Diss:
> >>> Hi,
> >>> (...)
> >>> So is there any command which replace \encl{}? And is there any
> >>> documentation (even succint) of the new module?
> >>=20
> >> With the new version of the module I tried to get rid of a few things
> >> which lead to problems or which didn=E2=80=99t fit into context normal s=
yntax.
> >> The \encl, \cc and \ps had been such a thing and all three value can
> >> now only bet set as keyval argument, e.g. \startletter[enclosure=3D=E2=
=80=A6]
> >>=20
> >> There isn=E2=80=99t a new documentation yet but I=E2=80=99ll give a shor=
t overview:
> >> (...)
> >=20
> > Unfortunatly, I have now another problem which I didn't notice before
> > because the \encl{} error didn't let me go to the end of the tex
> > processing. (...)
> >
> It=E2=80=99s a bug a fixed a while ago but I hadn=E2=80=99t uploaded the ne=
w version yet.
Thank you for the new version. It now works...

However, this leads me to new questions...

1. When I run context on a context letter input (like the previous minimal=20
example), the log let me suppose that the \usemodule[letter] command loads th=
e=20
t-letter.mkii instead of the t-letter.mkiv. Is this the case and why.=20
Moreover, t-letter.mkiv goal seems to only print an error message, even if my=
=20
context version is more recent than the one recommended.

2. The enclosure formatting is not good: there is no space between the encl. =

label and the text. Here is a minimal exemple:
% start
\usemodule[letter]
\setupletter
 [enclosure=3DSomething]
\startletter
  \input tufte
\stopletter
% end
Is this a bug or is this something to be set by hand? In the latter case, wha=
t=20
is the best way to do (I think \setuplettertext[\s!en][\v!enclosure=3D{encl:~=
}]=20
should work but one have then to modify the text for all the languages).

3. I respond to one of my previous post: the \getbuffer command works as=20
argument of the enclosure key. But in the following minimal example case, thi=
s=20
leads to strange sapcing. Any idea of what causes this?
%start
\usemodule[letter]
\startbuffer[enclosure]
  \startitemize
    \startitem something; \stopitem
    \startitem and something else. \stopitem
  \stopitemize
\stopbuffer

\setupletter
 [enclosure=3D{\getbuffer[enclosure]}]
\startletter
  \input tufte
\stopletter
% end

Thanks in advance.

--=20
Romain Diss
<romain.diss(a)yahoo.fr>

--===============6333484970564004927==--


From schuster.wolfgang@googlemail.com Thu Jan 19 23:08:18 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 23:08:05 +0100
Message-ID: <BC501CBF-0B3E-48B6-86F2-093C2D4079A9@googlemail.com>
In-Reply-To: <201201191528.32076.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1827134977893015699=="

--===============1827134977893015699==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 19.01.2012 um 15:28 schrieb Romain Diss:

> I forgot another question: does the 'enclosure' key accept a \getbuffer=20
> command? I tried and it seems that it doesn't work but I am not sure becaus=
e=20
> my input doesn't compile completely.

It tested it and it does work but why do you need a buffer?

When it is to format the list as itemize or something similar I can add a mec=
hanism
to make this in a form like =E2=80=9Cenclosure=3D{list:one,two,three}=E2=80=
=9D which is better than a buffer.

Wolfgang

--===============1827134977893015699==--


From schuster.wolfgang@googlemail.com Thu Jan 19 23:24:27 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 23:24:14 +0100
Message-ID: <F07DF822-3B4D-49BD-91B0-0883BDCECE1A@googlemail.com>
In-Reply-To: <201201192306.46029.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3003637497846200757=="

--===============3003637497846200757==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 19.01.2012 um 23:06 schrieb Romain Diss:

> However, this leads me to new questions...
>=20
> 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=20
> t-letter.mkii instead of the t-letter.mkiv. Is this the case and why.=20
> Moreover, t-letter.mkiv goal seems to only print an error message, even if =
my=20
> context version is more recent than the one recommended.

Do you use TeXLive or the ConTeXt Suite (minimals)?

> 2. The enclosure formatting is not good: there is no space between the encl=
.=20
> label and the text. Here is a minimal exemple:
> % start
> \usemodule[letter]
> \setupletter
> [enclosure=3DSomething]
> \startletter
>  \input tufte
> \stopletter
> % end
> Is this a bug or is this something to be set by hand? In the latter case, w=
hat=20
> is the best way to do (I think \setuplettertext[\s!en][\v!enclosure=3D{encl=
:~}]=20
> should work but one have then to modify the text for all the languages).

I=E2=80=99ll change the default values.

> 3. I respond to one of my previous post: the \getbuffer command works as=20
> argument of the enclosure key. But in the following minimal example case, t=
his=20
> leads to strange sapcing. Any idea of what causes this?
> %start
> \usemodule[letter]
> \startbuffer[enclosure]
>  \startitemize
>    \startitem something; \stopitem
>    \startitem and something else. \stopitem
>  \stopitemize
> \stopbuffer
>=20
> \setupletter
> [enclosure=3D{\getbuffer[enclosure]}]
> \startletter
>  \input tufte
> \stopletter
> % end

Something low level, could be caused by the buffer but I have to check myself
with a simple example without the letter module.

Wolfgang

--===============3003637497846200757==--


From romain.diss@yahoo.fr Thu Jan 19 23:58:05 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Thu, 19 Jan 2012 23:57:50 +0100
Message-ID: <201201192357.50555.romain.diss@yahoo.fr>
In-Reply-To: <F07DF822-3B4D-49BD-91B0-0883BDCECE1A@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1859666639359155799=="

--===============1859666639359155799==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Thank you for the (always) quick response.


Le jeudi 19 janvier 2012, Wolfgang Schuster a écrit :
> Am 19.01.2012 um 23:06 schrieb Romain Diss:
> > However, this leads me to new questions...
> > 
> > 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.
> 
> Do you use TeXLive or the ConTeXt Suite (minimals)?
I use the latest beta of the ConTeXt Suite (minimals):
- context 2012.01.16 18:33
- luatex beta-0.70.1-2011051918 (rev 4277)

-- 
Romain Diss
<romain.diss(a)yahoo.fr>

--===============1859666639359155799==--


From schuster.wolfgang@googlemail.com Fri Jan 20 00:05:53 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Fri, 20 Jan 2012 00:05:46 +0100
Message-ID: <07C648F9-2C05-4921-834D-A95ECC0469FA@googlemail.com>
In-Reply-To: <201201192357.50555.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5583250709820380551=="

--===============5583250709820380551==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


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):
> - context 2012.01.16 18:33
> - luatex beta-0.70.1-2011051918 (rev 4277)


Can show your log file, you should see something like this:

resolvers       > modules > loaded: 'letter'
interface       > macros > processed file 's-cor-01.mkvi', delta 24
(s-cor-01.mkvi
resolvers       > modules > loaded: 'cor-00'
interface       > macros > processed file 's-cor-00.mkvi', delta 1195
(s-cor-00.mkvi<+ s-cor-00.lua>) (letter-imp-default.mkiv) (letter-imp-dinb.mk=
iv (letter-imp-default.mkiv))){/Users/wolf/context/beta/tex/texmf-context/fon=
ts/map/pdftex/context/mkiv-base.map}

Wolfgang

--===============5583250709820380551==--


From romain.diss@yahoo.fr Fri Jan 20 00:23:59 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Fri, 20 Jan 2012 00:20:39 +0100
Message-ID: <201201200020.39309.romain.diss@yahoo.fr>
In-Reply-To: <07C648F9-2C05-4921-834D-A95ECC0469FA@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5692153675962154596=="

--===============5692153675962154596==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

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):
> > - context 2012.01.16 18:33
> > - luatex beta-0.70.1-2011051918 (rev 4277)
> 
> Can show your log file, you should see something like this:
> 
> resolvers       > modules > loaded: 'letter'
> interface       > macros > processed file 's-cor-01.mkvi', delta 24
> (s-cor-01.mkvi
> resolvers       > modules > loaded: 'cor-00'
> interface       > macros > processed file 's-cor-00.mkvi', delta 1195
> (s-cor-00.mkvi<+ s-cor-00.lua>) (letter-imp-default.mkiv)
> (letter-imp-dinb.mkiv
> (letter-imp-default.mkiv))){/Users/wolf/context/beta/tex/texmf-context/fon
> ts/map/pdftex/context/mkiv-base.map}

Here is what the log looks like:

resolvers       > modules > loaded: 'letter'
(/home/roms/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-
cor-01.mkvi
resolvers       > modules > loaded: 'cor-00'
(/home/roms/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-
cor-00.mkvi<+ /home/roms/opt/context/tex/texmf-
modules/tex/context/third/letter/base/s-cor-00.lua>) 
(/home/roms/opt/context/tex/texmf-
modules/tex/context/third/letter/style/letter-imp-default.mkiv) 
(/home/roms/opt/context/tex/texmf-
modules/tex/context/third/letter/style/letter-imp-dinb.mkiv 
(/home/roms/opt/context/tex/texmf-
modules/tex/context/third/letter/style/letter-imp-default.mkiv)))
{/home/roms/opt/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-
base.map}

and later in the log:

mkiv lua stats  > loaded tex modules        - 2 requested, 2 found (*-cor-00 
*-cor-01), 0 missing


-- 
Romain Diss
<romain.diss(a)yahoo.fr>

--===============5692153675962154596==--


From schuster.wolfgang@googlemail.com Fri Jan 20 00:59:51 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Fri, 20 Jan 2012 00:59:44 +0100
Message-ID: <2F73EC30-0BCC-489E-BC96-CBDCFAA8D3D2@googlemail.com>
In-Reply-To: <201201200020.39309.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2118859836188489497=="

--===============2118859836188489497==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 20.01.2012 um 00:20 schrieb Romain Diss:

> Le vendredi 20 janvier 2012, Wolfgang Schuster a =C3=A9crit :
>> Am 19.01.2012 um 23:57 schrieb Romain Diss:
>>>> Do you use TeXLive or the ConTeXt Suite (minimals)?
>>>=20
>>> I use the latest beta of the ConTeXt Suite (minimals):
>>> - context 2012.01.16 18:33
>>> - luatex beta-0.70.1-2011051918 (rev 4277)
>>=20
>> Can show your log file, you should see something like this:
>>=20
>> resolvers       > modules > loaded: 'letter'
>> interface       > macros > processed file 's-cor-01.mkvi', delta 24
>> (s-cor-01.mkvi
>> resolvers       > modules > loaded: 'cor-00'
>> interface       > macros > processed file 's-cor-00.mkvi', delta 1195
>> (s-cor-00.mkvi<+ s-cor-00.lua>) (letter-imp-default.mkiv)
>> (letter-imp-dinb.mkiv
>> (letter-imp-default.mkiv))){/Users/wolf/context/beta/tex/texmf-context/fon
>> ts/map/pdftex/context/mkiv-base.map}
>=20
> Here is what the log looks like:
>=20
> resolvers       > modules > loaded: 'letter'
> (/home/roms/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-
> cor-01.mkvi
> resolvers       > modules > loaded: 'cor-00'
> (/home/roms/opt/context/tex/texmf-modules/tex/context/third/letter/base/s-
> cor-00.mkvi<+ /home/roms/opt/context/tex/texmf-
> modules/tex/context/third/letter/base/s-cor-00.lua>)=20
> (/home/roms/opt/context/tex/texmf-
> modules/tex/context/third/letter/style/letter-imp-default.mkiv)=20
> (/home/roms/opt/context/tex/texmf-
> modules/tex/context/third/letter/style/letter-imp-dinb.mkiv=20
> (/home/roms/opt/context/tex/texmf-
> modules/tex/context/third/letter/style/letter-imp-default.mkiv)))
> {/home/roms/opt/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-
> base.map}
>=20
> and later in the log:
>=20
> mkiv lua stats  > loaded tex modules        - 2 requested, 2 found (*-cor-0=
0=20
> *-cor-01), 0 missing

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=20
example), the log let me suppose that the \usemodule[letter] command loads th=
e=20
t-letter.mkii instead of the t-letter.mkiv. Is this the case and why.=20
Moreover, t-letter.mkiv goal seems to only print an error message, even if my=
=20
context version is more recent than the one recommended.

t-letter.mkii or t-letter.mkiv aren=E2=80=99t loaded with the context suite, =
both files
are only used with texlive 2011 but a recent context doesn=E2=80=99t use them.

Wolfgang

--===============2118859836188489497==--


From romain.diss@yahoo.fr Fri Jan 20 22:44:58 2012
From: Romain Diss <romain.diss@yahoo.fr>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Fri, 20 Jan 2012 22:44:45 +0100
Message-ID: <201201202244.45697.romain.diss@yahoo.fr>
In-Reply-To: <2F73EC30-0BCC-489E-BC96-CBDCFAA8D3D2@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5852009277969534491=="

--===============5852009277969534491==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Le vendredi 20 janvier 2012, Wolfgang Schuster a =C3=A9crit :
> Am 20.01.2012 um 00:20 schrieb Romain Diss:
> > Le vendredi 20 janvier 2012, Wolfgang Schuster a =C3=A9crit :
> >> Am 19.01.2012 um 23:57 schrieb Romain Diss:
> >>>> Do you use TeXLive or the ConTeXt Suite (minimals)?
> >>>=20
> >>> 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:
>=20
> 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.
>=20
> t-letter.mkii or t-letter.mkiv aren=E2=80=99t loaded with the context suite=
, both
> files are only used with texlive 2011 but a recent context doesn=E2=80=99t =
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 conte=
xt=20
know that it have to load the s-cor-* files when I type \usemodule[letter]?

All the best

--=20
Romain Diss
<romain.diss(a)yahoo.fr>

--===============5852009277969534491==--


From pragma@wxs.nl Sat Jan 21 01:17:16 2012
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Sat, 21 Jan 2012 01:16:28 +0100
Message-ID: <4F1A03DC.90602@wxs.nl>
In-Reply-To: <201201202244.45697.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5490499056455930810=="

--===============5490499056455930810==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On 20-1-2012 22:44, Romain Diss wrote:

> Just by curiosity, if none of the t-letter.* files are loaded, how does con=
text
> know that it have to load the s-cor-* files when I type \usemodule[letter]?

cont-fil.mkiv

(one of the oldest features around)

Hans


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

--===============5490499056455930810==--


From schuster.wolfgang@googlemail.com Sat Jan 21 10:12:28 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Sat, 21 Jan 2012 10:12:11 +0100
Message-ID: <E154BBAD-5995-4BA9-ABC5-76F426C4D4CB@googlemail.com>
In-Reply-To: <201201202244.45697.romain.diss@yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4827063286613901425=="

--===============4827063286613901425==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 20.01.2012 um 22:44 schrieb Romain Diss:

> Just by curiosity, if none of the t-letter.* files are loaded, how does con=
text=20
> 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 =E2=80=9Cfuzzy=E2=80=9D or =E2=80=9Cshade=E2=80=9D. The m=
apping 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

--===============4827063286613901425==--


From hraban@fiee.net Mon Feb  6 00:05:47 2012
From: Henning Hraban Ramm <hraban@fiee.net>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Mon, 06 Feb 2012 00:05:42 +0100
Message-ID: <9D5A94D1-B97A-45F3-98AC-A1FC37FAA602@fiee.net>
In-Reply-To: <FC6BE627-C4E1-4D30-BC01-7058C5B77A92@googlemail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2043282017328195110=="

--===============2043282017328195110==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Am 2012-01-19 um 00:21 schrieb Wolfgang Schuster:

> There isn’t a new documentation yet but I’ll give a short overview.
...

Since my letter/invoice setup doesn’t work anymore (and perhaps you  
remember it was a tricky one) - can we expect some docs anytime soon?

E.g. \copyletterelement is gone, and I guess my "\startsetups  
letter:location" and \defineletterelement doesn’t do anything, or any  
of the other setup commands, at least my logo and sender data don’t  
show up...


Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)


--===============2043282017328195110==--


From schuster.wolfgang@googlemail.com Mon Feb  6 12:41:16 2012
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Problem with letter module
Date: Mon, 06 Feb 2012 12:40:53 +0100
Message-ID: <229FB39E-E4D1-4EDC-8E43-4E4D212DAB7E@googlemail.com>
In-Reply-To: <9D5A94D1-B97A-45F3-98AC-A1FC37FAA602@fiee.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6901093691974935456=="

--===============6901093691974935456==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Am 06.02.2012 um 00:05 schrieb Henning Hraban Ramm:

> Am 2012-01-19 um 00:21 schrieb Wolfgang Schuster:
>=20
>> There isn=E2=80=99t a new documentation yet but I=E2=80=99ll give a short =
overview.
> ...
>=20
> Since my letter/invoice setup doesn=E2=80=99t work anymore (and perhaps you=
 remember it was a tricky one) - can we expect some docs anytime soon?

I'll write one when I=E2=80=99m in the right mood.

For a few changes read the following I posted a while ago: http://www.ntg.nl/=
pipermail/ntg-context/2012/064695.html

> E.g. \copyletterelement is gone, and I guess my "\startsetups letter:locati=
on" and \defineletterelement doesn=E2=80=99t do anything, or any of the other=
 setup commands, at least my logo and sender data don=E2=80=99t show up=E2=80=
=A6

I made few changes in the recent version of the module which breaks backward =
compatibility with old styles.

1. External styles

The predefined styles are loaded from external files with the \useletterstyle=
 command, in the past these files had names in the form <style>.nls. The name=
 system has changed and personal styles have to follow the form =E2=80=9Clett=
er-<style>.tex=E2=80=9D, you could also use =E2=80=9Cmkiv=E2=80=9D and =E2=80=
=9Cmkii=E2=80=9D as extensions.

2. Setup commands

Previously there has been only the \setupletterstyle command to change the va=
lues of the elements, now the various types of elements have dedicated comman=
ds.

The =E2=80=9Clayers=E2=80=9D (which are used for the =E2=80=9Chead=E2=80=9D, =
=E2=80=9Caddress=E2=80=9D or =E2=80=9Creference line=E2=80=9D) are configured=
 with the \setupletterlayer and \setupletterframe command, the first is used =
to move the layer to it=E2=80=99s position on the page with the =E2=80=9Cx=E2=
=80=9D and =E2=80=9Cy=E2=80=9D keys and you can select one letter elements (w=
hich are created with \defineletterelement) with the =E2=80=9Calternative=E2=
=80=9D key. With the \setupletterframe you can change the =E2=80=9Cwidth=E2=
=80=9D and =E2=80=9Cheight=E2=80=9D of the element.

The =E2=80=9Csections=E2=80=9D (which are used for the =E2=80=9Csubject=E2=80=
=9D and =E2=80=9Ccontent=E2=80=9D) are configured with the \setuplettersectio=
n command which allows you to change the alignment and spacing before and aft=
er the element.

Global settings like the bodyfont, whitespace or language can be changed with=
 the \setuplettersoptions command.

The old \setupletterstyle command had been reduced to change the style and co=
lor for the variables which are set with \setupletter (or \startletter), e.g.=
 you can say \setupletter[date][textstyle=3Dbold,color=3Dred] to change the l=
ayout of the date in the reference line.

A complete list with all values for the various commands can be seen in the f=
ollowing document: https://bitbucket.org/wolfs/correspondence/downloads/comma=
nds.pdf

3. \defineletterelement

One limitation of the old module was that element names had been shared betwe=
en layers and section (i.e. it was impossible to have a layer and a section w=
ith the same name). This limitation was removed and it=E2=80=99s now possible=
 to layers and sections with the same name but ti handle this the \definelett=
erlement command needed a additional argument. The syntax for the command is =
now

   \defineletterelement[<type>][<element>][<name>]{<content>}

As a example I show a definition for the head with the name =E2=80=9Ctest=E2=
=80=9D which prints the value of the =E2=80=9Cfirstname=E2=80=9D key.

   \defineletterelement[layer][head][test]{\correspondenceparameter{firstname=
}}

The old \copyletterelement command is no longer available, when you miss a fe=
w default just send me a mail and I=E2=80=99ll add them.

4. \startsetups

The old version used \startsetups for the content of the elements. With the c=
urrent version all internals use now \letterelement but there is a method to =
feed them with the \startsetups argument, all you need is \setupletteroptions=
[option=3Dsetups] in your document. Nevertheless also the names for \startset=
ups have been changed to follow the unique named mentioned above and the old =
name =E2=80=9Cletter:location=E2=80=9D is now =E2=80=9Cletter:layer:location=
=E2=80=9D.

5. Layout

The layout of the letter environment can be changed with the \setupletterlayo=
ut command, it is possible to use a different layout for the first (firstpage=
) and the following (secondpage) pages but starting from the second page one =
can also set different value for left (leftpage) and right (rightpage) pages.

Wolfgang

--===============6901093691974935456==--