From: Robert Pluim <rpluim@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 34469@debbugs.gnu.org, Lukasz Pawelczyk <l.pawelczyk@samsung.com>,
Nicholas Drozd <nicholasdrozd@gmail.com>
Subject: bug#34469: 26.1; EWW stops renderring web page on null byte
Date: Thu, 28 Feb 2019 09:46:46 +0100 [thread overview]
Message-ID: <m2fts847wp.fsf@gmail.com> (raw)
In-Reply-To: <d6d00cc1-28fd-b59f-ce97-893a688f31df@cs.ucla.edu> (Paul Eggert's message of "Wed, 27 Feb 2019 17:52:52 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Thanks for fixing that bug. However, replacing NUL with \0 sounds iffy.
> Even if we assume that a web page contains C-like code, the replacement
> would mishandle a NUL followed by an octal digit, since the replacement
> would look like \07 which would be interpreted as a BEL character, not
> as a NULL followed by a digit 7. And web pages do not typically contain
> C code, so the replacement \0 might cause other trouble.
>
In my sample of 1 website, 100% of them contained C code :-)
> Instead, it sounds better to replace NUL with the four-character
> sequence "�", as this is a standard HTML way to represent a NUL
> character. I installed the attached patch to do this.
>
OK by me.
Robert
prev parent reply other threads:[~2019-02-28 8:46 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
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 [this message]
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=m2fts847wp.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=34469@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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.