ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problems with using PPCHTEX in LaTeX
Date: Thu, 20 Dec 2007 15:01:41 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.0.9999.0712201456090.26147@nqv-yncgbc> (raw)
In-Reply-To: <476AB54C.3020604@wxs.nl>

On Thu, 20 Dec 2007, Hans Hagen wrote:

> Aditya Mahajan wrote:
>> On Thu, 20 Dec 2007, Mojca Miklavec wrote:
>>
>>> On Dec 20, 2007 11:31 AM, Hans Hagen wrote:
>>>> Erik Stempel wrote:
>>>>> Dear Mr. Hagen,
>>>>>
>>>>> I have a problem with using PPCHTEX with LaTeX (MikTeX 2.6).
>>>>> After reporting this problem at GoogleGroups I get a message to report
>>>>> the problem directly to you.
>>>>>
>>>>> The problem is, that only the including of \usepackage{m-pictex,
>>>>> m-ch-de} makes six errors (pdflatex).
>>>>> The minimal example:
>>>>>
>>>>> \documentclass{scrartcl}
>>>>> \usepackage{m-ch-de}
>>>>> \begin{document}
>>>>> Test
>>>>> \end{document}
>>>> use the latest greatest context zips
>>> I do, but it does't help. I get exactly the same error:
>>
>> I am confused. Consider the following file:
>>
>> \unexpanded\def\test{Test}
>> \test
>> \bye
>>
>> Run it through ConTeXt, and it compiles fine. Run it through pdftex (plain
>> format) and it gives:
>
> \unexpanded is a primitive in etex, introduced when context already had
> an \unexpanded macro; the same is true for \protected
>
> \normalunexpanded gives you the primitive
>
> when loaded in latex, ppchtex should restore the meaning of \unexpanded
> after loading but i cannot test that here

There is a bug in ppchtex.noc. Line 39 says

\let\unexpanded\normalunexpanded

However, on line 181 you load ppchtex. ppchtex assumes that \unexpanded 
is the context macro, not the etex primitive. The easy work around is to 
move the \let\unexpanded\normalunexpanded line to the end of the 
ppchtex.noc. This works fine on my machine.

To the OP: locate ppchtex.noc by kpsewhich ppchtex.noc and copy that file 
to your current directory. Cut line 39 (\let\unexpanded\normalunexpanded) 
and paste it after line 213 (just before the last line). After this change 
the minimal example that you posted works correctly. See if your actual 
tex file now compiles.

Aditya
___________________________________________________________________________________
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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2007-12-20 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 14:06 Erik Stempel
2007-12-20 10:31 ` Hans Hagen
2007-12-20 17:41   ` Mojca Miklavec
2007-12-20 18:09     ` Aditya Mahajan
2007-12-20 18:32       ` Hans Hagen
2007-12-20 20:01         ` Aditya Mahajan [this message]
2007-12-20 21:33           ` 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=alpine.DEB.0.9999.0712201456090.26147@nqv-yncgbc \
    --to=adityam@umich.edu \
    --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).