[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34469: 26.1; EWW stops renderring web page on null byte
From: |
Robert Pluim |
Subject: |
bug#34469: 26.1; EWW stops renderring web page on null byte |
Date: |
Thu, 28 Feb 2019 09:46:46 +0100 |
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
- bug#34469: 26.1; EWW stops renderring web page on null byte, (continued)
- bug#34469: 26.1; EWW stops renderring web page on null byte, Glenn Morris, 2019/02/18
- bug#34469: 26.1; EWW stops renderring web page on null byte, Robert Pluim, 2019/02/19
- bug#34469: 26.1; EWW stops renderring web page on null byte, Eli Zaretskii, 2019/02/19
- bug#34469: 26.1; EWW stops renderring web page on null byte, Robert Pluim, 2019/02/19
- bug#34469: 26.1; EWW stops renderring web page on null byte, Eli Zaretskii, 2019/02/19
- bug#34469: 26.1; EWW stops renderring web page on null byte, Robert Pluim, 2019/02/20
- bug#34469: 26.1; EWW stops renderring web page on null byte, Robert Pluim, 2019/02/27
- bug#34469: 26.1; EWW stops renderring web page on null byte, Eli Zaretskii, 2019/02/27
- bug#34469: 26.1; EWW stops renderring web page on null byte, Robert Pluim, 2019/02/27
bug#34469: 26.1; EWW stops renderring web page on null byte, Paul Eggert, 2019/02/27
- bug#34469: 26.1; EWW stops renderring web page on null byte,
Robert Pluim <=