ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: Maurice Diamantini <Maurice.Diamantini@ensta.fr>
Subject: Re: ruby, Lua, Megapost, tcl, ...
Date: Mon, 19 Sep 2005 10:16:59 +0200	[thread overview]
Message-ID: <432E73FB.4020102@elvenkind.com> (raw)
In-Reply-To: <76C1E896-CA94-4908-85D4-ACAF693F941D@ensta.fr>


Hi Maurice,

Maurice Diamantini wrote:
> 
> What about Lua, Adding one more dependency to ConTeXt make it
> more difficult to install and maintain.
> So what is the advantage of luo in conTeXt instead of ruby?

Lua will not be 'in context', but 'in pdftex': the lua library
will be integrated in the executable, as a true extension language
that can be used besides and interleaved with TeX's normal syntax.

Lua is probably the best language for this sort thing, because
its code is small and very easy to extend/embed.

On the user side of things, nothing will change compared to the
current 'update  your pdftex release' stuff. Using LuaTeX will
eventually probably mean extra functionality, but the most likely
sort-term result is a gain in processing speed, because the in-line
scripting can reduce the number of needed TeX runs.

Greetings,

Taco

      parent reply	other threads:[~2005-09-19  8:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 18:12 ruby Hans Hagen
2005-05-11 19:29 ` ruby Nikolai Weibull
2005-05-11 21:54   ` ruby Hans Hagen
2005-05-11 22:10     ` ruby Nikolai Weibull
2005-05-12  6:02 ` ruby luigi.scarso
2005-05-12  7:01   ` ruby Hans Hagen
2005-05-12  9:48     ` Fill pdf forms luigi.scarso
2005-09-19  6:25     ` ruby, Lua, Megapost, tcl, Maurice Diamantini
2005-09-19  7:53       ` Hans Hagen
2005-09-19  8:11       ` Hans Hagen
2005-09-19  8:22         ` luigi.scarso
2005-09-19  8:16       ` Taco Hoekwater [this message]

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=432E73FB.4020102@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=Maurice.Diamantini@ensta.fr \
    --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).