Actually, I have to take back one thing that I said. When using a plain vanilla Properties object to read the properties file, the embedded "\n" seems to be interpreted as a newline character. If I create an email message, the message body has a "real" newline character where I want it.
But if I use TurbineResources to read the property values, the "\n" character shows up in the email message readable characters, rather than as a "real" newline. This is OK if I am sending the string to something that interprets "\n", such as popping up a javascript alert. But if I create an email message with this text, it doesn't have the desired effect. I am not sure why this is happening... Kevin -----Original Message----- From: Kevin Rutherford Sent: Wednesday, September 25, 2002 9:12 AM To: 'Turbine Users List' Subject: RE: TR.props and multiline values I'm not sure if this is what you are looking for, but you can use newline characters in the property value, and you can use the line continuation character (\) at the end of each line in TR.props in order to spread the value across multiple lines. For example: email.text = This is a test\nof the emergency \ broadcast system. This results in a string which looks like this when displayed: This is a test of the emergency broadcast system. Hope this helps. Kevin -----Original Message----- From: Alexander Banthien [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 11:14 PM To: Turbine Users List Subject: TR.props and multiline values Hello, has anyone ever found a way to define multiline keys in TR.props? I would like to put a few email-texts into the config-file and need linebreaks in there. Help appreciated -- regards, Alexander Banthien _______________________________________ Questech GmbH Schwarzwaldstr. 19 79199 Kirchzarten Fon: +49 (0)7661 90 35-15 Fax: +49 (0)7661 90 35-20 www.questech.de _______________________________________ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
