public inbox for [email protected]
 help / color / mirror / Atom feed
* Public Inbox Output Broken Due to Double HTML Encoding
@ 2024-09-05 15:42 Ammar Faizi
  2024-09-05 15:50 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 2+ messages in thread
From: Ammar Faizi @ 2024-09-05 15:42 UTC (permalink / raw)
  To: Konstantin Ryabitsev, Greg Kroah-Hartman
  Cc: Linux Kernel Mailing List, GNU/Weeb Mailing List,
	Alviro Iskandar Setiawan, Ravel Kevin Ethan,
	Michael William Jonathan


Hi,

We have noticed a recent issue with the lore public inbox output where
it appears to be affected by double HTML encoding. This problem
surfaced after 1 September 2024, as that was the last time we observed
the correct output.

The issue is particularly visible in email headers, where characters
such as <, >, and quotes are incorrectly encoded twice. This results in
unreadable and improperly rendered email headers. It also breaks
several links in the HTML output.

For instance, in this thread:

    https://lore.kernel.org/qemu-devel/[email protected]/

Here's the current, broken output:
```
From: Gerd Hoffmann &lt;[email protected]&gt;
To: [email protected]
Cc: &#34;Paolo Bonzini&#34; &lt;[email protected]&gt;,
	&#34;Yanan Wang&#34; &lt;[email protected]&gt;,
	&#34;Zhao Liu&#34; &lt;[email protected]&gt;,
	&#34;Eduardo Habkost&#34; &lt;[email protected]&gt;,
	&#34;Richard Henderson&#34; &lt;[email protected]&gt;,
	&#34;Marcel Apfelbaum&#34; &lt;[email protected]&gt;,
	&#34;Philippe Mathieu-Daud&#233;&#34; &lt;[email protected]&gt;,
	&#34;Michael S. Tsirkin&#34; &lt;[email protected]&gt;,
```

And here's the expected output:
```
From: Gerd Hoffmann <[email protected]>
To: [email protected]
Cc: "Paolo Bonzini" <[email protected]>,
	"Yanan Wang" <[email protected]>,
	"Zhao Liu" <[email protected]>,
	"Eduardo Habkost" <[email protected]>,
	"Richard Henderson" <[email protected]>,
	"Marcel Apfelbaum" <[email protected]>,
	"Philippe Mathieu-Daudé" <[email protected]>,
	"Michael S. Tsirkin" <[email protected]>,
	"Gerd Hoffmann" <[email protected]>
```

It seems like the encoding process is being applied redundantly, causing
special characters like &lt; (for <) and &gt; (for >) to render
improperly. This double encoding affects both usability and
readability, especially when dealing with email threads that rely
heavily on clear headers for communication between contributors.

For reference, I have also attached a screenshot of the output, which
can be found here:

    https://gist.github.com/ammarfaizi2/bbb1480822ece70cf2d261e876bd7ba2

It would be great if this could be resolved as soon as possible to
restore the proper display of inbox outputs.

Thank you for your attention to this matter!

-- 
Ammar Faizi


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Public Inbox Output Broken Due to Double HTML Encoding
  2024-09-05 15:42 Public Inbox Output Broken Due to Double HTML Encoding Ammar Faizi
@ 2024-09-05 15:50 ` Konstantin Ryabitsev
  0 siblings, 0 replies; 2+ messages in thread
From: Konstantin Ryabitsev @ 2024-09-05 15:50 UTC (permalink / raw)
  To: Ammar Faizi
  Cc: Greg Kroah-Hartman, Linux Kernel Mailing List,
	GNU/Weeb Mailing List, Alviro Iskandar Setiawan,
	Ravel Kevin Ethan, Michael William Jonathan

On Thu, Sep 05, 2024 at 10:42:54PM GMT, Ammar Faizi wrote:
> 
> Hi,
> 
> We have noticed a recent issue with the lore public inbox output where
> it appears to be affected by double HTML encoding. This problem
> surfaced after 1 September 2024, as that was the last time we observed
> the correct output.

This is an intermittent problem that is known and reported upstream:
https://public-inbox.org/meta/20240904-fearless-solid-toucanet-a70afa@meerkat/T/#t

-K

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-09-05 15:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-09-05 15:42 Public Inbox Output Broken Due to Double HTML Encoding Ammar Faizi
2024-09-05 15:50 ` Konstantin Ryabitsev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox