From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/3907 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Metafun::followtokens : more than one path; possible enhancements; notes Date: Mon, 29 Jan 2001 13:51:31 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <3.0.6.32.20010129135131.00792da0@server-1> References: <000201c08974$3bf382c0$a3ccfea9@nuovo> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: main.gmane.org 1035394613 21193 80.91.224.250 (23 Oct 2002 17:36:53 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:36:53 +0000 (UTC) Cc: "ConTeXt" Original-To: "Giuseppe Bilotta" In-Reply-To: <000201c08974$3bf382c0$a3ccfea9@nuovo> Xref: main.gmane.org gmane.comp.tex.context:3907 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:3907 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 -------------------------------------------------------------------------