From: Ammar Faizi <[email protected]>
To: Konstantin Ryabitsev <[email protected]>,
Greg Kroah-Hartman <[email protected]>
Cc: Linux Kernel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
Ravel Kevin Ethan <[email protected]>,
Michael William Jonathan <[email protected]>
Subject: Public Inbox Output Broken Due to Double HTML Encoding
Date: Thu, 5 Sep 2024 22:42:54 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
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 <[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]>,
```
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 < (for <) and > (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
next reply other threads:[~2024-09-05 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 15:42 Ammar Faizi [this message]
2024-09-05 15:50 ` Public Inbox Output Broken Due to Double HTML Encoding Konstantin Ryabitsev
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox