[stringtemplate-interest] ST & I18N

[FrankHarper.10118606 at bloglines.com]

Hi STers,

I haven't been able to find support in ST for I18N.

Is it
against the ST philosophy of "separating the specification of a page's business
logic and data computations from the specification of how a page displays
such information."?

My web app generates URLs on the fly based on user
input, which can contain non ascii characters. Sometimes I display the user
input in a page, and sometimes the same information is used to create links.
In this case the the user input has to be url encoded.

The only solution
I've come up with so far is to create two ST attributes with the same information,
one url encoded and one not.

Then of course there's another whole can of
worms that will appear when I actually want to translate the web page contents.
I guess this will require creating an attribute for each string that needs
I18Ning.

I would like to hear from anyone who has ideas or experience on
using ST in an I18Ned app, especially if you've come up with more elegant
solutions than the ones I've mentioned.

Cheers
  Frank