in reply to Re^18: aXML vs TT2
in thread aXML vs TT2

No. Where did you get that idea from?

From Re^12: aXML vs TT2 (Solution 3). It implies that "Rock & Roll" produces "Rock & Roll" (which is invalid XML). Now you tell me that's not the case. Could you fill in the blanks in the following table so I can understand.

In aXML templateOutput by aXMLReference
&lt;<Re^12: aXML vs TT2 (Solution 3)
&gt;>Re^12: aXML vs TT2 (Solution 3)
&amp;&amp;Re^18: aXML vs TT2
???&gt;
???&lt;
???&

Replies are listed 'Best First'.
Re^20: aXML vs TT2
by Logicus (Initiate) on Oct 23, 2011 at 05:54 UTC
    In aXML Template Output by aXML
    &lt; &lt;
    &gt; &gt;
    &amp; &amp;
    &lb; (
    &rb; )
    &lsb; [
    &rsb; ]

    As in... all data passes through unaltered, unless the parser recognises it as a valid tag to be processed, or it is one of the 4 extra specials needed to output aXML fragments without processing them.

[reply]
[d/l]
[select]

      Earlier, you said "&lt;db_select&gt;" outputs "<db_select>", but now you say it outputs "&lt;db_select&gt;".

      So how do I output "<db_select>" if db_select is a plugin? What about outputting "&lt;db_select&gt;"?

[reply]
[d/l]
[select]

        Ok there's two issues here, outputting to a browser, and outputting a literal string.

        In the context of making the browser display <db_select>, you can use the specails the browser understands, &lt;db_select&gt;

        In the context of outputting the literal string the only way to do that that I can think of is using a <post_include> type plugin, and storing the string you want literally output without being processed, in a separate file which is included post processing immediately prior to exit.

        
in the aXML
-----------

  <post_include>path/to/splarg</post_include>


in 'splarg'
-----------

  <db_select> 
    ...

        [download]
[reply]
[d/l]
[select]

In Section Meditations