Yahoo YQL Web JSON Google for Two Translate Speech Tutorial

Posted on by
Yahoo YQL Web JSON Google for Two Translate Speech Tutorial

Yahoo YQL Web JSON Google for Two Translate Speech Tutorial

Today we continue with Yahoo Web Services called YQL, building on previous tutorial here at Yahoo YQL Web Service JSON Google for Two Translate Tutorial as shown below. The name is the way it is because it simplified the API aspects of its functionality for the developer to concentrate on SQL, and I’m really supportive of this concept. You don’t have to output in JSON, as other data forms like XML are acceptable. Let’s see what Wikipedia says about YQL below.

Yahoo! Query Language (YQL) is an SQL-like query language created by Yahoo! as part of their Developer Network. YQL is designed to retrieve and manipulate data from APIs through a single Web interface, thus allowing mashups that enable developers to create their own applications.[1]

Initially launched in October 2008 with access to Yahoo APIs,[2] February 2009 saw the addition of open data tables from third parties such as Google Reader, the Guardian, and The New York Times.[3] Some of these APIs still require an API key to access them. On April 29th of 2009, Yahoo introduced the capability to execute the tables of data built through YQL using JavaScript run on the company’s servers for free.[3]

So this tutorial uses a YQL web service into the data emanating from its links to the Google Translate google.translate database with Yahoo YQL website … thanks. You join up with a person talking in another language, share the computer, or tablet, and type your single sentences, one at a time, into your relevant HTML textarea element, get it translated into the other language, which you’ve first selected from a dropdown, and then the other user has their go … if you want you can be totally silent (but probably laughing a lot). We’ve extended the functionality today to allow the users to hear an audio interpretation of their words in a window.open popup window calling on the amazing Google Translate Text-to-Speech functionality.

The two big PHP functions of use for this are:

Good links for information regarding this tutorial (thanks) are:

Another tool you should have in your armoury for jobs like this is the online JSON validator here. A generic JSON approach to issues could be:

  1. Type the URL you were given into a web browser address bar and have a look at it
  2. Type the URL you were given into http://jsonlint.com/ and have it validated
  3. Understand in your own mind what would be different about 1. to make it suitable
  4. Incorporate findings of 3. into massaging of data between file_get_contents and json_decode

Here is a link to some downloadable HTML programming source code which you may want to rename to google_four_translate.html which calls some downloadable PHP programming source code which you may want to rename to google_four_translate.php (and then there is a live run). For the modifications of today, only the HTML needed to change, believe it or not, and these changes are presented with google_four_translate.html link.

Previous relevant Yahoo YQL Web Service JSON Google for Two Translate Tutorial is shown below.

Yahoo YQL Web Service JSON Google for Two Translate Tutorial

Yahoo YQL Web Service JSON Google for Two Translate Tutorial

Here is a tutorial that might be re-introducing you to the Yahoo Web Services called YQL, building on previous ones here at this blog. The name is the way it is because it simplified the API aspects of its functionality for the developer to concentrate on SQL, and I’m really supportive of this concept. You don’t have to output in JSON, as other data forms like XML are acceptable. Let’s see what Wikipedia says about YQL below.

Yahoo! Query Language (YQL) is an SQL-like query language created by Yahoo! as part of their Developer Network. YQL is designed to retrieve and manipulate data from APIs through a single Web interface, thus allowing mashups that enable developers to create their own applications.[1]

Initially launched in October 2008 with access to Yahoo APIs,[2] February 2009 saw the addition of open data tables from third parties such as Google Reader, the Guardian, and The New York Times.[3] Some of these APIs still require an API key to access them. On April 29th of 2009, Yahoo introduced the capability to execute the tables of data built through YQL using JavaScript run on the company’s servers for free.[3]

So this tutorial uses a YQL web service into the data emanating from its links to the Google Translate google.translate database with Yahoo YQL website … thanks. You join up with a person talking in another language, share the computer, or tablet, and type your single sentences, one at a time, into your relevant HTML textarea element, get it translated into the other language, which you’ve first selected from a dropdown, and then the other user has their go … if you want you can be totally silent (but probably laughing a lot).

The two big PHP functions of use for this are:

Good links for information regarding this tutorial (thanks) are:

Another tool you should have in your armoury for jobs like this is the online JSON validator here. A generic JSON approach to issues could be:

  1. Type the URL you were given into a web browser address bar and have a look at it
  2. Type the URL you were given into http://jsonlint.com/ and have it validated
  3. Understand in your own mind what would be different about 1. to make it suitable
  4. Incorporate findings of 3. into massaging of data between file_get_contents and json_decode

Here is a link to some downloadable HTML programming source code which you may want to rename to google_four_translate.html which calls some downloadable PHP programming source code which you may want to rename to google_four_translate.php (and then there is a live run).

If this was interesting you may be interested in this too.

If this was interesting you may be interested in this too.

This entry was posted in Data Integration, eLearning, Tutorials and tagged , , , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *