30 Mayıs 2012 Çarşamba

Transliteration API adds 6 more languages

To contact us Click HERE

We're excited to announce the addition of 6 new languages (Greek, Russian, Serbian, Sanskrit, Amharic, Tigrinya) to the Transliteration API. Using Google Transliteration you can convert Roman characters to their phonetic equivalent in your language. Note that this is not the same as translation — it's the sound of the words that are converted from one alphabet to the other.

Transliteration API allows this functionality to be available to all websites, which will make it easier for you to add transliteration capabilities to textfields on your webpages. Using this customizable API, you can enable users of your website to type 19 languages. For more information, please take a look at the documentation and samples at our code playground. If you're looking for a finer level of control on your web pages, also check out the low-level interface to transliteration, and the font rendering support APIs.

Google Transliteration is integrated into several Google properties and we have bookmarklets in addition to API to extend this capability to other websites. Please try these out and let us know what you think and how you're using it.

Posted by: Kuntal Loya and Ajay Somani, Software Engineers

Google Feed API — Now with instant gratification

To contact us Click HERE
One of Google's most popular APIs is our Feed API. This API is found all over the web, making any feed content available for developers to embed on their sites.

A problem with embedding content in this manner is that there's no good way to make sure that your visitors see the freshest data, regardless of how long they stay on your page. Of course, you could try polling (also known as the "are we there yet?" method), repeatedly reloading the feed to see if the content has changed. This technique is generally a waste of bandwidth and doesn't always result in very low latency.

Instead, we've got something better. I'm pleased to announce a preview of a brand new version of the Feed API, which includes push updates. With this new version, you'll be able to make the latest feed data available to your visitors - when it's available - without polling or requiring a page refresh. The best part is that this will work with any PubSubHubbub enabled feed.

Here's a short demonstration of what I'm talking about:


As the video shows, this new version works much like the older Feed API. But instead of loading the existing feed data, you actually subscribe to the feed, and your callback is executed any time new feed data comes in.

Let's see how this works. First, you must load the API (just like before, except now v2):
google.load("feeds",  "2");
Now, subscribe to the feed you're interested in and give the callback to be executed:
var feed = new google.feed.push.Feed("example.com/atom.xml");
feed.subscribe(myCallback);
And, finally, you need to write the callback method that is run every time there's an update. In this example, we just display each new entry title as it comes in:
function myCallback() {
var container = document.getElementById("feed");
for (var i = 0; i < result.feed.entries.length; i++) {
var div = document.createElement("div");
div.appendChild(document.createTextNode(result.feed.entries[i].title));
container.appendChild(div);
}
}
For a running example you can try out, check out the Code Playground.

We want to encourage you to experiment and build innovative applications with this new API - but since we don't know how it will be used, we can't quite open the floodgates yet. Therefore, we're initially making it available on a sign-up basis. Please fill out this form, telling us a little about how you'd like to use this API, and we'll try to give you access as soon as possible. Also, please remember that this is a Code Labs version, and therefore it may change or be removed at any time.

After we get some data from this experimental period we'll be able to open it up to everyone. Once you've begun experimenting, be sure to stop by our support forum or IRC channel to share your creations with everyone. If you'd like to learn more about how this API works, our Google I/O session will be posted to YouTube soon.


Posted by: Brett Bavar, Software Engineer and Adam Feldman, Product Manager

Diacritization added to the Google Language API

To contact us Click HERE
Earlier this year, we launched the Tashkeel (Diacritization) service on Google Labs. I'm pleased to announce that we've added an experimental Diacritization component to the Google Language API. This is a simple JSON API which you can use to add diacritic symbols to strings of Arabic text.

To test it out, try clicking this link:
https://www.googleapis.com/language/diacritize/v1?lang=ar&message=مرحبا%20العالم&last_letter=false&callback=result

A URL-encoded string is supplied as the message parameter, and it's returned by the API with diacritics included. These symbols are useful to people just learning the language and as an important pre-step for several text processing applications.

Right now, the API only supports Arabic, but we're working on adding more languages, as well as a JavaScript API, so be sure to watch this blog for details. For more information, see the documentation and our post on the Google Arabia blog (you may want to click "view post in English").
Posted by: Adam Feldman, Product Manager and Jeff Scudder, Software Engineer

Increase site efficiency by retrieving just your preferred number of results

To contact us Click HERE
When using any of the searchers available in the Search API, four results are returned by default. Historically, it has been possible to request a large set of eight results (or ten for filter Custom Search Engines), but that’s it. We understand that there are many use cases for this API, and some of them require a finer grain of control over the number of results displayed.

For instance, with the JavaScript API, you can use .setResultSetSize(1) or .setResultSetSize(6) in addition to using the enum to request a SMALL_RESULTSET or LARGE_RESULTSET. When using the RESTful interface, you can also use any integer from 1 to 8 with the rsz parameter.

With this addition, you can now request an arbitrary number of results, based on the exact number you need. By requesting only the results you’re going to show to the end-user, you can make your site or app more efficient. Also, this will control the cursor values that can be used to retrieve subsequent pages of results (and impact paging in the Custom Search element).

For more details, check out the documentation, and if you have any questions, stop by our IRC channel and support forum.

Fall Housekeeping

To contact us Click HERE
When we introduced this blog over four years ago, the term AJAX was only a year old, and Google had exactly one relevant API . Ajax has since become a mainstream part of the Web, and our family of APIs has grown. Like many growing families, we’ve accumulated a lot of cruft over the years, and have outgrown our first home. Time for some housekeeping.

API Documentation - Now easier to find and use
We’ve reorganized our documentation to make it easier to find what you’re looking for, based on what you want to do. We used to group our APIs based on technology - for instance, there were Google Data APIs and AJAX APIs. Now, you’ll see that each API has been given its own place, including its own documentation pages. This new documentation has been created from the ground up to provide a better experience for people coding against the APIs. We’ve also organized these more logically by product, such as moving the Book Search API into the Books family of APIs, and added many more samples to help you get started.

A fond farewell
In the spirit of consolidation, we’ll be retiring this blog in favor of the Google Code Blog. By concentrating on fewer blogs, we’ll be able to keep the blog fresher and help make sure that as wide an audience as possible is able to benefit from our posts. We’ll continue using tags, so that you can subscribe to your favorite APIs and focus on the content that most interests you (though we hope you’ll check in occasionally to see what new stuff you might be missing).

Show your support for the Code blog by hopping over to read about the new Google APIs console and Custom Search API, and also say good-bye to the Web and Local Search APIs, which are being deprecated. Full post here.

Posted by: Adam Feldman, Product Manager

23 Mayıs 2012 Çarşamba

Create a Unique Password for Every Site You Use

To contact us Click HERE


You want to create lengthy, complicated and unique passwords for every website that you use but that rarely happens in practice because these complex strings would be nearly impossible for anyone to remember.

Most people thus rely on password management software that encrypt and store all your passwords in a database which is protected by a single password. You enter that master password and you instantly have access to all your stored user logins and passwords.

unique passwords

There’s however another solution as well that will help you generate unique passwords for all your online accounts but without storing the passwords anywhere – neither online nor on your computer. It’s called Password Chameleon.

With Password Chameleon, all you have to do is remember one master password. You enter the site’s domain name (say gmail.com) and your master password (say He!!0WorId) and tool will instantly create a password by mashing these two strings. Every time you enter your master password and the web domain, the tool will generate the same password.

The good thing is that passwords are generated locally on your computer and while all your online accounts will have unique passwords, you will have to remember just one master password. Also, Password Chameleon uses the SHA-1 Algorithm to generate your passwords (aka hashes) and it impossible to decrypt the master password from the generated hashes.

The downside is that this method isn’t a very practical solution for people who could be maintaining multiple accounts on the same website. The web app and browser extensions are free though the mobile apps cost a little less than $2.

Here’s another password trick suggested by Mozilla that recommends picking a base password and then adding a different suffix and prefix based on the website.

Related reading: Keep your Online Accounts Safe and Secure

Tweet this Share on Facebook


Digital Inspiration @labnolThis story, Create a Unique Password for Every Site You Use, was originally published at Digital Inspiration on 15/05/2012 under Password, Internet.

Related posts:

  1. Choosing Different Passwords for Different Websites
  2. How to Verify That You Have Typed In The Correct Password
  3. How Strong is your Password?
  4. My Password Tree
  5. Selecting a Safe Password Manager for Storing your Secret Passwords

Why You Should Not Rename Your Pinterest Boards?

To contact us Click HERE


pinterest boards

When I first read about Pinterest, I didn’t pay enough attention as it looked like any other image bookmarking site with a beautiful interface. But as I spent more time on the website exploring pins and repinning some of them to my own boards (see here), the interest level has definitely gone up.

I plan to do a detailed write-up later but here’s a quick tip for users who are already active on Pinterest – avoid renaming your Pinterest boards.

That’s because when you change the name of a Pinteret board, the associated web address (public URL) of that board will also change. If people have shared your Pinterest board on Facebook or if they have added your board to their online bookmarks, all those links will point to a non-existent (404) page once a board is renamed as the permalink changes.

Also, Pinterest boards have a Facebook Like button and the other side effect is that the Like counts will reset to zero after the board is renamed.

Tweet this Share on Facebook


Digital Inspiration @labnolThis story, Why You Should Not Rename Your Pinterest Boards?, was originally published at Digital Inspiration on 15/05/2012 under Pinterest, Internet.

Related posts:

  1. How to Hide your Email Address from Facebook Apps
  2. The Kindle Best Sellers that are currently Free
  3. Rename Multiple Files Efficiently Using Excel or Google Docs
  4. How to Change Your Name on Facebook
  5. The Most Popular Group on Facebook

Find the Address of a Place through Google Maps

To contact us Click HERE


Find Address

What’s the address? is a simple tool that can help you find the approximate address of any point on Google Maps.

All you have to do is drag the red marker pin to another location and the approximate snail address of that place should pop-up in a marker window.

You can also search for the street name, city or zip code to quickly jump to any particular location on the map.

The tool internally uses the reverse geocoding feature of the Google Maps API. When you click a point on the map, the latitude and longitude co-ordinates of that place are translated into a human-readable address which is what you see on the map. The UI was written using the Twitter’s Bootstrap framework.

Address Lookup – Demo

Here’s a quick video demo of the tool in action:

http://www.youtube.com/watch?v=V7ryxnKEL-0

Tweet this Share on Facebook


Digital Inspiration @labnolThis story, Find the Address of a Place through Google Maps, was originally published at Digital Inspiration on 17/05/2012 under Google Maps, Location, Internet.

Related posts:

  1. Embed Google Maps on your website or blog
  2. Find Our Blog Readers on Google Maps or Google Earth
  3. Reverse Lookup: Find a Street Address Give the Latitude and Longitude Coordinates
  4. Find the Exact Opposite Point on Earth with Google Maps
  5. Find the Latitude and Longitude of your Home with Google Maps