Using Translation from PEAR, other libraries

What is the common framework people use for I18N on your sites?  John 
Coggenshall has an article in PHPBuilder about using smarty filters. I 
don't really approve of this approach because it is forcing me into 
Smarty, which I am not particularly fond of.

I like the look of PEAR::translation2, but I am not sure about the best 
way to implement it.  I feel that a good I18N package, like any other 
package, doesn't compromise your framework intentions.  This one seems 
to require that you use PEAR:DB through their connection, which is a 
problem because of connection pooling, and the fact that I don't use 
PEAR:DB, I am using propel.

Any thoughts on this?  I need to make a site that is UTF-8 and has 
translations not only for labels and images, but in many cases for 
actual data.

I'm thinking of storing my data in an XML format in MySQL with multiple 
translations and making my own search index for each language.  The 
problem with this is that I have to grab the entire XML doc for each 
field which may have 10-15 translations, parse and then display, wasting 
lots of processing and database time.

I'm not farmilliar with XML databases, and I'm told they are bad voodo, 
but what is another solution if you have to store user entered records 
in 'n' languages?

Thanks
Jacob

-- 
PHP Internationalization Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php