...

Would it be possible to install (optionally perhaps) third party modules like t-letter and t-simplefonts also? Yeah, that should be doable. The Apple installer definitely supports packages with several (optional) components. ... I'll put it on the roadmap.

Great. Many thanks for that!

Well, you can. If you want these modules to be available to all local users of your Mac place the entire directory hierarchy of each module in the tree /usr/local/context/2009-06-11-beta/texmf- local. You'll need admin access though since /usr/local/context is a protected system directory.

I knew I need an installer. :-( I have downloaded the archive "t-simplefonts-2009.08.01.zip" from <http://modules.contextgarden.net/simplefonts

and placed this zip file in the place "/usr/local/context/ 2009-06-11-beta/texmf-local" and switched to the terminal:

---Terminal Output--- titus:~ jh$ su admin Password: ******** bash-3.2$ cd /usr/local/context/2009-06-11-beta/texmf-local bash-3.2$ ls t-simplefonts-2009.08.01.zip bash-3.2$ sudo unzip t-simplefonts-2009.08.01.zip Password: ******** Archive: t-simplefonts-2009.08.01.zip creating: tex/ creating: tex/context/ creating: tex/context/third/ creating: tex/context/third/simplefonts/ ... bash-3.2$ ls doc t-simplefonts-2009.08.01.zip source tex bash-3.2$ sudo luatools --generate LuaTools | fileio: variable SELFAUTOLOC set to /usr/local/context/ 2009-06-11-beta/texmf-osx-intel/bin LuaTools | fileio: variable SELFAUTODIR set to /usr/local/context/ 2009-06-11-beta/texmf-osx-intel LuaTools | fileio: variable SELFAUTOPARENT set to /usr/local/context/ 2009-06-11-beta LuaTools | fileio: variable TEXMFCNF set to {$SELFAUTODIR, $SELFAUTOPARENT}{,{/share,}/texmf{-local,.local,}/web2c} LuaTools | fileio: loading configuration file /usr/local/context/ 2009-06-11-beta/texmf/web2c/texmfcnf.lua ..... Then I tried a simple test file after using "luatool --generate" on my non-admin account: titus:wech jh$ luatool --generate titus:wech jh$ context myriad.tex ... ... /2009-06-11-beta/texmf-context/tex/context/base/type-otf.mkiv))) system : myriad.top loaded (myriad.top) fonts : preloading latin modern fonts bodyfont : 12pt rm is loaded language : language en is active system : module simplefonts loaded (/usr/local/context/2009-06-11-beta/texmf-local/tex/context/third/ simplefonts/t-simplefonts.tex loading : ConTeXt User Module / Simplefonts ! Undefined control sequence. l.707 \startprocesscommacommand [\simplefonts!weight] ? ---Terminal Output--- Well, it seems that your instructions did basically work, since the module simplefonts is loaded. But nevertheless the simple test file aborts and complains about " Undefined control sequence. l.707 \startprocesscommacommand[\simplefonts!weight]". Do you have an idea what went wrong on my side? The content of the file "myriad.tex" is just: \mainlanguage[de] \setuplayout[middle] % \definefontfeature[default][default][ % mode=node, % protrusion=quality, % expansion=quality, % onum=yes,pnum=yes] \usemodule[simplefonts] %[size=10pt] \setmainfont[Myriad Pro] % \setupbodyfont[ss,10pt] % % \setupinterlinespace[line=2.6ex] % % \definefont[big][Serif at .25\vsize] \starttext Nun denn. \stoptext The Myriad font is installed, see Screenshot "Schriftsammlung.pdf". Definitely a dump error on my side, but could you please give me a hint on how to proceed? It seems that I am really dependent on your installer... Many thanks again for your help and patience Best regards Joerg Hecke

Am 19.08.2009 um 10:43 schrieb Oliver Buerschaper:

...

Well, it seems that your instructions did basically work, since the module simplefonts is loaded. But nevertheless the simple test file aborts and complains about " Undefined control sequence. l.707 \startprocesscommacommand[\simplefonts!weight]".

Do you have an idea what went wrong on my side?

Yes. Although the module is found it crashes during initialization. Observe that

--- \usemodule[simplefonts]

\starttext

This tests whether the module \type{t-simplefonts} is loaded successfully.

\stoptext ---

already hangs. The reason is that the latest version of the t- simplefonts module (which is the one you obtained) makes use of ConTeXt kernel commands (\startprocesscommacommand) which seem to have only been introduced lately. In other words, the version I packaged into the experimental installer is too old for the current module. So not your fault.

You're right and the command was added *for* the simplefonts module :)

Keep in mind though that this might happen frequently without warning since you're working with development code here. For the moment I'm merely trying to establish something along the lines of a nightly installer build ... since there's no regression test suite I can't even test whether anything works but the most basic features. Also, modules don't check for a minimum kernel version required :-(

There is a command to check the context version %D \macros %D {doifolderversionelse} %D %D We start with a macro specially for Aditya who wants to be able %D to use development versions of \MKIV\ for real documents. %D %D \starttyping %D \doifolderversionelse\contextversion{2001.02.03}{yes}{no} %D \doifolderversionelse\contextversion{3001.02.03}{yes}{no} %D \stoptyping and end the module and output a message in the terminal but then you will you will get a error message in the document itself because a few commands (e.g. \setmainfont) are no longer defined. Wolfgang

Am 20.08.2009 um 10:23 schrieb Oliver Buerschaper:

Would it then be possible to have ConTeXt grind to a complete halt once it encounters a module whose minimum requirements aren't met?

\doifolderversionelse\contextversion{2100.01.01}\normalend\donothing %\doifolderversionelse\contextversion{2009.07.01}\normalend\donothing \starttext Hello \stoptext

Since TeX would have to give up on the document anyway perhaps an early bail out could be the more graceful option ... what do you think?

I can add this test to my module together with a message at the terminal. Wolfgang

Oliver Buerschaper wrote:

...

...

Would it then be possible to have ConTeXt grind to a complete halt once it encounters a module whose minimum requirements aren't met?

\doifolderversionelse\contextversion{2100.01.01}\normalend\donothing %\doifolderversionelse\contextversion{2009.07.01}\normalend\donothing

\starttext Hello \stoptext

That's great! It's almost what I was looking for ... yet I think \normalend might not be drastic enough ;-) Namely, running this example with

I'll add: \unprotect \def\forcequitjob#1% {\writestatus\m!systems{forcing quit: #1}% \batchmode \dorecurse\textlevel\stoptext \normalend} \protect \starttext test \forcequitjob{whatever} \stoptext ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Sun, 23 Aug 2009, Wolfgang Schuster wrote:

Am 22.08.2009 um 13:47 schrieb Oliver Buerschaper:

...

What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-)

*You* want to write a test suite for ConTeXt?

The test suite is there. There is even a script in the test suit that compares the outputs of two versions at pixel level. All we need is people to submit tests and then someone to monitor the test suite. See http://wiki.contextgarden.net/Test

...

Perhaps one could even integrate this requirement check into the module loading code of the kernel. For example, one might enforce that each valid module has to declare a field like "minkernelversion" in its header ... just thinking out loud.

The problem with such systems is they lead always to incompatibilities with ConTeXt installations (think about TeXLive) and we had one at the end of last year when Hans changed the multilingual interface to allow a persian interface.

Loading of lua files has this feature. For modules, asking for a minimum kernel version is no guarantee that the module will work with future versions of ConTeXT :-) Aditya

On Sun, 23 Aug 2009, Wolfgang Schuster wrote:

Am 23.08.2009 um 17:22 schrieb Aditya Mahajan:

...

...

*You* want to write a test suite for ConTeXt?

The test suite is there. There is even a script in the test suit that compares the outputs of two versions at pixel level. All we need is people to submit tests and then someone to monitor the test suite. See http://wiki.contextgarden.net/Test

Is this still alive and used?

It is alive (as in, you can submit test cases) but it is not used. I think that Hans and Taco have made it clear that someone else need to volunteer for running the test suite. Sanjoy had some ideas, but then he became busy with other things. I still think that it is a good idea for people to submit examples to the test suite. Maybe having enough tests will be an incentive for someone to write a regression suite. Aditya

...

What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-)

*You* want to write a test suite for ConTeXt?

Well, not exactly ... this might be too ambitious an endeavour for one person alone ;-) I'm trying though to store a bunch of test cases locally which I sporadically collect from the main mailing test whenever a bug report shows up. If only to have something I can test my installation package against ... For the moment I'm mainly interested in whether these test cases compile at all hence my remark about the exit status ... (After all, if that can't be automated any further verification steps will be pretty much useless I guess.)

...

Perhaps one could even integrate this requirement check into the module loading code of the kernel. For example, one might enforce that each valid module has to declare a field like "minkernelversion" in its header ... just thinking out loud.

The problem with such systems is they lead always to incompatibilities with older ConTeXt installations (think about TeXLive) and we had one at the end of last year when Hans changed the multilingual interface to allow a persian interface.

I agree that my suggestion would sacrifice backwards compatibility. At the same time I'm not sure how much change to the MkIV kernel is desirable given that MkII is considered frozen. I'm really in no position to have an educated opinion on whether there should be as few changes as possible or rather the occasional clear cut. It's just that if you guys think that some clear cuts are due for MkIV anyway then there will probably be never a better time than now to make module loading more bullet-proof. As I was saying, I'm just thinking out loud ;-) Oliver

On Sun, 23 Aug 2009, Wolfgang Schuster wrote:

Am 23.08.2009 um 17:52 schrieb Oliver Buerschaper:

...

I agree that my suggestion would sacrifice backwards compatibility. At the same time I'm not sure how much change to the MkIV kernel is desirable given that MkII is considered frozen. I'm really in no position to have an educated opinion on whether there should be as few changes as possible or rather the occasional clear cut. It's just that if you guys think that some clear cuts are due for MkIV anyway then there will probably be never a better time than now to make module loading more bullet-proof. As I was saying, I'm just thinking out loud ;-)

MkIV is ConTeXt’s feature without an doubt but it's not so easy as you think.

I have myself two modules which work only with MkIV (simplefonts and games) but bigger ones like simpleslides or letter are just complexer styles and you can't expect from a user to upgrade to MkIV just to make a presentation or to write a short letter.

I thought about integrating the version check into \setupmodule because the command is only used in modules and available in MkII and MkIV but Thomas and Aditya use it in the simpleslides module to pass parameters to the module and this a few times at different places and not only at the start of the file.

If you have a suggestion that will make things cleaner, we (Thomas and I) can easily change the internals of simple slides to accomodate that. Aditya

On Sun, 23 Aug 2009, Wolfgang Schuster wrote:

Am 23.08.2009 um 22:06 schrieb Aditya Mahajan:

...

On Sun, 23 Aug 2009, Wolfgang Schuster wrote:

...

I thought about integrating the version check into \setupmodule because the command is only used in modules and available in MkII and MkIV but Thomas and Aditya use it in the simpleslides module to pass parameters to the module and this a few times at different places and not only at the start of the file.

If you have a suggestion that will make things cleaner, we (Thomas and I) can easily change the internals of simple slides to accomodate that.

In your module you can either use \getparameters or – what I think you want in your module – \setvariables because it's not very different to \setupmodule.

I thought that \setupmodule was meant for passing parameters to modules, mainly because of the following comment in core-fil % \usemodule[newmml] % \usemodule[newmml][a=b] % \usemodule[x][newmml] % \usemodule[x][newmml][a=b] % % \startmodule [mathml] % \setupmodule[a=c] \relax [\currentmoduleparameter{a}] % user vars will be set afterwards % \setupmodule[a=c] \relax [\currentmoduleparameter{a}] % user vars are now forgotten % \stopmodule As, \setupmodule is just \getparameters with a few defaults in place, I can also use \getparamters with \currentmoduleparamters.

To stop the TeX run we can have

\setupmodule[contextversion=2009.08.22]

at the begin of a module and ConTeXt will abort the run if the key 'contextversion' has a value and context is older than the user has requested.

Do you want this to check to be part of the definition of \setupmodule? One difficultly that I see is that typically this will mean that we need to set this separately for each engine. Aditya

On Mon, 24 Aug 2009, Wolfgang Schuster wrote:

Am 24.08.2009 um 00:17 schrieb Aditya Mahajan:

...

...

In your module you can either use \getparameters or – what I think you want in your module – \setvariables because it's not very different to \setupmodule.

I thought that \setupmodule was meant for passing parameters to modules, mainly because of the following comment in core-fil

Is this passing parameters to the module, I don't think so!

\def\dosetupTitle[#1]% {\setupmodule[simpleslides:title][#1]}

Oh those. I had forgotten about them :) I will change these to \getvariables.

...

As, \setupmodule is just \getparameters with a few defaults in place, I can also use \getparamters with \currentmoduleparamters.

You use \currentmoduleparameter only in t-simpleslides to load a style file but \moduleparameter is used many other files to setvariables etc. and the last one is more like \getvariables (which use rawparameters)

I agree.

...

...

To stop the TeX run we can have

\setupmodule[contextversion=2009.08.22]

at the begin of a module and ConTeXt will abort the run if the key 'contextversion' has a value and context is older than the user has requested.

Do you want this to check to be part of the definition of \setupmodule? One difficultly that I see is that typically this will mean that we need to set this separately for each engine.

I don't need such a check, it was Olivers idea and I thought about a idea how this can be integrated without introducing a new command which breaks backward compatibility.

I meant that when you said \setupmodule[contextversion=...]", what is the implementation you had in mind. \setupmodule macro doing the checking, or the module writer doing the checking. Aditya

Wolfgang Schuster wrote:

Am 24.08.2009 um 16:27 schrieb Aditya Mahajan:

...

...

...

...

To stop the TeX run we can have \setupmodule[contextversion=2009.08.22] at the begin of a module and ConTeXt will abort the run if the key 'contextversion' has a value and context is older than the user has requested. Do you want this to check to be part of the definition of \setupmodule? One difficultly that I see is that typically this will mean that we need to set this separately for each engine.

I don't need such a check, it was Olivers idea and I thought about a idea how this can be integrated without introducing a new command which breaks backward compatibility.

I meant that when you said \setupmodule[contextversion=...]", what is the implementation you had in mind. \setupmodule macro doing the checking, or the module writer doing the checking.

I think it's up to the developer to write something in the module, e.g. http://bitbucket.org/wolfs/simplefonts/src/46a1f454bccc/files/t-simplefonts....

but it's not so hard to integrate it into the \setupmodule command.

% untested, it should only show how \setupmodule can be extended to stop a tex run % when a module is used with a too old context version

\def\c!contextversion{contextversion}

\def\doabortmodule#1#2#3%

{\doif{#2}\c!contextversion{\doifolderversionelse\contextversion{#3}{\forcequitjob{#1}}\donothing}}

\def\dosetupmodule[#1][#2]% {\scratchtoks\expandafter{\currentmoduleparameters}% \ifsecondargument \getparameters[\??md:#1:][#2]% \expanded{\getparameters[\??md:#1:][\the\scratchtoks]}%

no need for toks \expanded{\getparameters[\??md:#1:]\expandafter}\expandafter[\currentmoduleparameters]% but maybe a \hetparameterscommand makes more sense -)

\processassignmentlist[#2]{\doabortmodule{#1}}% \else \getparameters[\??md:\currentmodule:][#1]% \expanded{\getparameters[\??md:\currentmodule:][\the\scratchtoks]}% \processassignmentlist[#1]{\doabortmodule\currentmodule}% \fi \let\currentmoduleparameters\empty}

but anyway, i wonder if we should go that route; normally context is downward compatible and eventually mkiv will become more stable ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Mon, 24 Aug 2009, Wolfgang Schuster wrote:

Am 24.08.2009 um 16:27 schrieb Aditya Mahajan:

...

...

...

...

To stop the TeX run we can have \setupmodule[contextversion=2009.08.22] at the begin of a module and ConTeXt will abort the run if the key 'contextversion' has a value and context is older than the user has requested. Do you want this to check to be part of the definition of \setupmodule? One difficultly that I see is that typically this will mean that we need to set this separately for each engine.

I don't need such a check, it was Olivers idea and I thought about a idea how this can be integrated without introducing a new command which breaks backward compatibility.

I meant that when you said \setupmodule[contextversion=...]", what is the implementation you had in mind. \setupmodule macro doing the checking, or the module writer doing the checking.

I think it's up to the developer to write something in the module, e.g. http://bitbucket.org/wolfs/simplefonts/src/46a1f454bccc/files/t-simplefonts.... but it's not so hard to integrate it into the \setupmodule command.

Thanks for clarifying. I also think that it is better to do this selectively for each module rather than in the core. Aditya

Hi,

... The reason is that the latest version of the t-simplefonts module (which is the one you obtained) makes use of ConTeXt kernel commands (\startprocesscommacommand) which seem to have only been introduced lately. In other words, the version I packaged into the experimental installer is too old for the current module. So not your fault.

Ok. So the point is that I should search for an older version of the t- simplefonts module which does not yet request this new and specific kernel command, right? (Or just skip the idea of trying to use Myriad Pro I assume)

Keep in mind though that this might happen frequently without warning since you're working with development code here. For the moment I'm merely trying to establish something along the lines of a nightly installer build ... since there's no regression test suite I can't even test whether anything works but the most basic features. Also, modules don't check for a minimum kernel version required :-(

Hmm, yep. Quite a fair warning. OK. I was so naïve, that it would be a breeze to add some modules simply by myself. My problem is really to detect whether it was my stupidity (in 99% the case) or if something else went wrong. I do read the ntg-context list and many remarks ("This is broken in MKIV", "Ah I see, just use this patch...") are quite kind of scary to me, since I would be completely lost applying such patches, snippets of code, etc. But overall, all the information and the help of the context lists is really extremly informative and helpful and I am learning lots of new things daily. But using fonts is beyond my horizon at the moment, unfortunately. Therefor I was keen on trying the simplefonts module. I will definitely look forward to your next version of the installer. many thanks again for all and regards Jörg

Wow. I have used the attached version and it worked right out of the box with the Context Minimals version installed by the installer of Oliver and his instructions.

You can try the following version http://bitbucket.org/wolfs/simplefonts/src/0a2adbda3117/files/t-simplefonts.... (or use the attached version, was on the garden afair) but i won't provide support in the case there is a problem with them.

Yes, I understand that. Many thanks for your help! The simple test file runs just fine right now.

There is a package with typescripts (including Myriad Pro) on the garden you can use.

Thanks for that tip. You mean here: <http://wiki.contextgarden.net/TypeScripts

? Can't find that package there. Seems to be a little bit tricky to find. I'll keep on searching.

Many thanks for your help so far! Regards Jörg

Am 21.08.2009 um 17:56 schrieb Wolfgang Schuster:

The zip is here http://modules.contextgarden.net/typescripts and the dev version can be found at http://bitbucket.org/wolfs/typescripts/ but as i don't need them myself other users are needed to add more typescripts.

Ahh many thanks for the links. I have not looked at the modules site. I'll download it right away and will try to get it work in the standard TeXlive Context (MKII) distribution. Thanks and a nice WE! Jörg

Hi Wolfgang, I am trying to use your t-letter module. Thanks to your letter documentation and the examples (letter-examples.zip) from your web side I was able to set up the letter. But I am failing to use the resume part:-( I would like to use your classic or casual layout, but I have no idea how to use them. An excerpt from your file "correspondence-resume-examples.tex": %---begin resume.tex--- \usemodule[resume] \useresumestyle [classic] \setresumevalue{image} {\blackrule[width=25mm,height=25mm]} \setresumevalue{firstname} {John} \setresumevalue{familyname}{Doe} \setresumevalue{title} {Resum\'e title (optional)} \setresumevalue{quote} {Some quote (optional)} \setresumevalue{street} {street and number} \setresumevalue{town} {postcode city} \setresumevalue{mobile} {mobile (optional)} \setresumevalue{phone} {phone (optional)} \setresumevalue{fax} {fax (optional)} \setresumevalue{email} {email (optional)} \setresumevalue{info} {additional information (optional)} \startresume \section{Education} \cventry{year--year}{Degree}{Institution}{City}{\it Grade}{Description} \cventry{year--year}{Degree}{Institution}{City}{\it Grade}{Description} \section{Master thesis} \cvline{title}{\em Title} \cvline{supervisors}{Supervisors} \cvline{description}{\tx Short thesis abstract} \stopresume %---end resume.tex--- does not compile at all, which tells me that I do not have a clue how to setup a proper tex frame and how to use it. My environment: Context-Mnimals on MacOS 10.6.2 (Snow Leopard) ConTeXt ver: 2010.01.26 18:39 MKIV fmt: 2010.1.27 int: english/english on Is it possible to get me on the right track to use your module? I must be doing something really stupid, but currently I have no idea what I have to do to get your resume module running. Do you have a minimal example perhaps? Many thanks for your help in advance. Best regards Jörg Hecke The terminal output is:

[22:47][~/Desktop/Lebenslauf] ➔ context jhresume.tex MTXrun | run 1: luatex --fmt="/Users/jh/context_minimals/2010-01-27/tex/texmf-cache/luatex-cache/context/b1c97208f21e2e812306e4f74f4bfba4/formats/cont-en" --lua="/Users/jh/context_minimals/2010-01-27/tex/texmf-cache/luatex-cache/context/b1c97208f21e2e812306e4f74f4bfba4/formats/cont-en.lui" --backend=pdf "./jhresume.tex" This is LuaTeX, Version beta-0.50.0-2009122423 \write18 enabled. (jhresume.tex

ConTeXt ver: 2010.01.26 18:39 MKIV fmt: 2010.1.27 int: english/english

system : cont-new loaded (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/cont-new.tex systems : beware: some patches loaded from cont-new.tex (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/cont-new.mkiv)) system : cont-fil loaded (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/cont-fil.tex loading : ConTeXt File Synonyms ) system : cont-sys.rme loaded (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/user/cont-sys.rme (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-def.mkiv) (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-lua.tex) (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-tmf.tex (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-tmf.mkiv)) (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-siz.tex (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-siz.mkiv)) (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-otf.tex (/Users/jh/context_minimals/2010-01-27/tex/texmf-context/tex/context/base/type-otf.mkiv))) system : jhresume.top loaded (jhresume.top) fonts : preloading latin modern fonts bodyfont : 12pt rm is loaded language : language en is active (m-resume.tex) system : module resume not found ! Undefined control sequence. <recently read> \useresumestyle

l.2 \useresumestyle [classic] ?

Hi Wolfgang, Am 14.02.2010 um 23:22 schrieb Wolfgang Schuster:

...

But I am failing to use the resume part:-( I would like to use your classic or casual layout, but I have no idea how to use them.

I'm sorry but there is something missing in documentation, the resume part is not really written and the two styles are just included from a older module of me and you have to load them with

\usemodule[resume] % load the module \useresumeinterface[moderncv] % load the moderncv-interface \useresumestyle[classic|casual] % load a style

you can also do this with one command

\usemodule[resume][interface=moderncv,style=casual] You have a module with the m-resume.tex on your system which is loaded instead of my module, you can now either remove this from the current directory or force ConTeXT to load my module with '\usemodule[t][resume][...]' in your document.

Many thanks for your prompt and brilliant help! Your examples do work right away! Will try to use one of your examples. Thanks again. Jörg

Am 17.02.10 22:57, schrieb Jörg Hecke:

Hi Wolfgang,

sorry for bothering you again. I am using your letter module, but it seems that I am not able to use a 2 column itemize environment?

No idea what’s the problem but as a workaround you can use this: \startsimplecolumns[n=2] \startitemize \item ... \stopitemize \stopsimplecolumns

\startletter [subject=Verteiben der Position \quotation{nicht hier {\bf B11r} }, opening=Sehr geehrter Herr nicht Hier\textcomma, closing=Mit freundlichen Grüßen\crlf\crlf\crlf Jörg Hecke]

\setupletterstyle[closing][inbetween={\blank[3*line]}] \startletter [subject={Vertreiben der Position \quotation{nicht hier {\bf B11r}}}, opening={Sehr geehrter Herr nicht Hier,}, closing={Mit freundlichen Grüßen}, signature={Jörg Hecke}] Wolfgang

Am 17.02.10 22:57, schrieb Jörg Hecke:

Hi Wolfgang,

I am using your letter module, but it seems that I am not able to use a 2 column itemize environment?

Fixed. Wolfgang