Comments on: Google AJAX Language API first impressions http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/ Wed, 09 Jul 2008 05:59:40 +0000 http://wordpress.org/?v=2.5.1 By: Roland http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/#comment-11291 Roland Wed, 26 Mar 2008 23:32:58 +0000 http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/#comment-11291 If you folks want to see the API in action, we've implemented in a live webchat solution.... <a href="http://hab.la/articles/2008/03/21/hab-la-can-now-translate-the-chat-into-the-language-of-your-choice" rel="nofollow">http://hab.la/articles/2008/03/21/hab-la-can-now-translate-the-chat-into-the-language-of-your-choice</a> If you folks want to see the API in action, we've implemented in a live webchat solution....

http://hab.la/articles/2008/03/21/hab-la-can-now-translate-t.....our-choice

]]> By: Kevin Pirkl http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/#comment-11224 Kevin Pirkl Mon, 24 Mar 2008 19:54:20 +0000 http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/#comment-11224 One big item that I missed is that the return results have the special characters like > or < unicode encoded... If you want to call the API with anything but text you will need to decode that return data... Outbound %3E and inbound \u003e One big item that I missed is that the return results have the special characters like > or < unicode encoded... If you want to call the API with anything but text you will need to decode that return data... Outbound %3E and inbound \u003e

]]> By: choonkeat http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/#comment-11213 choonkeat Mon, 24 Mar 2008 09:00:43 +0000 http://softwareblogs.intel.com/2008/03/21/google-ajax-language-api-first-impressions/#comment-11213 google translate + a wiki interface to contribute corrections (to the site only) might take us far enough to giving 80% website that 80% completeness in i18n. better than 99% websites with 0% i18n support? google translate + a wiki interface to contribute corrections (to the site only) might take us far enough to giving 80% website that 80% completeness in i18n. better than 99% websites with 0% i18n support?

]]>