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: TeX-MP interaction in mkii and mkiv
Date: Mon, 13 Oct 2008 09:45:24 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.00.0810130943520.28064@nqv-yncgbc> (raw)
In-Reply-To: <6faad9f00810130129y5f8b6e4al3d65843ec048abf1@mail.gmail.com>

On Mon, 13 Oct 2008, Mojca Miklavec wrote:

> On Fri, Oct 10, 2008 at 7:24 PM, Aditya Mahajan wrote:
>> On Fri, 10 Oct 2008, Hans Hagen wrote:
>>
>>> Aditya Mahajan wrote:
>>>> Hi,
>>>>
>>>> Another difference in mkii and mkiv handling of sometxt. If there is a
>>>> line break in \sometxt{ ... } then it fails in mkii, but runs in mkiv. For
>>>> example,
>>>>
>>>> \starttext
>>>>
>>>> \startMPcode
>>>>
>>>>    draw \sometxt{A very
>>>>                 long string} ;
>>>>
>>>> \stopMPcode
>>>>
>>>> \stoptext
>>>>
>>>> I vaguely understand why this is happening, but I do not know if it can be
>>>> corrected.
>>>
>>> in mkii we obey lines because it gives better tracing etc etc given that
>>> we use external files; this will work:
>>>
>>>
>>>    draw \sometxt{A very %
>>>                 long string} ;
>>>
>>
>> Ah, thanks.
>>
>>> indeed mkiv is different but let's consider it an improvement; i don't
>>> want to waste time on mkii fixes that are not that important
>>
>> I understand that. We need to document all these differences between mkii
>> and mkiv with regards to mp interaction for those who want to write code
>> that works in both. Mojca, any plans to update your MyWay?
>
> If you want to do changes, just go ahead (you might be more
> competitive to describe them).
>
> Otherwise: I'm not sure what all the differences are.
> 1.) withcolor doesn't work
> 2.) \startTeXtexsts cannot be used
> 3.) the example above fails in mkii

In MKIV certain commands inside \sometxt should be unexpandable. I do not 
really understand which ones, but I occasionally get errors which can be 
fixed by making the command unexpandable.

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:[~2008-10-13 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  4:53 Aditya Mahajan
2008-10-02 14:43 ` Aditya Mahajan
2008-10-02 15:03   ` Taco Hoekwater
2008-10-02 15:07     ` Taco Hoekwater
2008-10-02 15:37       ` Aditya Mahajan
2008-10-10 16:54 ` Aditya Mahajan
2008-10-10 17:05   ` Hans Hagen
2008-10-10 17:24     ` Aditya Mahajan
2008-10-13  8:29       ` Mojca Miklavec
2008-10-13 13:45         ` Aditya Mahajan [this message]

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.1.00.0810130943520.28064@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).