Pablo Rodríguez wrote:
> Hans Hagen wrote:
>> Johannes Graumann wrote:
>>> Dear all,
>>>
>>> What is currently the best source for documentation on mark iv's xml
>>> capabilities?
>> there is a chapter in mk.pdf; next year i'll write a manual (and i'll 
>> probably give a tutorial at the context conference)
> 
> I have read that chapter and I wonder whether this XML handling will be 
> available in LuaTeX or it will be exclusive for ConTeXt.

luatex is just lua + tex + access to each other, the luatex dev team 
will *not* provide solutions; mkiv is what we use for testing etc etc

> Sorry if the question seems to be stupid. I would like to know whether 
> this will be available for LuaTeX + LaTeX one day.

i'm thinking of a multi layer context i.e. kind of macro package 
building subsystem; this means that we can for instance provide a kind 
of bare tex with only core functionality (fonts, languages, io, xml, etc)

i have no plans to support latex if only because i have no need for it; 
the xml parser is rather generic, which is why it is in l-xml, but 
things may change (there will be more functionality, as in lxml-*)

(btw, the lpath code is somewhat experimental and will be extended, as 
will manipulative functions)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to