ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MKIV and XML documentation
Date: Tue, 18 Dec 2007 16:26:53 +0100	[thread overview]
Message-ID: <4767E6BD.4050107@wxs.nl> (raw)
In-Reply-To: <4767B908.40602@web.de>

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
___________________________________________________________________________________


  parent reply	other threads:[~2007-12-18 15:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 16:15 Johannes Graumann
2007-12-17 21:18 ` Hans Hagen
2007-12-18 12:11   ` Pablo Rodríguez
2007-12-18 13:04     ` luigi scarso
2007-12-18 16:22       ` Hans Hagen
2007-12-18 15:26     ` Hans Hagen [this message]
2007-12-18 13:13   ` Johannes Graumann
2007-12-18 13:39     ` Wolfgang Schuster
2007-12-18 14:03       ` Johannes Graumann
2007-12-18 14:13         ` Wolfgang Schuster
2007-12-18 14:31           ` Johannes Graumann
2007-12-19 11:52             ` Wolfgang Schuster
2007-12-19 13:11               ` Hans Hagen
2007-12-19 17:22                 ` Johannes Graumann
2007-12-23 13:59                 ` Johannes Graumann

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=4767E6BD.4050107@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).