unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
Cc: 59537@debbugs.gnu.org
Subject: bug#59537: `libxml-parse-xml-region` strips out the namespace information, and namespace prefix in the DOM representation
Date: Thu, 24 Nov 2022 13:00:41 +0200	[thread overview]
Message-ID: <83pmdcwrae.fsf@gnu.org> (raw)
In-Reply-To: <TY2PR0101MB3693E0E264287F641FACAC61DA0F9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (message from Ramesh Nedunchezian on Thu, 24 Nov 2022 16:21:30 +0530)

> Date: Thu, 24 Nov 2022 16:21:30 +0530
> Cc: 59537@debbugs.gnu.org
> From: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
> 
> On 24/11/22 15:52, Eli Zaretskii wrote:
> >> Date: Thu, 24 Nov 2022 14:31:52 +0530
> >> From: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
> >>
> >> `libxml-parse-xml-region` strips out the namespace information, and namespace prefix in the DOM representation.
> >>
> >> Stripping out the NAMESPACE information is a bug.
> > AFAICT, we just call a function from libxml2.  So I guess the bug is in that
> > library?
> 
> Do I need to upgrade? 

I don't know.  I'm not sure the latest libxml2 has this fixed.

I'm saying that you should probably discuss this with the libxml2
developers.

> I believe, libxml was introduced to cater to Eww's HTML rendering.

No, we introduced it for any kind of HTML and XML processing we need.





  reply	other threads:[~2022-11-24 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  9:01 bug#59537: `libxml-parse-xml-region` strips out the namespace information, and namespace prefix in the DOM representation Ramesh Nedunchezian
2022-11-24 10:23 ` Eli Zaretskii
2022-11-24 10:51   ` Ramesh Nedunchezian
2022-11-24 11:00     ` Eli Zaretskii [this message]
2022-12-03  0:58       ` Stefan Kangas

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=83pmdcwrae.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59537@debbugs.gnu.org \
    --cc=rameshnedunchezian@outlook.com \
    /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).