On Oct 27, 6:24 pm, zuha <[email protected]> wrote: > What I'm talking about is this : http://translate.google.com/translate_tools > > And that does allow you to have specific translations for specific pages > and/or websites, but also will automatically translate using a world wide > translation system. (In other words it takes advantage of a social > database of translations which get better as more people use it.)
If you're happy that your translated content is purely in js, and your site is completely invisible in translated languages - by all means. > > So scalability wise - you can translate your app into 50 different > languages immediately and then have it improved upon at anytime by any > visitor to your site because they can contribute a better translation at > the click of a button. That's fine if your site is community driven, not so if you need control over the translations. I think you're looking at google translate like it's a golden bee-bee, it's not. It's a means of making pages on the web that you can't understand understandable. It's not an appropriate means of having a site you can say is multilingual. In summary: Google translate is a user tool, it's not a web- development tool. AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
