Jonathan Revusky wrote:

I've heard this before. I think you must mean that FreeMarker's syntax -- the use of <#...> as delimiters -- confuses XML-oriented editors.

It does not confuse them. It is just wrong for XML. Or are you saying freemarker understands things it was not specified to handle?



Because, of course, generally, the claim is not valid: there's no general need for a template to be well formed in its output format. For example, it would be surprising if a raw template used to generate Java code was itself compilable java.If you're generating XML, the key thing is that the output be well formed XML and a lots of people use it for that.

Well, I use Velocity in content chunks that are transformed by XSL to whatever end result. I need the source to be well-formed.


But, anyway, FYI that was just addressed. You can now use an alternative syntax where instead of:

<#assign x = 3>

you write

[#assign x=3]

OK. I guess I would trust velocity at this point.


etcetera. So it's now just as XML-friendly as Velocity is. Though, with the difference that FM is a powerful XML transformation tool and a viable replacement for XSLT.

Is freemarker a standard (sorry, I know the answer :)? Does freemarker have as many/more implementations as there are XSLT processors? I highly doubt freemarker has run into the cases that the more established XSL processors have.

-Rob


Jonathan Revusky


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to