On 02/23/2015 10:59 PM, Robert A. Rosenberg wrote: > At 11:59 -0600 on 02/23/2015, Paul Gilmartin wrote about Re: O/T What > ŒThe Imitation Game¹ didn¹t tell you abo: > >> On Mon, 23 Feb 2015 10:14:44 -0600, Joel Ewing wrote: >> >>> In the original Email that I received from Ed the Email source text (as >>> opposed to the way my Email client renders it) shows the presence of a >>> hex-encoded blank (= 2 0) followed by a CR at about the 70-character >>> >> GIYF: >> Character-set: USASCII; Format-flowed >> Content-transfer-encoding: Quoted-printable >> >>> This is certainly a confusing inconsistency in Thunderbird if not an >>> out-right bug (depends on whether this way of wrapping long character >>> strings is actually an approved Email standard). >>> >> RFC 822 requires support for up to 999. > > Format-flowed says that long lines are split with each line ending in > =20CR. Each split line should be no longer than 80 characters (including > the =20CR). Your input meets this format. > > The =20CR is removed and the next line is concatenated until a line does > NOT end with =20CR. At that point you have the original long input line. > This requires that the receiving MUA support Format-flowed however. > > >> >>> Apparently some other >> >Email clients do interpret it in a way that preserves the link. On the >>> other hand there are certainly Email clients that send long URLs without >>> using this formatting convention, as I frequently receive long URLs in >>> Emails (including the reformatted version of this URL from Paul) that >>> work fine with Thunderbird. > > See my prior message. The URL was malformed since it was not included in > angle brackets. URLs without angle brackets are part of the text and are > not indicated as URLs - Thus may not be spotted for special treatment. > Note that such text URLs MAY be correctly handled anyway but you are > playing Russian Roulette with 5 bullets if you do not bracket your URLs. > >> >> -- gil
>From doing some testing with my Thunderbird Email client, which by default does text line wrapping at around 70 chars for composed mail, if I send a long URL in an Email via copy/paste from a browser URL it does not use angle brackets around the URL but does suppress line wrapping in the middle of the URL. >From looking in the IBM-MAIN archives at the original 21 Feb 2015 23:34:42 -0600 posting by Ed Gould and comparing that to the follow-up 22 Feb 2015 08:56:50 -0600 posting by Paul Gilmartin you can see that Paul's post with the usable URL follows the same convention as Thunderbird of suppressing line wrap within the URL while other text lines are wrapped at a shorter length. While the browser display of that archived posting does wrap the URL depending on browser window size, increasing the width of the browser window causes the URL to re-flow to fill the larger width, clearly showing the URL in the post itself is not line wrapped. Just as clearly the original post by Ed has the URL line-wrapped at the same length as ordinary text and the browser link in the IBM-MAIN archive web page display excludes the last two lines intended as part of the URL. Clearly the URL problem has occurred by the time the post is received by IBM-MAIN and whatever convention is used to broadcast the postings to the list members is just preserving that difference. If the technique and application Ed is using to compose his postings does not allow any way to influence line wrapping, then manually inserting angle brackets around the entire URL might circumvent the problem; but I suspect the sending application could still do things in the way it handles line wrap or assigns Email content attributes that might prevent that suggestion from working as well. If Ed has no way to circumvent and it's an interesting enough link, it's not that big of deal for a recipient to circumvent the problem manually by editing the URL. -- Joel C. Ewing, Bentonville, AR [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
