all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Juri Linkov" <juri@jurta.org>, <emacs-devel@gnu.org>
Subject: RE: Texinfo XML support in Emacs Info browser
Date: Sun, 3 Jun 2007 16:45:32 -0700	[thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMAEBDDCAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87abvgd4aq.fsf@jurta.org>

> 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.

Search is specific to the medium at hand. So, yes, it would be appropriate
to search the _rendered_ text, however it might be rendered. For example,
for PDF output, a PDF reader's search function could be quite different from
Info's. Likewise, for XHTML, a browser's search could be different from
Info's.

I doubt there would be much call for searching the underlying XML, but, if
there were, then XQuery or XPath expressions would be appropriate. I see no
sense in trying to regexp search across XML nodes, with the possible
exception of searching only the text() nodes (as you mentioned).

  reply	other threads:[~2007-06-03 23:45 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
2007-06-03 23:45         ` Drew Adams [this message]
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

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

  git send-email \
    --in-reply-to=EIENLHALHGIMHGDOLMIMAEBDDCAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.