ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Offset MP text with font change
Date: Sun, 28 Apr 2013 22:24:23 +0200	[thread overview]
Message-ID: <517D8577.50909@wxs.nl> (raw)
In-Reply-To: <20130428200347.GG3895@homerow>

On 4/28/2013 10:03 PM, Marco Patzer wrote:

> This is usually not a problem, since typescripts are loaded in the
> setup area. Even when loaded within the text area the spaces don't
> cause problems. Loading an entire file within a box, like I did in
> the example, is an unusual edge-case and there's a simple
> workaround, see Wolfgangs answer.

normally it only matters in hmode

when you \usetypescriptfile[iwona] outside the macro the definitions get 
preloaded in memory ; in fact, each typescript eventually gets cached

typescripts are loaded under a newline restricted regime but that 
doesn't always prevent spaces creeping in (like those before comments)

\definetextext
   [foo]
   [#1]#2{\switchtobodyfont[#1]\removeunwantedspaces#2}

and moving all to lua is no option now (although ... in 
antykwapoltawskiego.lfg one can see how such a thing can be done)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2013-04-28 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 17:56 Marco Patzer
2013-04-28 18:04 ` Wolfgang Schuster
2013-04-28 18:37   ` Marco Patzer
2013-04-28 18:40     ` Wolfgang Schuster
2013-04-28 18:40   ` Keith J. Schultz
2013-04-28 20:03     ` Marco Patzer
2013-04-28 20:24       ` Hans Hagen [this message]
2013-04-28 22:42       ` Keith J. Schultz
2013-04-28 23:00         ` 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=517D8577.50909@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).