all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicholas Drozd <nicholasdrozd@gmail.com>
Cc: 34469@debbugs.gnu.org, l.pawelczyk@samsung.com
Subject: bug#34469: 26.1; EWW stops renderring web page on null byte
Date: Thu, 14 Feb 2019 21:14:12 +0200	[thread overview]
Message-ID: <83ef8anpx7.fsf@gnu.org> (raw)
In-Reply-To: <CABAiW0ocfkB0Ld71CwJ29ZUg6Eih5c2m968YYKBa9KTnhfzUqQ@mail.gmail.com> (message from Nicholas Drozd on Wed, 13 Feb 2019 22:44:50 -0600)

> From: Nicholas Drozd <nicholasdrozd@gmail.com>
> Date: Wed, 13 Feb 2019 22:44:50 -0600
> 
> This looks a problem with libxml-parse-html-region (or maybe even
> lower than that, I have no idea).

libxml-parse-html-region calls parse_region, which passes a C string
to libxml functions.  So there can be no embedded null bytes.

Does libxml have facilities to deal with such cases?  If not, maybe
this should be taken up with libxml developers.





  reply	other threads:[~2019-02-14 19:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190213122718eucas1p26156656a2376e5055452ac4d0385fc6d@eucas1p2.samsung.com>
2019-02-13 12:27 ` bug#34469: 26.1; EWW stops renderring web page on null byte Lukasz Pawelczyk
2019-02-14  4:44   ` Nicholas Drozd
2019-02-14 19:14     ` Eli Zaretskii [this message]
2019-02-16 18:13   ` Nicholas Drozd
2019-02-19  1:12     ` Glenn Morris
2019-02-19 10:06       ` Robert Pluim
2019-02-19 16:30         ` Eli Zaretskii
2019-02-19 17:37           ` Robert Pluim
2019-02-19 18:11             ` Eli Zaretskii
2019-02-20 18:48               ` Robert Pluim
2019-02-27 11:31                 ` Robert Pluim
2019-02-27 15:55                   ` Eli Zaretskii
2019-02-27 16:21                     ` Robert Pluim
2019-02-28  1:52   ` Paul Eggert
2019-02-28  8:46     ` Robert Pluim

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=83ef8anpx7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34469@debbugs.gnu.org \
    --cc=l.pawelczyk@samsung.com \
    --cc=nicholasdrozd@gmail.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 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.