From: "Thomas Weißschuh" <firstname.lastname@example.org> To: email@example.com Subject: Windows-style linebreaks (\r\n) and the web-renderer Date: Fri, 14 Jan 2022 21:48:22 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) 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://email@example.com/ 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. Thanks, Thomas
next reply other threads:[~2022-01-14 20:48 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 20:48 Thomas Weißschuh [this message] 2022-02-11 20:22 ` [PATCH] view: remove all CR before LF Eric Wong
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Windows-style linebreaks (\r\n) and the web-renderer' \ /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).