On Nov 30, 2015 at 22:10, bastian-muttu...@t6l.de wrote:
On 30Nov15 15:44 +0000, Samir Benmendil wrote:
On Nov 29, 2015 at 19:42, Matthias Apitz wrote:
El d?a Sunday, November 29, 2015 a las 05:55:32PM +0100, Bernard Massot
escribi?:
I'm struggling to build mails readable on small screens, ie mails
whose lines wrap correctly even when there are few columns. I'm
indeed thinking of smart phones.
I thought format=flowed would be the answer. However the first
mailer I tried – K9 mail – doesn't support f=f. I guess Android's
native app is no better. So f=f isn't the universal solution.
Your mail renders fine in my Ubuntu mobile phone BQ E4.5, in Dekko
and in mutt, see the screens:
Dekko: http://www.unixarea.de/screenshot20151129_180118205.png
mutt: http://www.unixarea.de/screenshot20151129_180302430.png
f=f seems to be the esoteric way to tackle that problem. All other
users just make sure their terminal is at least 80 chars wide.
text/plain is just what it is, plain text. No formating meta data in
there.
f=f doesn't really have much meta data, just a space at the end of a
line that is still part of the same paragraph.
No it does not: http://rmz.io/ff.png
That screen is approx 65 chars wide/narrow. But also I would not count
that as not readable.
But it doesn't wrap correctly when there are few columns, which is what
Bernard was asking about.
And that is the problem with text/plain and textwidth=72, if you have
less than 72-80 chars you going to run into those wrapping problems. And
on the other hand if you have a very wide terminal and (for some reason)
like to read long lines of text, you can't, because the lines are
forcefully wrapped for you.
With f=f, I can change the textwidth to MY liking and have it formatted
properly.
https://rmz.io/f=f:reflow_wrap=60.png
https://rmz.io/f=f:reflow_wrap=80.png
https://rmz.io/f=f:reflow_wrap=120.png
(note that I reflow all my replies)
You might have better luck with "quoted-printable". "f=f" is much
nicer though.
To my knowledge quopri is an encoding method. I would not say that
could solve the problem here.
quopri can encode long lines and is more widely supported. It would flow
properly if you write your paragraph onto the same line, and don't add
any hard wraps.
