From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Texinfo XML support in Emacs Info browser Date: Sun, 3 Jun 2007 16:45:32 -0700 Message-ID: References: <87abvgd4aq.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1180914392 8495 80.91.229.12 (3 Jun 2007 23:46:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 3 Jun 2007 23:46:32 +0000 (UTC) To: "Juri Linkov" , Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 04 01:46:30 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HuzmD-0001t6-69 for ged-emacs-devel@m.gmane.org; Mon, 04 Jun 2007 01:46:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HuzmC-0007v7-K4 for ged-emacs-devel@m.gmane.org; Sun, 03 Jun 2007 19:46:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HuzmA-0007v2-1K for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:46:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Huzm7-0007un-Lu for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:46:20 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Huzm7-0007uk-EY for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:46:19 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Huzm6-00062N-VU for emacs-devel@gnu.org; Sun, 03 Jun 2007 19:46:19 -0400 Original-Received: from rgmgw2.us.oracle.com (rgmgw2.us.oracle.com [138.1.186.111]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id l53NkGRb005113; Sun, 3 Jun 2007 17:46:16 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by rgmgw2.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l53NkFIx011618; Sun, 3 Jun 2007 17:46:15 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-81-137.vpn.oracle.com by acsmt351.oracle.com with ESMTP id 2796250341180914346; Sun, 03 Jun 2007 16:45:46 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <87abvgd4aq.fsf@jurta.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:72170 Archived-At: > 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).