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)?
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=Something] \startletter \input tufte \stopletter % end Is this a bug or is this something to be set by hand? In the latter case, what is the best way to do (I think \setuplettertext[\s!en][\v!enclosure={encl:~}] should work but one have then to modify the text for all the languages).
I’ll change the default values.
3. I respond to one of my previous post: the \getbuffer command works as argument of the enclosure key. But in the following minimal example case, this 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={\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