ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: \type ,\meaning eror check
Date: Fri, 29 Jul 2005 11:28:34 +0200	[thread overview]
Message-ID: <42E9F6C2.1050201@elvenkind.com> (raw)
In-Reply-To: <42E9F324.1030702@logosrl.it>



luigi.scarso wrote:
> Taco Hoekwater wrote:
> 
>>
>>
>> AFAIK, there is only one way to do this: write a new tex file on-
>> the-fly and run a separate texexec on that file (using \write18),
>> then parse the resulting log file for the occurence of any errors.
>> Not simple at all, I'm afraid.
>>
> hmm, i've hundred of \startArticle..

I'll consider the possibility of adding a new primitive to pdfetex
(the language) for the discovery of run-time errors like this. That
will not help you at this moment, though.

>>>   2. \type does not combine well with \meaning: ò (ie {\`o} ) is not 
>>> show.
>>
>>
>>   \expanded\type{\expandafter\scantokens\expandafter{\Temp}}%
>>
> good , but type also first \expandafter after \type

Sorry, the correct solution is:

  \expandafter\expandafter\expandafter\type
  \expandafter\expandafter\expandafter
    {\expandafter\scantokens\expandafter{\Temp}}%

or, a bit shorter but needing \(un)protect:

  \@EA\@EA\@EA\type\@EA\@EA\@EA{\@EA\scantokens\@EA{\Temp}}%

My original post only \expanded the single token \type, not the whole
argument.

Cheers, Taco

  reply	other threads:[~2005-07-29  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 16:28 new minimals Hans Hagen
2005-07-28  9:51 ` Taco Hoekwater
2005-07-29  3:52 ` Stuart Jansen
2005-07-29  6:37   ` Hans Hagen
2005-07-29  7:06   ` \type ,\meaning eror check luigi.scarso
2005-07-29  8:32     ` Taco Hoekwater
2005-07-29  9:13       ` luigi.scarso
2005-07-29  9:28         ` Taco Hoekwater [this message]
2005-07-29  9:42           ` luigi.scarso
2005-07-31 21:11     ` Hans Hagen

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=42E9F6C2.1050201@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).