ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lua in LuaLaTeX is diferent??
Date: Sun, 06 Jun 2010 20:24:43 +0200	[thread overview]
Message-ID: <4C0BE7EB.8020105@gyza.cz> (raw)
In-Reply-To: <4C0B82D4.50703@wxs.nl>

Hi, Hans
Thanks a lot for advice and inspiration. With your contribution of my 
applications running under LuaPlain well below LuaLaTeX :-).
Application process CSV tables and allows you to easily print the data 
in CSV tables (mailmerges, cards, etc). Now I do not know whether 
somebody else will be interested in my application. ConTeXt uses the few 
people around me. Therefore, I try to modify it to LuaTeXu and LuaPlain. 
I think I'm just a lousy programmer, and therefore do not anticipate 
that the application could become a larger library, you could use 
others.  Thanks again for your time and valuable advice
Have a nice day
Jaroslav




Dne 6.6.2010 13:13, Hans Hagen napsal(a):
> On 5-6-2010 10:19, Jaroslav Hajtmar wrote:
>> Hi,
>> I did a Lua application for ConTeXt, and now I wanted to adapt it to
>> work even LuaLaTeX.
>> On what needs to be careful? Compiling by LuaLaTeX specific messages
>> appear as if the Lua in LuaLaTeX didnt know some Lua commands (i.e.
>> split, find .... ).
>>
>> On what needs to be careful generaly when programming applications for
>> LuaLaTeX?
>
> In context there is quite some lua code that can be used by users for 
> their applications. The l-*.lua files can considered to be more 
> general libraries and most ofthat is unlikely to change (extended for 
> sure). At some point I will make a manual for that. Of course you can 
> always load such modules using 'require'.
>
> Using other context lua code outside context is more tricky as it also 
> assumes the system to be designed in a certain way. I hope to have 
> much if that stable within the next few years. As long as one does not 
> mess with the namespaces not much harm can be done.
>
> I'm not following lualatex dev but i know that it uses some of the 
> font code. The reason that this code can be shared is that it's sort 
> of isolated and specific functionality needed is wrapped up in 
> *-dum.lua modules. Probbably some stripping down will happen to 
> prevent clashes etc. Here the reference is luatex-plain.tex (and 
> luatex-fonts.tex) in the context distribution.
>
> Also, the reverse is also tricky: lualatex speicific code is unlikely 
> to work in context.
>
> BTW, Sharing macro code between context and latex is non trivial 
> either as both are different systems and developed completely 
> independent.
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2010-06-06 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 20:19 Jaroslav Hajtmar
2010-06-05 23:35 ` Jaroslav Hajtmar
2010-06-06  2:46   ` Khaled Hosny
2010-06-06  6:15     ` Jaroslav Hajtmar
2010-06-06  6:34       ` Jaroslav Hajtmar
2010-06-06 11:17         ` Hans Hagen
2010-06-06 13:00       ` Khaled Hosny
2010-06-06 11:42   ` Hans Hagen
2010-06-06 11:13 ` Hans Hagen
2010-06-06 18:24   ` Jaroslav Hajtmar [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=4C0BE7EB.8020105@gyza.cz \
    --to=hajtmar@gyza.cz \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).