unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: epameinondas@gmx.de, bob@rattlesnake.com, karl@freefriends.org,
	emacs-devel@gnu.org
Subject: XML and emacs (was Re: A new online publishing tool for Texinfo documents.)
Date: 24 Nov 2003 09:43:17 +0000	[thread overview]
Message-ID: <87znemcdai.fsf_-_@kanga.tapsellferrier.co.uk> (raw)
In-Reply-To: <87znemp5a0.fsf@mail.jurta.org>

Juri Linkov <juri@jurta.org> writes:

> Making some XML library available as part of Emacs might be useful.
> Current XML parsing implemented in Emacs Lisp is too slow on large
> XML files.  But maybe building a DOM tree from makeinfo XML output
> is not needed at all.  This might be needed for XML transformation,
> e.g. for reordering the Info nodes.  But for simple text formatting
> a simple sequential SAX-like processor should be enough.  It could
> provide, for instance, the following hooks:
> 
> (defun xml-start-element (name atts))
> 
> (defun xml-characters (str)
>   (insert str))
> 
> (defun xml-end-element (name from to)
>   ;; this could be used to format the inserted text
>   (cond ((equal name "para"))
>          (fill-region-as-paragraph from to)))

Yes. Or STaX which is a new API available only for Java right now and
looks like it's a  bit easier to deal with than SAX.

libxml2 does have a SAX implementation so if I make it part of Emacs
then that would be available.

James Clark and I have already had a discussion about this on the
emacs-devel list. James is writing an XML parser in Emacs Lisp and
his view was that native Elisp is always going to be better than a
foreign library.

I take his point. But there are other reasons why I'd like libxml2
integrated into Emacs (because I use it everywhere else other than
Emacs) so I might do it anyway.



Nic

  parent reply	other threads:[~2003-11-24  9:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22 21:18 A new online publishing tool for Texinfo documents Karl Berry
2003-11-22 21:37 ` Nic Ferrier
2003-11-24  7:57   ` Juri Linkov
2003-11-24  9:11     ` Nic Ferrier
2003-11-25  4:27       ` Richard Stallman
2003-11-25  7:52       ` Juri Linkov
2003-11-25 11:21         ` Kim F. Storm
2003-11-25 10:37           ` Emacs and Javascript/XSLT (was Re: A new online publishing tool for Texinfo documents.) Nic Ferrier
2003-11-25 15:47             ` Stefan Monnier
2003-11-25 17:55             ` Juri Linkov
2003-11-24  9:43     ` Nic Ferrier [this message]
2003-11-24 14:10     ` A new online publishing tool for Texinfo documents Karl Berry
2003-11-25 21:45       ` Juri Linkov
2003-11-24 16:22   ` Richard Stallman
2003-11-24 16:39     ` Nic Ferrier
2003-11-22 21:48 ` A new online publishing tool for Texinfo documents (regarding Lynx and Links) Nic Ferrier
2003-11-23  0:12   ` Alex Schroeder

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87znemcdai.fsf_-_@kanga.tapsellferrier.co.uk \
    --to=nferrier@tapsellferrier.co.uk \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=epameinondas@gmx.de \
    --cc=karl@freefriends.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).