SourceForge Logo Designer documentation  

Designer documentation

1. Philosophy
2. ACS tags
3. Quoting

Python documentation





A little would-be FAQ

Q. Suppose I want to show (* and *) in my template, but I don't want AHTS to strip it?

A. Well, just add one more bracket. AHTS will strip one bracket for you. ((* will be shown as (*, (((* as ((*, and so on.

Q. Suppose I want like @foobar@ to appear in the output?

A. Well, just add a backspace before each at: \@foobar\@.

Q. But what if I want to show \@foobar\@?

A. Add one more backslash: \\@foobar\\@.

Q. How do I know when to add a \ before an @, and when not to?

A. Technically, you'd only need to add backslashes when you have two @'s surrounding an possible identifier. But then again, what's an identifier? To make it simple, put backslashes before @'s everytime you write two @'s connected by non-whitespace characters.

Q. I have this master-templated called my"master.tml, and inserting it into a master tag won't work?

A. Add a backslash before the quote: <master src="my\"master.tml">.


The rule of tumb is this: everything can be quoted if you add one more leading character then you normally would do.

Well, this everything is a lie: the tags cannot be quoted, but than again, <else> is not valid HTML-either.

Multiple AHTS-runs

Q. Suppose I want to use AHTS twice, once to put a header and footer around the pages, and a second time at runtime to fill in some variables, possibly coming from a database?

A. This is possible. Surround the piece you don't want to be parsed by <noparse>...</noparse>-tags. AHTS will write everything between those tags verbatim (but strips the <noparse>). The second invocation will parse what's between the tags.

  $Id: quote.tml,v 1.1 2001/04/09 22:36:18 benderydt Exp $