The problem multiple language support is that, in my opinion, it needs to be for every aspect of the page. That is not just titles and comments but tooltips, metadata, home links, About/Contact pages etc.
Yes and no.

As I remember Cameleon was able to handle just that, titles and comments, nothing more or less. That would do the trick for me.
That's why I made Polyglot (based on Laza's Chameleon language support). It is the only truly multi-language skin, it's also the reason why the design is simple - the JavaScript required is horrendous.
Please don't get me wrong. But I really like the Tiger skin, as I liked Turtle and Chameleon. Using another skin, for whatever reason, wouldn't be an option to me.
More to the point, these days mobile devices (at least Safari on iOS) have built in translation of web page texts (even speaking the translated text if wanted). It can't be long until desktop browsers have the same facility.
I assume you are right, "online" translation will become more and more a standard. Nevertheless I don't like that other companies "grab" the text of my homepage and process it. Of course I know I can't prevent them to do so.