ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: UTF-8 characters and gnuplot module
Date: Mon, 24 Mar 2008 23:02:14 +0100	[thread overview]
Message-ID: <47E824E6.9020907@wxs.nl> (raw)
In-Reply-To: <6faad9f00803241314m467aeec8hc590f2c0f8ef86b1@mail.gmail.com>

Mojca Miklavec wrote:

> That's also right. Actually, "btex label etex" which calls TeX (in an
> extremely inefficient way, among other things) is the one that doesn't
> know how to handle them. It would be nice if someone from this mailing
> list had at least some idea if that is solvable or not.

don't bother too much about these issues ... in mkiv things will be 
different

i'm currently playing with mplib; the default converter works ok; the 
specials handler is reimplemented and mostly finished; and now i'm 
playing with the textual part ... i even got this working ...

\startMPgraphic
     fill fullcircle scaled 10cm withcolor green ;
     n := 50 ;
     for i=1 upto n :
         draw btex goodbye world etex
		scaled 2
		rotatedaround(origin,i*360/n) ;
     endfor ;
\stopMPgraphic

so, btex/etex works ok in a loop; everything happpens in luatex/mplib

it's even acceptable fast ...

100 times the previous graphic (i.e. 5000 btex/etex's) takes .7 seconds 
on my machine


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


  reply	other threads:[~2008-03-24 22:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 14:38 Morgan Brassel
2008-03-24 15:53 ` Mojca Miklavec
2008-03-24 16:03   ` Mojca Miklavec
2008-03-24 16:35   ` Morgan Brassel
2008-03-24 17:21     ` Mojca Miklavec
2008-03-24 18:52   ` Ethan Merritt
2008-03-24 20:14     ` Mojca Miklavec
2008-03-24 22:02       ` Hans Hagen [this message]
2008-03-24 22:21         ` Mojca Miklavec
2008-03-24 22:43           ` Hans Hagen
2008-03-25 14:28             ` Morgan Brassel
2008-03-25 14:55               ` Mojca Miklavec
2008-03-25 15:57                 ` Morgan Brassel
2008-03-25 17:11                   ` Mojca Miklavec
2008-03-25 20:24                     ` Henning Hraban Ramm
2008-03-26  8:05                 ` Taco Hoekwater
2008-03-26  9:28                   ` Mojca Miklavec
2008-03-24 19:24 ` Mojca Miklavec

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=47E824E6.9020907@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).