ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: sometxt in mkiv
Date: Mon, 08 Sep 2008 11:26:26 +0200	[thread overview]
Message-ID: <48C4EFC2.9050509@wxs.nl> (raw)
In-Reply-To: <412BE50D-3652-4602-A678-BE1D873B3813@uni-bonn.de>

Thomas A. Schmitz wrote:

> thanks for your responses. I was aware that you can use textext  
> (that's what I do right now), but was under the impression that  
> sometxt was the way to go (faster and more flexible). Now I'm  
> confused :-)  I was asking because I was working on my presentation  

both mkiv and sometxt use some box trickery which keeps the tex 
processing completely inside the tex engine (only refs and dimensions 
are passed); in order to deal with loopt, we introduced the TeXtext 
trick but it' sno longer needed

there is still \sometxt but it's just a shortcut to a predefined 
commando (e.g. framed) which can be handy sometimes

> module. One of the metapost graphics for picture inclusion seems to  
> give problems when run under XeTeX, so I was wondering if I could  
> replace it with the clever sometxt mechanism Mojca mentions in her  
> MyWay. But then I saw that this doesn't work in mkiv... I find XeTeX  
> very hard to support in my module. I don't use it myself, I find fonts  

then just don't support it and assume mkiv usage

> deeply baffling (I still got the darned "mktextfm lmtypewriter- 
> blablabla" message a zillion times, and there is no way to stop a  
> XeTeX run; I still had to explicitly disable MKTEXTFM in texmf.cnf in  
> TeXLive 2008), so I'm considering just giving it up and tell people to  
> use mkiv instead.

indeed; this is a side effect of xetex being opentype and mp only able 
to deal with 8 bit fonts; in mkiv mp never sees any text (not een the 
btex .. etex which is replaced by by textext before the mp code is 
passed to mp); that's why in mkiv your text is a matter of the current 
run (inlcuding fotn settings and such, i.e. no need to pass anything to 
MPenvironment either)

concerning your module ... you can have a mymodule.mkiv alongside 
mymodule.tex if needed

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-09-08  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 11:15 Thomas A. Schmitz
2008-09-07 13:43 ` Aditya Mahajan
2008-09-07 19:42 ` Mojca Miklavec
2008-09-08  7:22   ` Thomas A. Schmitz
2008-09-08  9:26     ` Hans Hagen [this message]
2008-09-08 18:43       ` Thomas A. Schmitz
2008-09-09 15:07       ` Mojca Miklavec
2008-09-09 15:13     ` Mojca Miklavec
2008-09-09 17:23       ` Thomas A. Schmitz
2008-09-08  8:16   ` Hans Hagen
2008-09-07 15:52 Thomas A. Schmitz
2008-09-07 23:32 ` Aditya Mahajan

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=48C4EFC2.9050509@wxs.nl \
    --to=pragma@wxs.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).