Fairchild’s Raging Domain

unleashing the kid in me! ^o^

Google Translation Flags Widget Update August 20, 2010

Filed under: Editorials — Mari Agnes @ 7:32 am
Tags: , , , ,

I previously had the codes up for translating English blogs into other popular languages but I received so many emails asking how to translate from another foreign language to English, say, Japanese  to English.

We just need to edit a bit of the codes as provided on the translation widget available for download on this page.

Notice in the document containing the codes the highlighted words in bold as shown below.

<a href=”http://translate.google.com/translate?hl=en&amp;langpair=en|ja&amp;u=https://fairchildonrage.wordpress.com/” title=”Japanese“><img border=”0″ style=”cursor:pointer; cursor:hand;” width=”24″ alt=”Google-Translate-English to Japanese BETA” src=”http://upload.wikimedia.org/wikipedia/commons/thumb/9/9e/Flag_of_Japan.svg/800px-Flag_of_Japan.svgxx.png” height=”18″ title=”Translate English to Japanese BETA“/></a>

1. Interchange the following: en/ja to ja/en (en = English /// ja= Japanese)

2. Rename the title “Japanese” into “English

3. Rename “Google-Translate-English to Japanese BETA” into “Google-Translate-Japanese BETA to English”

4. Replace the Japanese flaglet’s URL to that of the UK or American flag, say, http://UK/US.flag.jpg

5. Finally edit “Translate English to Japanese BETA” into “Translate Japanese BETA to English

6. Make use of the text widget on your dashboards to display on your sidebars and you’re done!

For other legends: (just for the languages I’ve used in this widget)

ar = Arabic ///zh-CN =Chinese Simplified /// bg = Bulgarian /// zh-TW = Chinese Traditional /// hr = Croatian ///cs = Czech /// da = Danish /// nl = Dutch /// fi = Finnish /// fr = French /// de = German /// el = Greek /// hi = Hindi /// it = Italian ///ko = Korean /// no = Norwegian /// po = Polish /// pt = Portuguese /// ro = Romanian /// ru = Russian /// es = Spanish /// sv = Swedish

Have fun tweaking the codes!

 

Whos.Among.Us on your WP Sidebars

Filed under: Editorials — Mari Agnes @ 6:27 am
Tags: , , , ,

Fairchild here, yoroshiku!

I never thought I’d be posting something here again on my old blog, how nostalgic. It’s just that I’ve been receiving email inquiries on how to display Whos.Amung.Us Counters on their WordPress blogs. I also have sneaked into the forums about the issue but it won’t work for the many of us since WordPress indeed does not allow javascripts on their platforms, only HTMLs.

Truth is, Whos.Among.Us made a tutorial on how to in this outdated post –> How To – WordPress Installation and if you would notice a year or two ago, they were still offering a choice of java-script and non-javascript codes so probably I didn’t fuss about the issue back then.  It worked for me no less but it isn’t the case this time with the many who were interested to use the same widget on their blog too since they no longer offer the same options.. only javascripts!

Wait, don’t despair yet!  I’m gonna be sharing with you two simple tricks and you can use WAU widget right on your blog in seconds!  I’m not an expert on htmls and javascripts or anything closer than that, lol.  It’s just out of curiosity that I have rediscovered these tricks and it’s worth sharing I guess.

Method A.

This is kinda simpler, if I were to be asked..

1. Learn the steps on how to add the WUA Widget on WordPress by checking this article — WordPress Installation.

2. Go to the front page of the site — Whos.Among.Us

3. Next for Trick No. 1, scroll down to the Getting Started area and find a dialogue box containing a javascript like the image below:


4.  Look for your tracker code. In this case, it’s lw191dcgtiv, usually following the word “tab” and enclosed in parenthesis.

5.  Edit this HTML code ideal for our WP.  This was the non-java script code WAU offered users before.

<a href=”http://whos.amung.us/stats/xxxxxxxxxxxx/”><img src=”https://whos.amung.us/widget/xxxxxxxxxxx.png&#8221; width=”81″ height=”29″ border=”0″ title=”Click to see how many people are online” /></a>

6.  Replace the “xxxxxx” with the tracking code and proceed with Step 1.

7. Voila!  Enjoy your Widget.

Method B

This is for those who wanted a more complicated setup..

1. Follow Steps 1 & 2 as stated above.

2. Scroll further down to the “More Widgets” area and click on “Showcase” or simply click on the “Showcase Nav Tab” on the upper left side of the WAU front page and you will be led into this:

3.  Notice that yo will still be provided with the same javascript as on the front page but this time you will be given an option to post on several sites that the widget can be used on and it will show you this:

And since we’re on WordPress choose the WP icon and enter your data as follows:

After filling in details, click on Post.

4.  Check on Your WordPress blog and a Post would have been published. (Though it took a while in my case, but it depends.)

5. Use custom methods in editing WP posts which looks like this:

6. You may copy the whole text or just simply start copying from <a href=….

7. Paste on the WP Text Widget and you’re done. See step 1 of  Method A for more reference.

But remember we can’t use those cool maps, just the counters, unless you are on a self hosted blog I suppose (not sure though, haven’t tried).  Also, check on this forum topic for more helpful ideas.

That’s all folks!  Hope you will have that handy little widget on your blogs the soonest!

 

Google Translation Flags Widget for my WP! September 27, 2008

Filed under: Editorials — Mari Agnes @ 9:51 am
Tags: , , ,

Finally there’s one for my WP blog!

It’s been so hard to embed scripts on WordPress but just today I stumbled upon Blogger Accessories‘ page and at the same time found over via search engine a similar forum post.

Here’s the WP forum post with Ishmailimail’s codes:

Translate your blog into different languages.

Now after doing some tweaks, I came up with this codes.

translation-widget (English to other languages)

Now, I do have my own translator widget on my blog’s sidebars!

Yey, thanks to both!

Check on the UPDATED post HERE.