all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Sending mail: line wrapping and quoted-printable encoding
Date: Tue, 28 Apr 2020 16:37:39 +0200	[thread overview]
Message-ID: <87a72vn0b0.fsf@no.workgroup> (raw)
In-Reply-To: <draft-prg8v9lk8t9y.fsf@butoi.nyc.corp.google.com>

Hi Radu, emacs users,
* Radu Butoi <rbutoi@gmail.com> [2020-04-27; 18:20]:
> Gregor Zattler <telegraph@gmx.net> writes:
>> And then there is the question who other providers will show
>> quoted-printable E-Mails in their clients (web interfaces).
>
> I appreciate your skepticism here :-) -- but from everything I've read the quoted-printable encoding is well-supported by most/all email clients. It is from RFC2045 (MIME), whereas f=f is the lesser-supported RFC3676. Doing a search of my maildir, I find a large majority of them contain it. To test this, I'll be sending this message without hard-wrapping and with the Q-P encoding. If it shows up fine, I think I need to `edebug` the Emacs MIME library to find out exactly what's going wrong.

This paragraph of yours is wrapped fine by notmuch show, but
this is to expect, it's merely a single long line.  I do not
re-fill it here.

f=f is different though it:

1. f=f renders paragraphs with soft line breaks thus every
   email client should be able to show it even if not able
   to grok f=f.
2. f=f enabled mail clients are not only capable of
   re-flowing the paragraphs to the window size, but even
   quoting in several levels is preserved while reflowing
   the paragraphs


>> thanks a lot for this screenshot.  Obviously this also
>> depends on the users font size.  I now re-wraped this whole
>> email to 60 chars per line and hope it displays well.
>
> Ah, there's no need to do that, since it is clearly Gmail
> who is at fault here. Emacs is my main way or reading and
> writing mail, I'd just like to have the option to use my
> phone.

I re-filled your last paragraph.

I fiddled around f=f several years ago and found

a. support in email clients to be lacking
b. f=f does not support, but to the contrary ruins, plain
   lists and indented paragraphs.


Points a. and b. were deal breakers for me and so I stay
with hard line breaks till today.  But since I want my
emails to be readable even for people on mobile devices I
opted for short lines.  Thus your screenshot is really
helpful for me.

> Thanks for your responses! And let me know if this shows up okay.

Have a look for yourself, ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-




  reply	other threads:[~2020-04-28 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  0:19 Sending mail: line wrapping and quoted-printable encoding Radu Butoi
2020-04-26  0:24 ` Radu Butoi
2020-04-26  0:38   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-26 18:44     ` Radu Butoi
2020-04-27  7:50       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-26  8:00 ` Gregor Zattler
2020-04-26 18:44   ` Radu Butoi
2020-04-27  8:52     ` Gregor Zattler
2020-04-27 22:20       ` Radu Butoi
2020-04-28 14:37         ` Gregor Zattler [this message]
2020-05-05 21:44           ` Radu Butoi
2020-05-06  7:37             ` Gregor Zattler

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 \
    --in-reply-to=87a72vn0b0.fsf@no.workgroup \
    --to=telegraph@gmx.net \
    --cc=help-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.