From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: textext vs. btex ... etex
Date: Tue, 17 Aug 2010 17:34:33 +0200 [thread overview]
Message-ID: <4C6AAC09.3080405@wxs.nl> (raw)
In-Reply-To: <21CE9841-242A-4F91-B2DF-FBB8722FB5C9@mpq.mpg.de>
On 17-8-2010 4:32, Oliver Buerschaper wrote:
> Hi,
>
> I've been trying to troubleshoot a problem with TeX labels I ran into the other day... finally I discovered that
>
> 1. MkIV (textext) includes TeX material as one single chunk apparently while MkII (btex ... etex) used to include a decomposable picture and that
> 2. the anchor point is completely different!
>
> Is there any way to restore both the "individual addressing" of glyphs and the MkII anchor point in MkIV?
>
> This would be crucial for a customized labelling macro...
>
> Best,
> Oliver
>
>
> P.S. Why is "h," included as one piece in MkII?
the fact that you have pieces in mkii is a side effect of dvitomp
turning dvi output in mp pictures; in the process it combines glyphs
that have no kerning and whatever spacing becomes shifts
in mkiv the text is treated as a whole and that will not change
so, if in mkiv you want pieces, you need to textext each snippet that
you want as such
keep in mind that the way mkii (read: external tex processing and
dvitomp) works is quite unpredictable
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-08-17 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 14:32 Oliver Buerschaper
2010-08-17 15:34 ` Hans Hagen [this message]
2010-08-18 12:20 ` Oliver Buerschaper
2010-08-18 13:02 ` Khaled Hosny
2010-08-18 14:00 ` Oliver Buerschaper
2010-08-18 14:34 ` Hans Hagen
2010-08-21 14:24 ` Oliver Buerschaper
2010-08-21 14:49 ` Taco Hoekwater
2010-08-22 7:53 ` Oliver Buerschaper
2010-08-22 9:32 ` Taco Hoekwater
2010-08-24 9:31 ` Oliver Buerschaper
2010-08-24 10:19 ` Taco Hoekwater
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=4C6AAC09.3080405@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).