ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: Metafun::followtokens : more than one path; possible enhancements; notes
Date: Mon, 29 Jan 2001 13:51:31 +0100	[thread overview]
Message-ID: <3.0.6.32.20010129135131.00792da0@server-1> (raw)
In-Reply-To: <000201c08974$3bf382c0$a3ccfea9@nuovo>

At 10:02 PM 1/28/01 +0100, Giuseppe Bilotta wrote:

>A future enhancements could be a \longfollowtokens that automatically
splits a
>(single) token list into as much paths as necessary (the user should
>preventively define enough paths), more like a parshape (actually, the
splitting
>could be done by parshaping the text using the lengths of the paths as
>parshape...). But this is definitely too much for me, at least at the current
>stage of knowledge of both TeX and ConTeXt.
>
>Final note: I suspect that some fine tuning on these macro group could render
>TeX--XeT useless. I mean, you can reflect a whole paragraph: first typeset it
>to get the linebreaks, then apply \followtokens to each line ... you don't
even
>need a reflected font! Actually, any kind of rotatation/skewing/etc, normally
>achieved with PSTricks, could be achieved this way, in a
driver-independent way

The current method would break on complicated tex code, since we (using
some tricks) work on token lists. Imagine languages where 4 chars become
one lig. 

However, i do have a slightly other alternatuve running here, but need to
finish it with regards to spacing. That one works ike : 

followtokens("some complicated string", path, offset); 

Technically it comes down to feeding the string into a btex/etex and
disassembling the resulting picture. Faster, less mem, more beautiful, but
less instructive -)

Concerning multiple path's, it should not be that hard to support auto
splitting. 

In your patch, i wonder why you don't use two followtokens, since you can
overlay pictures and by setting the boundingbox explicitly you can then
achieve the same results. I will look into your code later [maybe next
month, when i start revisioning the metafun manual]. 

Hans  

-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  reply	other threads:[~2001-01-29 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28 21:02 Giuseppe Bilotta
2001-01-29 12:51 ` Hans Hagen [this message]
2001-01-29 16:26 ` Giuseppe Bilotta

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=3.0.6.32.20010129135131.00792da0@server-1 \
    --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).