ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: [Aleph] OpenType-to-TeX and other musings...
Date: Sun, 18 Dec 2005 21:07:39 +0100	[thread overview]
Message-ID: <43A5C18B.60704@wxs.nl> (raw)
In-Reply-To: <op.s1zmv5s1nx1yh1@walayah1.wildblue.com>

Idris Samawi Hamid wrote:

> On Sun, 18 Dec 2005 07:16:31 -0700, Hans Hagen <pragma@wxs.nl> wrote:
>
>>> In the short run, for Aleph's purposes, these declarations and   
>>> much/most/all of the metainfo can be treated as "suggestions" for 
>>> the  otp  designer to consider in implementing things. There is no 
>>> need to  treat  them as something "holy".
>>
>>
>> in the near future pdftex will provide open type as well as hooks 
>> for  input processing using lua, so you may as well end up rewriting 
>> your  otp's in a more friendly language
>
>
> At the risk of getting off topic: I know nothing about lua-) What 
> makes it  such a great tool? Why not just use, e.g., Ruby (less 
> languages for me to  learn->)?

well, there is google ...

lua is

- small, so no huge overhead and expanding library base
- clever enough for the job needed
- a well designed embedded language
- fun

>
> But you are quite right: the otp language is a real bear...

indeed, let'd get rid of it -)

Hans

  reply	other threads:[~2005-12-18 20:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 22:21 OpenType fonts Idris Samawi Hamid
2005-12-17  9:58 ` Taco Hoekwater
     [not found] ` <op.s1wituiynx1yh1@walayah1.wildblue.com>
     [not found]   ` <op.s1wjhmttnx1yh1@walayah1.wildblue.com>
     [not found]     ` <1134825201.43a40ef110463@diogel.enst-bretagne.fr>
2005-12-17 17:50       ` [Aleph] OpenType-to-TeX and other musings Idris Samawi Hamid
2005-12-18 14:16         ` Hans Hagen
2005-12-18 16:32           ` Idris Samawi Hamid
2005-12-18 20:07             ` Hans Hagen [this message]
2005-12-19 17:35           ` [OT] Was: " David Wooten
2005-12-19 19:58             ` Hans Hagen
2005-12-19 20:08               ` David Wooten

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=43A5C18B.60704@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).