Sure you don't have to assign it to a semantic property but the text will be wraped in a template which brings us to a problem. The problem is that in this text not everything is allowed. 
That brings me to the question I wrote earlier - how can we better develop escaping. Multiple {{{free text}}}s is also an alternative to escaping. 
Yury Katkov

On Thu, Jun 14, 2012 at 1:32 PM, Stephan Gambke <> wrote:
Hi Kim,

the problem is, that free text has no identification attached to it in
the final page. There is no definite way for SF to figure out which
piece of text goes where.
What you can do instead is to define a normal text area input and then
display this in the template however you want. You don't have to
assign it to a semantic property.


On 14 June 2012 11:23, Kim Eik <> wrote:
> Today if you specify two or more {{{standard input|free text}}} a form
> page and you input value in them both. Only the last value will be
> displayed, and also duplicated over all instances of the {{{standard
> input|free text}}}.
> Why is this? Say if someone wanted to have a form in the middle of a
> page, and some free text above and below the form. How would one go
> about achieving this?
> Would it be possible to extend the {{{standard input|free text}}} with
> an extra parameter giving it a name, so that content would not be
> duplicated and you could indeed have several instances of this input?
> Cheers Kim

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
Semediawiki-devel mailing list