Re: New Gmail interface does not render carriage returns as Line breaks in 4D plain text Emails

2019-04-17 Thread jeff--- via 4D_Tech
It seems that all line breaks must be carriage return/line feed. Here’s what we did that seemed to fix this issue: $BodyText:=Replace string($BodyText;"\r\n";"\r";*) $BodyText:=Replace string($BodyText;"\n";"\r";*) $BodyText:=Replace string($BodyText;"\r";"\r\n";*) --

Re: New Gmail interface does not render carriage returns as Line breaks in 4D plain text Emails

2019-04-17 Thread snicklin via 4D_Tech
Hi Dave, I've seen this too, in v16 and v17. Did anything ever come of this? Steve -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) Archive:

New Gmail interface does not render carriage returns as Line breaks in 4D plain text Emails

2018-08-02 Thread Dave Nasralla via 4D_Tech
Hey all, This may be a bit obscure for most. Our system (for decades) has sent plain text emails (mostly alerts and short notices). It's never been an issue until the new Gmail interface. The new interface does not render line breaks sent as a carriage return. Everything just runs together. Line