I've never done much investigation. the only strategy i've ever used is putting all front-end strings in an xml file, then swapping xml files per language. or letting users customize their own xml file. of course, it doesn't help for multi-cultural sites, eg reading right to left, customizing navigation menus, etc.
not sure i'd trust a translation API. not if you have actual paying customers using it, anyway. if you're gonna use some automated service, might as well use the xml strategy and run a file through the API instead of using the API on the fly every time.
This post was edited by carteblanche on Jul 22 2014 01:22am