This is arguably not a HTML::Template question but since not many people besides HTML::Template users will have encountered this situation I will ask here.

I have a lot of template code like

<OPTION <TMPL_IF NAME=foo>SELECTED</TMPL_IF>>Foo</OPTION>

and similar for radio buttons and checkboxes. A customer's favorite HTML editing application (DreamWeaver) does not like this syntax, and persists in changing it to

<OPTION><TMPL_IF NAME=foo>SELECTED</TMPL_IF>>Foo</OPTION>
^

(It inserts the extra >).

This after fiddling with DW's options for rewriting HTML, and also trying the comment form of <TMPL_IF>.

I can see two choices, equally unpleasant:

(1) Get customer to use another HTML editor. Only choice appears to be emacs/vi. Customer will detest this option.

(2) Have my application output the whole <OPTION> tag via a <TMPL_VAR> instead of just the SELECTED attribute. I detest this option because customer will not be able to switch between checkboxes, radio buttons, and menus without bugging me.

Has anyone else encountered this situation and found a third solution?
--
Peter Scott
Pacific Systems Design Technologies



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Html-template-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/html-template-users

Reply via email to