ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: letters in context mkiv
Date: Mon, 31 Jul 2017 17:23:01 +0200	[thread overview]
Message-ID: <36b8c2fb-48cd-d3c6-684f-8a57487921a3@gmx.es> (raw)
In-Reply-To: <62E89064-51ED-4C7C-8D3D-B875D04D17A0@hccnet.nl>

On 07/31/2017 12:48 PM, r.ermers@hccnet.nl wrote:
> Dear Contex’ers,
> 
> This morning I have been experimenting with the solutions suggested by
> Thomas and Wolfgang.
> 
> Thomas’ solution works, it produces two distinct letters, yet the
> address is probably on another layer. This means that it is not shifted
> to the right, at least not with the command
> (\setupletterlayer[address]), so that it will be visible through the
> envelope window.
> 
> With Wolfgang’s solution the address is moved to its desired place, and
> the letter text is printed as well.
> 
> However, inserting a text (by means of \input) is problematic (see pdf),
> with or without \relax.

Hi Robert,

it isn’t the use of \input. The problem is that you only get one level
of expansion.

If you add \input directly to letter:section:content, such as in:

    \startsetups[letter:section:content]
    \input knuth \relax
    \stopsetups

You will have \input expanded. But in the text itself \TeX\ and
large||scale won’t be expanded.

I have no idea why this happens. And I don’t know how to fix it. Maybe
Wolfgang knows what is happening here.

If I had to guess, it might be that \directsetups only allows a level of
expansion. But I may be plainly wrong.

A way to avoid the issue is to add the letter content directly to the
\startsetups[letter:section:context]. And rememmber that you have only
one level of expansion.

Just in case it might help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-07-31 15:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 12:15 r.ermers
2017-07-30 15:38 ` Schmitz Thomas A.
2017-07-31  8:09   ` r.ermers
     [not found] ` <597DFB2C.60001@gmail.com>
2017-07-31 10:48   ` r.ermers
2017-07-31 15:23     ` Pablo Rodriguez [this message]
2017-07-31 16:58       ` r.ermers
2017-07-31 17:23         ` Pablo Rodriguez
2017-07-31 21:57         ` Schmitz Thomas A.
2017-08-01  7:55           ` r.ermers
2017-08-01  8:46             ` Schmitz Thomas A.
2017-08-01 10:15               ` r.ermers
2017-08-01 11:17                 ` Schmitz Thomas A.
2017-08-01 12:04                   ` r.ermers
  -- strict thread matches above, loose matches on Subject: below --
2017-07-28  6:18 r.ermers
2017-07-28  6:18 r.ermers
2017-07-25 11:14 r.ermers

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=36b8c2fb-48cd-d3c6-684f-8a57487921a3@gmx.es \
    --to=oinos@gmx.es \
    --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).