If I have an include with variables in it. If the value of that variable changes with each loop, and I call the include in that loop, then the content of the include will correspondingly change. So I can do a mail-merge kind of thing.
If my loop is a mail merge and has lots of iterations, I break the rules, so I can't use includes in this situation. If I call the include before the loop, then the embedded variables will resolve to whatever they are before the loop starts, and they will never change as the loop cycles through, so that's not so useful. That's what it looks like to me. Am I right? (I'm on 5.0) I don't think this is an issue of encoding, but when variables are resolved. It's not a huge deal. Just perplexed me why all my tafs with any includes in all domains stopped. When it dawned on me what was going on, I tried the <@literal> tag, but it didn't help because it never resolved. On 9/19/04 10:12 PM, "Phil Wade" <[EMAIL PROTECTED]> wrote: >> If I read the include into a variable before the loop, I can't embed >> variables that change in each loop. > > This is a summary of the encoding methods in 5.5. I think they make sense > now. > > The NONE value for the ENCODING attribute allows you to indicate that the > value returned by the meta tag contains formatting codes that are to be > passed back to the user's Web browser without any translations. > > The HTML value for the ENCODING attribute allows you to indicate that the > value returned by the meta tag contains HTML formatting codes that are to be > translated as they are passed back to the user's Web browser. I.e. > < & ' > and " are translated to the html encoding equivalent. > > The META attribute value of the ENCODING attribute performs the same > function as NONE but also looks for Witango meta tags in the value and > evaluates any it finds. > > The METAHTML attribute value lets you combine the functions of META and > HTML. > > The MULTILINE attribute value causes Witango to replace return, line feed, > and return/line feed combinations in the value with <BR> tags. It will not > do HTML encoding. > > The MULTILINEHTML attribute value lets you combine the functions of HTML and > MULTILINE. > > > > In Witango Server 5.5 <@VAR scope$varname encoding="meta"> will resolve the > meta tags in the variable without html encoding before pushing it onto the > results buffer. > > In Witango Server 5.0 <@VAR scope$varname encoding="metahtml"> will resolve > the meta tags in the variable without html before pushing it onto the > results buffer. > > > > This is the reason we cleaned up the encoding names in Witango Server 5.5. > No one seemed to know what they really did. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
