From: "Fengnan Gao" <fnsteed@hotmail.com>
To: <ntg-context@ntg.nl>
Subject: Re: Serious bug?
Date: Mon, 22 Dec 2008 09:53:40 +0800 [thread overview]
Message-ID: <COL106-DS103D8ED8BAD6416F4DDCEFA4EF0@phx.gbl> (raw)
In-Reply-To: <68bfdc900812210618g68bd4534vac8bdb6e0ef6ca03@mail.gmail.com>
>Definitely not.
>
>What version of LuaTeX is in Windows distribution? Maybe I forgot to
>update it. I'll check tomorrow (you can try to fetch the version from
>W32TeX).
>
>Mojca
C:\Users\fnsteed>luatex --credits
This is LuaTeX, Version snapshot-0.31.2-2008121200, build 1659
The LuaTeX team is Hans Hagen, Hartmut Henkel, Taco Hoekwater.
LuaTeX merges and builds upon (parts of) the code from these projects:
tex by Donald Knuth
etex by Peter Breitenlohner, Phil Taylor and friends
omega by John Plaice and Yannis Haralambous
aleph by Giuseppe Bilotta
pdftex by Han The Thanh and friends
kpathsea by Karl Berry, Olaf Weber and others
lua by Roberto Ierusalimschy, Waldemar Celes,
Luiz Henrique de Figueiredo
metapost by John Hobby, Taco Hoekwater and friends.
xpdf by Derek Noonberg (partial)
fontforge by George Williams (partial)
Some extensions to lua and additional lua libraries are used, as well as
libraries for graphic inclusion. More details can be found in the source.
Code development was sponsored by a grant from Colorado State University
via the 'oriental tex' project, the TeX User Groups, and donations.
Compiled with libpng 1.2.33; using libpng 1.2.33
Compiled with zlib 1.2.3; using zlib 1.2.3
Compiled with xpdf version 3.02pl2
Hope that'll help.
---------------
Cheers,
Fengnan Gao <fnsteed@hotmail.com>
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-12-22 1:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 12:58 Fengnan Gao
2008-12-21 14:18 ` Yue Wang
2008-12-21 14:28 ` Fengnan Gao
2008-12-22 1:53 ` Fengnan Gao [this message]
2008-12-22 7:26 ` Mojca Miklavec
2008-12-22 7:35 ` Mojca Miklavec
2008-12-21 14:26 ` Hans Hagen
2008-12-21 20:52 ` Mojca Miklavec
2008-12-22 9:58 ` Taco Hoekwater
-- strict thread matches above, loose matches on Subject: below --
2008-12-22 18:57 Tad Ashlock
2008-12-22 12:56 Fengnan Gao
2008-12-22 16:04 ` Mojca Miklavec
2008-12-23 18:22 ` Taco Hoekwater
2008-12-24 13:27 ` Alan STONE
2008-12-22 17:55 ` Taco Hoekwater
2008-12-22 18:25 ` Taco Hoekwater
2008-12-21 14:36 Fengnan Gao
2008-12-21 7:19 Fengnan Gao
2008-12-21 11:08 ` Yue Wang
2008-12-22 19:24 ` Alan STONE
2008-12-23 12:32 ` Taco Hoekwater
2008-12-23 18:30 ` Taco Hoekwater
2008-12-24 2:45 ` Fengnan Gao
2008-12-24 10:29 ` Mojca Miklavec
2008-12-24 13:49 ` Alan STONE
2008-12-22 23:05 ` Mojca Miklavec
2008-12-23 12:31 ` Taco Hoekwater
2008-12-24 10:03 ` Taco Hoekwater
2008-12-24 12:54 ` Alan STONE
2008-12-24 13:21 ` Taco Hoekwater
2008-12-24 16:32 ` Alan STONE
2008-12-26 8:40 ` Taco Hoekwater
2008-12-23 15:21 ` Derek CORDEIRO
2008-12-23 15:28 ` Derek CORDEIRO
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=COL106-DS103D8ED8BAD6416F4DDCEFA4EF0@phx.gbl \
--to=fnsteed@hotmail.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).