unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: karl@freefriends.org (Karl Berry)
Cc: ttn@gnuvola.org, emacs-devel@gnu.org
Subject: Re: Texinfo XML support in Emacs Info browser
Date: Mon, 04 Jun 2007 01:47:45 +0300	[thread overview]
Message-ID: <87abvgd4aq.fsf@jurta.org> (raw)
In-Reply-To: <200706032123.l53LN7l22641@f7.net> (Karl Berry's message of "Sun\, 3 Jun 2007 16\:23\:07 -0500")

> How about fixing xml-parse-file so that it can be "permissive"?
> It seems rather strange to use regexps when something was developed
> specifically to parse XML files.  Not that it's my call.

I like xml-parse-file approach, but I doubt that xml-parse-file can be fixed to
parse non-well-formed XML.

After fixing bugs in makeinfo we can achieve the state when Texinfo XML
output of makeinfo is well-formed, so we could completely rely on
correctness of its output, and use xml-parse-file.

Using XML structures from xml-parse-file is very different approach from using
text-based Info files and poses many interesting problems. For example,
how to search manuals for a regexp.  One solution is to traverse the XML tree
and to match its text elements.  But what to do with text split between different
XML elements?  Another solution is to search a regexp in the rendered text
of all nodes.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2007-06-03 22:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 23:03 Texinfo XML support in Emacs Info browser Juri Linkov
2007-06-03  9:39 ` Thien-Thi Nguyen
2007-06-03  9:59   ` Juri Linkov
2007-06-03 21:23     ` Karl Berry
2007-06-03 22:47       ` Juri Linkov [this message]
2007-06-03 23:45         ` Drew Adams
2007-06-06  0:43           ` Stefan Monnier
2007-06-03 23:26       ` Thien-Thi Nguyen
2007-06-03 21:27     ` Richard Stallman

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=87abvgd4aq.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.org \
    --cc=ttn@gnuvola.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).