I can't ever remember the rules for when it's needed, but try enclosing the paragraph symbols in double quotes.
Sent from my iPhone
Thank you for the suggestion, but we tried that (enclosing the paragraph mark in quotes) but that didn’t change anything.
For what it’s worth: Lisa is running FileMaker Pro 12 on a Macintosh. Her email program is Outlook 2011 for Mac.
Gary M. Torborg
Southern Methodist University
w: 214-768-7211 or 214-768-7957
Context | Learner | Intellection | Analytical | Connectedness
I liked this up because I remembered something about Outlook. My notes say to use "<br/>" in place of the paragraph symbol when dealing with Outlook. My notes also say that Windows users will be okay with this as well.
Be sure to test with different recipient mail clients if possible unless you are in a controlled environment.
Hope this helps.
Sent from my iPhone
Copy your calc definition into a text editor, substitute "¶" with "CHAR(13)", select all, copy, paste back into field definition.
It will work this time.
Char(13) is same as ¶ in result (CR), so if ¶ is not working, Char(10) or Char(13)&Char(10) have chance. (LF or CRLF)
But, on Mac CR is normal line break character.
gtorborg77, are you usiing open URL mailto: protocol instead of Send mail script step? Then the parts of URL should be urlencoded.
Try not using all of the & symbols to create breaks, but simply put the Paragraph symbol within the quoted text where you want the breaks.
Thanks, all. I have submitted two of the above ideas to Lisa for testing.
Sorry I don't have Outlook on Mac, so tested on Windows and have no problem.
Then I guessed there is something other than linefeed chars on their side.
If the resulted text is treated as HTML source, line break will have no effect on view...
Quick and dirty workaround. Wrap the entire calculation in the GetAsCSS ( ) function. The HTML engine in Outlook will format the email using paragraph spacing.
Thanks, everyone who tried to help with this issue. The only solution out of the several that were submitted was the last one, where the entire function was wrapped in a GetAsCSS function. None of the other ideas worked at all; in fact, all the other ideas made no difference of any kind.