Skip to main content

Everybody Makes Mistakes

In February 2008, out of necessity, I developed (using publicly available code) my on-the-fly multi-lingual translator applet, which you can see in the top of the sidebar. When originally developed, the applet offered a dozen or so languages, a population which has now grown to 34, from several enhancements.

Some time ago, I became aware of an anomaly which bothered me mildly - if you were viewing an archived post in your blog, and you used the translator, you would get a nicely translated copy of the main page of the blog, not of the archived post. In other words, if you had attempted to translate Make Your Blog Speak More Languages, you would, none the less (today) have gotten a translation of Importing / Exporting Blog Contents Now In Production (Orange) Blogger.

This was slightly annoying, but just one more oddity which I never took the time to research. Until today.

To shorten this narrative somewhat, today I found a small code error which caused the anomaly. If you acquired this applet from the original post Make Your Blog Speak More Languages, your copy will probably have this code problem, too. Fortunately, it's a simple correction, in the header section of the applet code.

<form action="http://www.google.com/translate">

<script language="javascript" type="text/javascript">

<!--

document.write ("<input name=u value="+location.href+" type=hidden>")

// -->

</script><input value="http://blogging.nitecruzr.net/" name="u" type="hidden"/>

<noscript><input value="http://blogging.nitecruzr.net/" name="u" type="hidden"/></noscript>

<input value="en" name="hl" type="hidden"/>

<input value="UTF8" name="ie" type="hidden"/>

<input value="" name="langpair" type="hidden"/>

<input onclick="this.form.langpair.value=this.value" title="Andorran / Catalan" value="en|ca" type="image" height="20" src="http://1.bp.blogspot.com/__v4nth5_ki0/SP-fM7vwhSI/AAAAAAAAHl0/ZoZkfhEb01M/s320/Andorra+-+Catalan+-+ad_flag.png" width="30" name="langpair"/>

...

</form>

<a href="http://blogging.nitecruzr.net/2008/02/make-your-blog-speak-more-languages.html"><span style="font-weight:bold;">What Are These?</span></a>

If your blog is using the code which I provided, you may wish to look in your applet code for the snippet highlighted above, and remove it. I think that will make the applet then reliably translate whatever individual post (archive, label search, what have you) rather than simply the blog main page.

Everybody makes mistakes, sorry about that.

>> Top

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.