After some discussion we came to the conclusion that there are no real use cases for the template-version of rawoutput.
Using the rawoutput-template would disable the HTML-escaping inside its body.

It is currently only used in built-in.app, for which the ordinary, more clean, rawoutput function would suffice* , and internally by the compiler for ajax event constructs which are not documented and should also be removed (issue(WebDSL/713)).

*Usage in built-in.app :

    rawoutput{ //don't escape the html from internal email rendering
      output(q.body)
  }

may become:

    //don't escape the html from internal email rendering
    rawoutput( q.body )

Submitted by Elmer van Chastelet on 14 May 2013 at 14:49

dropped in r5699

I thought that I already checked the usages of this template, but it seems that it is used on various places. Maybe re-enable for compatibility…

rawoutput was used on the wrong location in case of reposearch. Other references to the template-version (rawoutput{ ... }) are in old code from the structure-evolution project. Only one usage needs to be replaced in Eelco’s blog app:

define copyright() { rawoutput{ "&copyright;" } }

to

define copyright() { rawoutput( "&copyright;" ) }