Line feeds are safely escaped, so yes, you can include them in properties like DESCRIPTION. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-12-11
Thanks for your reply. I will check this by importing the calendar event in a calendar like outlook.
If I add \n in Description and print the event to file, \n is not interpreted, but printed in my file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I guess it wouldn't hurt to add it. The reason I only added it to DateStart is to make it easier to construct the DATESTART properties inside of VTIMEZONE components.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
First of all, thank you for the nice work..
Is there any possibility to have a line feed in the description?
Greetings
Hi,
Line feeds are safely escaped, so yes, you can include them in properties like DESCRIPTION. :)
Thanks for your reply. I will check this by importing the calendar event in a calendar like outlook.
If I add \n in Description and print the event to file, \n is not interpreted, but printed in my file.
When you add line feed to a property value, the resultant property will look something like this:
The "\n" in the property value represents a newline. Is this what you are seeing? What do you expect to see? This is the correct behavior. :)
everything's fine. thanks.
One last thing :)
DateEnd has no Constructor with DateTimeComponents. since DateStart has it, it would be nice if DateEnd has this Constructor too.
I guess it wouldn't hurt to add it. The reason I only added it to DateStart is to make it easier to construct the DATESTART properties inside of VTIMEZONE components.