In the past I ended up turning the templates into perl programs. I made
all the decisions within the template and then built the output based on
that logic. It wasn't very pretty (it was ugly, actually), but it
worked flawlessly for years. Gotta be careful with maintenance on the
templates,
On 6 September 2013 11:04, Landon Stewart lstew...@iweb.com wrote:
What I think I can do is simply have one very short Template that is
basically 100% perl and includes some text from a text file stored on the
file system but outside RTIR. Which file gets included in the Template is
On 6 September 2013 11:55, Landon Stewart lstew...@iweb.com wrote:
Actually I believe I found the answer which I'm going to try… I basically
need a hybrid of these two because we also send different copies of
templates depending on the language the customer prefers to be communicated
with
