ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: r.ermers@hccnet.nl
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: letters in context mkiv
Date: Tue, 1 Aug 2017 14:04:05 +0200	[thread overview]
Message-ID: <19552875-2118-4FD1-A7E9-EE7B3AE95FD2@hccnet.nl> (raw)
In-Reply-To: <05E6DA9F-D6F9-48D3-B21A-BC9883FE815F@uni-bonn.de>

Thanks Wolfgang and Thomas,

The solutions of both of you function!

Thank you!

Robert


> Op 1 aug. 2017, om 13:17 heeft Schmitz Thomas A. <thomas.schmitz@uni-bonn.de> het volgende geschreven:
> 
> 
>> On 1. Aug 2017, at 12:15, r.ermers@hccnet.nl wrote:
>> 
>> While understanding what it means, I guess this might imply that it is difficult (?) or impossible (?) to correctly process files such as the knuth text and for that matter any other letter text that contains regular Context commands.
>> 
>> Nevertheless, for the moment this problem remains unsolved.
>> 
>> What would you advise as the next step?
>> 
>> Should the letter be somehow set-up outside xml setups rather than inside?
>> Should the letter texts (and a specific knuth sample text) be reformatted as xml?
> 
> So: you want to import the letter texts from an external file. Easiest solution: instead of simply \input knuth, try this:
> 
> {\pushcatcodetable
> \catcodetable\ctxcatcodes\input knuth
> \popcatcodetable}
> 
> As you can see, changing the catcode regime processes the file correctly. “Expansion” means something different in TeX speak.
> 
> Other possibilities: write your letter body in xml, or write the letters in buffers and use \processTEXbuffer.
> 
> Thomas
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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-08-01 12:04 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
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 [this message]
  -- 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=19552875-2118-4FD1-A7E9-EE7B3AE95FD2@hccnet.nl \
    --to=r.ermers@hccnet.nl \
    --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).