From: Oliver Buerschaper <oliver.buerschaper@mpq.mpg.de>
To: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: textext vs. btex ... etex
Date: Tue, 24 Aug 2010 11:31:49 +0200 [thread overview]
Message-ID: <56A39236-DE19-46D2-84A2-CC2F71ADAF96@mpq.mpg.de> (raw)
In-Reply-To: <4C70EEA9.4030906@elvenkind.com>
>> Clearly, this gives me each glyph individually but stacked on top of
>> each other. What I need though is that the second figure looks
>> exactly like the first one (with all glyphs in the right location)
>> except that the grey bounding boxes appear per glyph.
>
> I know what you want now, but I have no idea how to go about doing
> it via this approach. It could be made to work from the other
> direction (by writing lua code to intercept tex nodes) but that is
> not trivial either.
I see.
> You could use standalone metapost with btex ... etex, that would work.
OK. But then I would lose e.g. OpenType fonts, right?
Oliver
___________________________________________________________________________________
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-24 9:31 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
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 [this message]
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=56A39236-DE19-46D2-84A2-CC2F71ADAF96@mpq.mpg.de \
--to=oliver.buerschaper@mpq.mpg.de \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).