Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Seo Master present to you: By Chris Yang, Product Manager and Haidong Shao, Software Engineer, Translator Toolkit

Cross-posted with the Google Open Source Blog and the Google Translate Blog

At Google, we put a lot of energy into helping localize the world's information to make it more useful to more people. It's not just about localizing our own products – we want to provide tools that make it easy for translators and developers around the world to localize their own apps and content. Google Translator Toolkit is our online translation tool for amateur and professional translators -- it’s built on Google Translate and supports more than 100,000 language pairs.

This week, the Translator Toolkit team has launched support for four new translation-related file formats:

Android Resource (.xml)
Application Resource Bundle (.arb)
Chrome Extension (.json)
GNU gettext-based (.po)

With these new file formats, you can use Translator Toolkit to localize your apps and other products and content much more quickly and easily.

For example, to translate your Android application, go into the res/values directory and upload strings.xml into Translator Toolkit -- Translator Toolkit will now automatically translate it. You can then share your translations with amateur or professional translators, who can localize the text using Translator Toolkit’s WYSIWYG online editor.



When you’re finished, you can export your translated application and store it in a locale-specific directory in Android. Voilà -- easy localization! 翻译起来太方便了!

In addition, we’ve made the Translator Toolkit interface more intuitive for these new file formats so users can translate faster and more accurately. For example, you can turn on ‘Customized colors’ so translators can annotate the edited segments, ‘Number of characters in the segment’ to make sure the text doesn’t run too long (very important for mobile devices), and ‘Synchronized scrolling’ so you can scroll the original and translated text at the same time, which makes navigation much easier.



With these new file formats and UI features, along with the file formats we already support (.aea, .srt, .html), we hope Translator Toolkit can help you reach more users around the world.

When you’re ready, give Google Translator Toolkit a try and suggest any improvements you’d like to see so we can work on making it even better.


Chris Yang and Haidong Shao are on the Google Translation Toolkit team.

Posted by Scott Knaster, Editor
2013, By: Seo Master
Google resmi tancapkan bisnis mereka di indonesia dan di resmikan 30 maret 2012 ini di gedung cyber 2, melihat perkembangan pengguna internet di indonesia demikian pesat maka mau tidak mau google tidak bisa meremehkan peran indonesia. Seperti kita ketahui jumlah penduduk yang begitu banyak maka indonesia adalah target awal pebisnis dunia jika ingin besar.

Seperti facebook yang jadi besar karena
Seo Master present to you: I'm sure many of you already know about Facebook Social Plugins (FSP) like Facebook Like Button, Facebook Recommendation, Facebook Comments etc. They serve as a good source of traffic since Facebook users share and post your blog into their wall. To install these plugins to Blogger or Wordpress, you will be asked for something called Javascript SDK.

What is Javascript SDK


The real name of Javascript SDK is Facebook SDK for Javascript. To make it simple, it helps you install and use any Facebook Social Plugins with a few lines of code. For example:
To install Facebook like button without Javascript SDK, use this code:
<iframe src="//www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fwww.facebook.com%2Fplatform&amp;width=292&amp;height=590&amp;show_faces=true&amp;colorscheme=light&amp;stream=true&amp;border_color&amp;header=true&amp;appId=136654566362129" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:292px; height:590px;" allowTransparency="true"></iframe>
But with Javascript SDK installed, you just need:
<fb:like-box href="http://www.facebook.com/platform" width="292" show_faces="true" stream="true" header="true"></fb:like-box>
Really cool, right?

Do I Need To Install Javascript SDK For Every Facebook Plugins?

Absolutely not! You only need to install it once.
If you read tutorials about installing FSP to blog, every post contains some steps like "Create Facebook Application", "Adding Code" ("code" means Javascript SDK). Or when you install a plugins from Facebook Developers, the first step is always "Include the Javascript SDK". That does not mean you must install Javascript SDK everytime, you just need to do it once.
Follow this post, and you can skip these steps forever from now on.

How To Install Javascript SDK

1. Create a Facebook Application

Facebook Application helps you manage and track your plugin. This also help you add more Administrator to manage plugin (especially for Facebook Comment) and more. Every Facebook Application comes with an App ID. When you provide this ID, it enables Facebook's Open Graph Meta Tags, which let you administer Facebook Pages for products (where you can share product updates and engage with customers who have "Liked" a product), and use Facebook Insights to track key metrics.

When creating a new Facebook Application, we are not really building an actual app, we just need a App ID. Providing an App ID for use with the Social Widgets feature is recommended, but optional, so you can skip this step.
Something you need to know about Facebook AppID:
  • You can use one AppID for multiple blogs.
  • Some plugins will not work without Facebook App.
  • Not all of the Facebook plugin need an App ID for installation code.
  • Some plugins need a particular AppID to work properly, that's mean you need to create a new Facebook App for the blog which uses that plugin.
Okay, let's do it:
  1. Go to Facebook Apps Developer and Login. Then click Create New App.
    Create New Facebook App
    Create New Facebook App
Read more »2013, By: Seo Master
Powered by Blogger.