I wrote the following filter for that reason (and also WYSIWYG editors), but
didn't get any feedback on whether this was worth trying to integrate.
sub filter_template {
my $text_ref = shift @_;
$$text_ref =~ s/\{%(.*?)%\}/<tmpl_var name="$1">/g;
}
It seems that HTML/XHTML validation should be possible by default. I
considered using *vanguard_compatibility_mode* flag but since I know nothing
of vangard or how long it would remain compatible....
-----Original Message-----
From: htm...@li...
[mailto:htm...@li...] On Behalf Of Tobias
Grimm
Sent: Tuesday, January 18, 2005 6:51 PM
To: htm...@li...
Subject: [htmltmpl] Valid XHTML templates
Hi!
Is there any way to use a valid XHTML document as template? As far as I
tried
this seems to be not possible.
e.g.:
[1] valid XHTML, working:
<title><tmpl_var name="title"/></title>
[2] valid XHTML, but not working:
<option value="<tmpl_var name>"><tmpl_var name="name"/></option>
[3] invalid XHTML, not working either
<option value="<tmpl_var name>"><tmpl_var name="name"/></option>
[4] invalid XHTML, but working (just removed the slash, this worked in [1]!)
<option value="<tmpl_var name>"><tmpl_var name="name"></option>
The template needs to be valid xml, to be processed for translations. My
current solution is to transform the valid XHTML to an invalid template
that HTML::Template can deal with. But I would prefer feeding HTML::Template
directly with the XHTML file.
Any ideas?
Someone mentioned a patch to use {%TMPL_xxx%} instead of <TMPL_xxx>. Is
there
already a working version of this patch available?
bye,
Tobias
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Html-template-users mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/html-template-users
|