ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: new version luatex / mkiv
Date: Sat, 12 Apr 2008 09:53:57 +0200	[thread overview]
Message-ID: <48006A95.8020703@elvenkind.com> (raw)
In-Reply-To: <48006378.3060600@wxs.nl>

Hans Hagen wrote:
>> This manual is not viewable without deleting a html-frame.
>> Or what I am doing wrong?
> 
> i don't know, it's a pdf document, so no html frame is part of it

That is just a weirdness in viewcvs, too bad. Here is better link

   http://www.luatex.org/svn/tags/beta-0.25.2/manual/luatexref-t.pdf


>> The manual describes a lua interface. 

(next paragraphs written as the MPlib maintainer)

Real API documentation will be provided once I am past the "alpha"
release stage. At the moment, I do not trust the API enough to expose
it to anything except controlled environments (lua mplib, newmpost)

>> Isn't mplib a dll under windows?

It is possible to build the unix version as a .so because support for
that comes from autofoo automatically, but that is not yet officially
supported: debugging dynamic libraries is harder than debugging static
code.

MPlib could become a dll on windows eventually, but first someone will
have to explain to me how to create a windows dll (and I vastly prefer
a solution that does not involve me having to pay Microsoft any money).
I have exactly zero knowledge in that area and do not have a Windows
installation either: the one and only XP machine here is my wife's
gaming machine and that is strictly offlimits to me.

Future versions of luatex and mpost itself (and potential other texlive
programs) will almost certainly remain statically linked because that is
much more convenient for us as maintainers.

Best wishes,
Taco
___________________________________________________________________________________
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-04-12  7:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4785.1207920366.4340.ntg-context@ntg.nl>
2008-04-11 19:50 ` Wolfgang Werners-Lucchini
2008-04-12  7:23   ` Hans Hagen
2008-04-12  7:53     ` Taco Hoekwater [this message]
2008-04-12 15:09     ` Lou
2008-04-12 15:20       ` Mojca Miklavec
2008-04-13 12:00       ` Hans Hagen
     [not found] <mailman.1.1207994403.7394.ntg-context@ntg.nl>
2008-04-12 19:47 ` Wolfgang Werners-Lucchini
2008-04-13 12:06   ` Hans Hagen
     [not found] <mailman.1.1207908001.11489.ntg-context@ntg.nl>
2008-04-11 13:01 ` Wolfgang Werners-Lucchini
2008-04-11 12:58   ` Taco Hoekwater
2008-04-11 12:59   ` Hans Hagen
2008-04-10 15:18 Hans Hagen
2008-04-10 19:44 ` Peter Rolf
2008-04-10 21:17 ` Thomas A. Schmitz
2008-04-10 22:14   ` Hans Hagen
2008-04-11  3:27 ` luigi scarso
2008-04-11  7:32   ` Hans Hagen
2008-04-12  0:32     ` luigi scarso
2008-04-11  9:24 ` Maurice Diamantini
2008-04-11  9:46   ` Hans Hagen
2008-04-11  9:49   ` Yue Wang

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=48006A95.8020703@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).