Skip to main content

Get yoor blog translated via Google Translations



Ok this is real cool, all you need is to copy and paste this code(courtesy consumingexperience.blogspot.com, the guy who started Technorati) . So what I did was.

o Install my language packs(for east asian languages).

o Restarted my computer(gee..that you so have to do, if you're on a microsoft machine)

o The code, in JavaScript and HTML


o I pasted this code just under my post tag, you can also put it all above to display it on top as well. (Maybe I'll do that too, if I can't find a way quickly now to translate my individual post, it's possible but right now I gotta rush to the movies ;-)).

Ok so we're back, cool movie Madagascar, by the way.


PS: For Japanese, Korean and Chinese you'll need to install language packs on your XP machine, or else you'll see lot's of pipe bars.

If you're not seeing this on for the Japanese, Korean or Chinese then you need to install the language packs(On *nix machines it should be installed). If you have XP/2000 then you might want to install the language packs. See below.

Click on it and then Install them, you will be asked for the installation CD.



And then clicking on, for instance a japanese translation you'll see this page.



and upon clicking for translation you get this...



or if you'd rather want it in spanish.



If you want it(the translation) to open in the same window get rid of all the _target=blank in the Template code.

Ok so as you see I went ahead and replaced the JavaScript with the HTML code. The code was placed between [blogger] and [/blogger]
and here it is


<a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Cde&#38;hl=de&ie=UTF-8&amp;ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools">Deutsche</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Ces&hl=es&ie=UTF-8&#38;ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools">Español</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Cfr&#38;hl=fr&ie=UTF-8&amp;ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools">Français</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Cit&#38;hl=it&ie=UTF-8&amp;ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools">Italiano</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Cpt&#38;hl=pt&ie=UTF-8&amp;ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools">Português</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Cja&#38;hl=ja&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools"> ���</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Cko&#38;hl=ko&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools"> �국�</a> | <a href="http://translate.google.com/translate?u=<$BlogItemPermalinkURL$
>&langpair=en%7Czh-CN&#38;hl=zh&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools">�语</a>



All I did was

o Replace the $BlogURL$ with $BlogItemPermalinkURL$



and then replace it all...




o removed _target="blank"

Try it out!

Tarry

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op...