unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: meta@public-inbox.org
Subject: [PATCH] view: remove all CR before LF
Date: Fri, 11 Feb 2022 20:22:17 +0000	[thread overview]
Message-ID: <20220211202217.GA19151@dcvr> (raw)
In-Reply-To: <8d13668f-cac7-4984-bb4e-ad90502dc46d@t-8ch.de>

Thomas Weißschuh <thomas@t-8ch.de> wrote:
> Hi,
> 
> it seems the rendering of \r\n (Windows-style) linebreaks, is a bit suboptimal
> on the website.
> 
> The \r are rendered literally. Mutt for example does not.
> 
> Example: https://lore.kernel.org/lkml/20210914093515.260031-1-maxime@cerno.tech/

Thanks for the example.

> Raw message:
>     ...
>     Content-Type: text/plain; charset="utf-8"
>     Content-Transfer-Encoding: quoted-printable
>     ...
> 
> 
>     Hi,=0D
>     =0D
>     ....
> 
> Rendered:
> 
>     ....
>     Hi,\r
>     \r
>     ...
> 
> 
> The fix is probably obvious for you, if not I can try to come up with one.

Yes, except I remember adding support for CR-LF long ago...
The problem here is some messages are CR-CR-LF for some odd reason.
Oh well, it's a 1 character fix on our end for the HTML.

Not sure if ContentHash (deduplication) and SolverGit (blob
regeneration) ought to strip redundant CR, yet...

-------8<-------
Subject: [PATCH] view: remove all CR before LF

While we've rendered CR-LF as LF-only in HTML for many years,
some messages end up as CR-CR-LF.  So strip ALL all CR bytes
preceding LF bytes, while preserving odd CR in the middle of
lines.

Reported-by: Thomas Weißschuh <thomas@t-8ch.de>
Link: https://public-inbox.org/meta/8d13668f-cac7-4984-bb4e-ad90502dc46d@t-8ch.de/
---
 lib/PublicInbox/View.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index 2e9cf705..ca02ae05 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -586,7 +586,7 @@ sub add_text_body { # callback for each_part
 
 	# makes no difference to browsers, and don't screw up filename
 	# link generation in diffs with the extra '%0D'
-	$s =~ s/\r\n/\n/sg;
+	$s =~ s/\r+\n/\n/sg;
 
 	# will be escaped to `&#8226;' in HTML
 	obfuscate_addrs($ibx, $s, "\x{2022}") if $ibx->{obfuscate};

      reply	other threads:[~2022-02-11 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 20:48 Windows-style linebreaks (\r\n) and the web-renderer Thomas Weißschuh
2022-02-11 20:22 ` Eric Wong [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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220211202217.GA19151@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=thomas@t-8ch.de \
    --subject='Re: [PATCH] view: remove all CR before LF' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).